Intro
Agenda
Test Automation
Test Automation - Why
What's the problem?
UI test automation
Domain model
UI representation
Test case
Test automation effectiveness
Automation effectiveness
Automation effectiveness constituents
The formula
Automation effectiveness charts
Td or Ts - what to minimize
Tools
Tool characteristics that affect effectiveness
Jemmy
Automation techniques
Test automation approaches
Techniques
Coordinates (images)
Coordinates cont.
Widgets
Widgets cont.
Widgets (or coordinates)
Library
Library of UI primitives
Library of UI primitives cont.
Domain test library - 1
Domain test library - 2
Domain test library - 3
TD and TS - all together
TD and TS
TD and TS for NC=3, NR=8, TM=1
EA for NC=3, NR=8
Other aspects improving effectiveness
Test is a program
Test harness
Resources
Conclusion
UI test automation is, nowadays, a commonly used approach. First, because of the tools offering, second because different organization started to realize (if they did not do it before) how high is the defect cost, so they started to think about getting more from testing while spending less on it. For many, it becomes obvious pretty soon that the automation is not as beneficial as if first seemed.
Alexandre Iline has a lot of background in quality engineering and UI testing in particular. Over the past years Alexandre has been a tester, test lead, quality technologist and/or test tool architect on several large products such as Netbeans or Java Studio Creator.
He has developed a testing tool: Jemmy, which is one of the tools used for Java UI testing commonly nowadays. Also, I've been an architect for several extensions for Jemmy, one of which is Jellytools.
As the author of Jemmy, I have made numerous presentations about the tool, test automation and other technical aspects of QE to a various audiences in SUN Microsystems. As Jemmy is open-source, I am participating in some open aliases and discussion forums.