5 | | The core of QUEST is that we provide abstract events that are independent of any specific event-driven platform. Using a plug-in mechanism, support for specific platforms is added to QUEST. There are 4 plug-ins available at the moment: |
6 | | * quest-plugin-jfc for Java JFC GUIs |
7 | | * quest-plugin-mfc for Windows MFC GUIs |
8 | | * quest-plugin-php for PHP-based Web applications |
9 | | * quest-plugin-guitar as a bridge to the GUITAR testing framework |
| 5 | [[Image(quest-architecture2.png, nolink, align=center, border=2)]] |
11 | | As for the quality assurance itself, there are two main branches with the following components of QUEST: |
12 | | * Usage-based Testing |
13 | | * quest-core-assertions |
14 | | * quest-core-coverage |
15 | | * quest-core-testgeneration |
16 | | * quest-core-usageprofiles |
17 | | * Automated Usability Analysis |
18 | | * quest-core-tasktrees |
19 | | * quest-core-usability |
| 7 | The '''Quest Core Library''' is independent of specific event-driven platforms and consists of seven components. |
| 8 | * The ''Abstract Events'' provides the required classes and interfaces for working with an abstract notion of events independent of any platform. Furthermore, it includes the classes and interfaces required by GUI platforms to create an GUI model. This allows a very powerful and yet platform independent modelling of GUI events. |
| 9 | * The components ''Usage Profiles'', ''Test Case Generation'', ''Test Oracles'', and ''Test Coverage'' provide support for usage-based software testing. |
| 10 | * The components ''Task Trees'' and ''Usability Evaluations'' facilitate usability analysis. |
| 12 | The '''Quest Plug-ins''' depend on the Quest Core Library and build the bridge between abstract events and the platform-independent tooling and concrete event-driven software platforms. Currently, Quest provides four plug-ins: |
| 13 | * The ''Java Foundation Classes'' plug-in supports the analysis of Java applications with a JFC GUI (i.e., AWT/Swing). |
| 14 | * The ''Microsoft Foundation Classes'' plug-in supports the analysis of Microsoft Windows applications with a MFC GUI. |
| 15 | * The ''PHP-based Web Applications'' plug-in supports the analysis of strictly PHP-based websites, i.e., all parts of the website have to use PHP, no other technologies, e.g., simple HTML are allowed. |
| 16 | * The ''GUITAR'' plug-in provides a bridge to the [http://guitar.sourceforge.net/ GUITAR testing framework]. |
| 17 | Furthermore, two additional plug-ins are currently planned. |
| 18 | * The ''!JavaScript Web Monitoring'' plug-in will provide better support for the analysis of websites than the ''PHP-based Web Applications'' plug-in, to broaden the scope of websites we can analyze. |
| 19 | * The ''SOA Applications'' will facilite the application of our techniques to Service Oriented Architectures. |