Programų testavimo metodai Autorius: Rūtenis Turčinas IFM–2/2 gr. Graphical user interface testing

What is it? Graphical user interface (GUI) testing is the process of testing a product's graphical user interface to ensure it meets its written specifications 2

On which projects use it? It depends on project type: Impossible to use on projects without GUI: backend, middleware, etc. Possible and worth to use on projects with GUI: many of today‘s products 3

When is it worth to use? Trying to achieve 100% product quality – must use GUI tests If goal is to check mostly usable cases - worth to use GUI tests Don‘t use GUI tests - if quality is not important 4

Is GUI testing useful? It is easier to test with GUI associated functions Possible to test situations, which are not testable with other methods In test cases simulated real users 5

Problems Size WordPad – 325 possible GUI operations Sequence Some functionality of the system may only be accomplished by following some complex sequence of GUI events Error location 6

GUI testing approaches GUI component testing GUI hierarchical model testing GUI functionality testing 7

GUI component testing Split application into test components (component = window) Test each component thoroughly Test integration of components 8

GUI hierarchical model 9 1 Level (main GUI form) 2 Level (sub-forms)... N-th Level (sub-forms)

GUI functionality testing Determine: Users Initial state Steps (event sequences to achieve goal state) Goal state 10

GUI functionality testing 11

Testing tools Selenium (Web UI) Robotium (Android OS) Jemmy (JAVA SE) SWTBot (SWT applications) And many others 12

Selenium IDE 13

Selenium IDE Targets – Xpath language: 123"] JavaSript support (parameters, etc.) TestCase command source: open ${stUrl}/login.xhtml 14

Questions: 15

1. When to use GUI test? 2. When do not use GUI test? 3. What are GUI testing problems? 4. What are GUI testing approaches? 5. Is it possible to test GUI without testing tools? 16