From: Jurgen Vinju To: Date: Fri, 5 Nov 2004 13:09:51 +0100 Subject: PEM: Maarten van der Graaf | From Box to HTML | 26.06.97 PEM: Gerjon de Vries | Testing User Interfaces | 26.06.97 From: pem (PEM moderator) To: pem-noreply Subject: PEM meeting | 26.06.97 | F013, UvA WINS Precedence: bulk X-url: http://www.cwi.nl/~pem Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" This announcement can be found at Testing User Interfaces Date: 26.06.97 Time: 10:30 Venue: F013, UvA WINS Speaker: Gerjon de Vries Title: Testing User Interfaces 1. There are a lot of tools and methods available to the software engineering, that aid in the development of platform independent applications. However, most of these tools share the same drawback: the generated applications use an interface that is directed to one of the targeted platforms. Platform independence almost never means interface independence. 2. Much research is done in the field of program testing. But it remains an incredible difficult task to test programs with a GUI automatically. Besides that, most companies choose a testing tool to fit their software architecture. Testing could be much more effective when the software architecture is chosen to fit the testing methods. I am working on a project that addresses both of these symptoms. The result will be an application framework. The framework should be extensible in an interface independent way. So different versions of the framework may target an application to different (types of) interfaces. One very special version of the framework will not target an interface, but can be used to test the application under development. The test framework should aid in the automation of: testcase-generation and -execution and oracle definition. To achieve this, I will introduce a new software architecture. In that architecture a layer is introduced between model and view-controller. Besides that a more clear division is made between the three building blocks, and the controller is divided in a user-controller and an application-controller. I will also show how automation of the testing process is achieved with this new architecture _________________________________________________________________ The programming environment meetings are a forum for the presentation and discussion of new ideas, ongoing and finished work. A typical meeting addresses a subject in the area of programming environments, program generation, algebraic specification, term rewriting, parsing, etc. A presentation ideally takes between 45 and 90 minutes. Meetings taking longer than 45 minutes are interrupted by a coffeebreak. Most Thursdays, a meeting is held which starts at 10:00 am. in one of the rooms at CWI/WINS. Exceptionally, dates or times may change. The program of the meetings is available on WWW: http://www.cwi.nl/~pem _________________________________________________________________