|
|
 |
|
|
|
Automation
Automated TestingMy first testing assignment as a “tester” was the testing of a life insurance application that was programmed in Smalltalk, running under OS/2 in 1997. The VSE-implementation was somewhat dirty, dealing improperly with the OS/2 message queue and showing some typical racing condition flaws. There was just one test driver for automated tests that would be suited: QA partners from Seque Software. However, because of the dirty GUI-implementation of VSE, simple methods needed for test automation provided false input. the use of the method
settext(textwidgetname, “1010”)
would set the textfield to 010 instead of 1010.
Nevertheless, we managed to automate functional testing. The picture shows our main testing framework architecture. In 1998 the file structure used was a little bit clumsy. The basic outline of the testing script was already governed by testcases and keywords (later refurnished to become testactions). There also was no direct scripting of the automated test automation tool. Instead we programmed an interpreter shell around the test automation tool. That made it easy to exchange the third party tool to another one better suited for our needs. Testcases were maintained in a testcase data base.
The basic structure of Generali's test automation system in 1998/1999.
The implementation would not have been possible without the help of: * Ernst Corazza-Sefcik, Where did it go from there? ABCD Application Based Testcase Database
|
|
©2005 Hans Hartmann, all Rights reserved. Last Updated: Thursday 13 July 2006. Impressum und Disclaimer
