Deconstructing GUI Test Automation

[magazine]
Four framework-building abstraction layers, their advantages and pitfalls, and ways developers may be able to help you avoid them altogether.
By
Bret Pettichord
-
March 5, 2003
Volume-Issue: 
2003-01
Article Summary: 

Window mapping gives elements specific names so tests are easier to update and understand. Task libraries group sequences of steps that make up part of user tasks when those sequences show up in multiple tests. Data-driven test automation separates the parameters of a test case from the test script so that the test script can be reused for many related tasks. Keyword-driven test automation formats tests as tables or spreadsheets and creates parsers to read and execute the test descriptions. Take advantage of these four techniques to help you test a graphical user interface, and see how developers can make your life easier.