4 Typical workflow to create tests with QF-Test Create new test suiteDefine application (SUT) startupRun SUT (system under test) in QF-TestIn recording mode: perform manual actions (includes component recognition)Check, adapt, parameterize recognized components (menus, windows, buttons, …)Use recorded actions as basis for new procedure(s), parameterize, …Define new test case, specify dependencies and call required procedures
13 Developers support Intervention on the code: call during the initialization phase to the method setName() for all GUI-elementsevent on a thread other than the AWT event dispatch thread (COMP-5141 and COMP-2905) (seewhen important changes in the GUI are planned and are being developed. The sooner we are informed, the better.
14 Problems GUI test & QF-Test experience required Adaptations to client changesComponent recognition issues, threads handling (cooperation with developers)QF-Test covers basic functionality but still requires a lot of manual work
15 ConclusionsOnce the manual work is done and the SUT is stable enough so that it does not require a lot of changes at every new release, the automated tests reveal to be very useful as regression tests.They are configurable, therefore can be run in whatever environment with whatever db and user (provided QFTest licence is available)
16 Selenium: Introduction, Documentation, Installation and Download, Tutorials…Example of a demo:Products:Selenium IDESelenium RCSelenium 2.0...
17 Selenium IDE Add-On for Firefox Record and Replay Tool Access to Selenium commandsSave test cases in Selenese or many other programming languages
18 Selenium RC Selenium RC components are: The Selenium Server which launches and kills browsers, interprets and runs the Selenese commands passed from the test program, and acts as an HTTP proxy, intercepting and verifying HTTP messages passed between the browser and the AUT.Client libraries which provide the interface between each programming language and the Selenium RC Server.
19 Selenium and ZkZK Web Applications can be a challenge with Selenium because ZK dynamically generates element IDsWorkaround: not fully satisfactoryQFTest: just starting with support for ZkOther products: Sahi: