Changes between Version 40 and Version 41 of WikiStart
- Timestamp:
- 10/01/12 10:10:39 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v40 v41 1 1 [[TracNav(TOC|nocollapse)]] 2 2 3 = Quest - ''QU'''ality assurance of '''E'''vent-driven '''S'''of'''T'''ware =3 = !EventBench - Quality assurance of Event-driven Software = 4 4 5 Welcome to the homepage of the Quest software quality assurance tool suite. Within the Quest project, we provide research prototypes for testing, analyzing, and observing event-driven software. The two main venues of the project are ''usage-based testing'' and ''usability analysis''. Questconsists of three main architectural components, as depicted by the following figure.5 Welcome to the homepage of the !EventBench software quality assurance tool suite. Within the !EventBench project, we provide research prototypes for testing, analyzing, and observing event-driven software. The two main venues of the project are ''usage-based testing'' and ''usability analysis''. !EventBench consists of three main architectural components, as depicted by the following figure. 6 6 7 [[Image( quest-architecture2.png, nolink, align=center)]]7 [[Image(eventbench-architecture.png, nolink, align=center)]] 8 8 9 The ''' QuestCore Library''' is independent of specific event-driven platforms and consists of seven components.9 The '''!EventBench Core Library''' is independent of specific event-driven platforms and consists of seven components. 10 10 * 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. 11 11 * The components ''Usage Profiles'', ''Test Case Generation'', ''Test Oracles'', and ''Test Coverage'' provide support for usage-based software testing. 12 12 * The components ''Task Trees'' and ''Usability Evaluations'' facilitate usability analysis. 13 13 14 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, Questprovides four plug-ins:14 The '''!EventBench Plug-ins''' depend on the !EventBench Core Library and build the bridge between abstract events and the platform-independent tooling and concrete event-driven software platforms. Currently, !EventBench provides four plug-ins: 15 15 * The ''Java Foundation Classes'' plug-in supports the analysis of Java applications with a JFC GUI (i.e., AWT/Swing). 16 16 * The ''Microsoft Foundation Classes'' plug-in supports the analysis of Microsoft Windows applications with a MFC GUI. … … 20 20 * 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. 21 21 * The ''SOA Applications'' will facilite the application of our techniques to Service Oriented Architectures. 22 23 == Infrastructure ==24 25 * SVN repository: https://eventbench.informatik.uni-goettingen.de/svn/quest/26 * Hudson CI server: https://trex.informatik.uni-goettingen.de/hudson/view/QUEST/27 * ohloh metrics: [https://www.ohloh.net/p/quest_]