Tutorial | QF-Test Tutorial

1Working with a Sample Test suite (Java)

Fig. 1.1The Test suite FirstJavaTests.qft Fig. 1.2The "Test set: Simple Tests" Node Fig. 1.3The Setup Node Fig. 1.4The Sequence to start the SUT Fig. 1.5The CarConfigurator Demo Fig. 1.6The "First" Test case Fig. 1.7Details of the first Test case Fig. 1.8The result view in the status line Fig. 1.9The Second Test case Fig. 1.10Details of the second Test case Fig. 1.11Error in the second test case Fig. 1.12Run log for the second test case Fig. 1.13Error in the second test case Fig. 1.14Screenshot node showing the error situation Fig. 1.15The Cleanup Sequence Fig. 1.16Run log for the Completed Test set Fig. 1.17Report Generation Properties Fig. 1.18An HTML Report

2Creating your own test suite (Java)

Fig. 2.1Type of Application Fig. 2.2Type of Executable Fig. 2.3Executable file selection.Fig. 2.4Final Information Fig. 2.5Generated Setup Sequence Fig. 2.6The CarConfigurator Demo Window Fig. 2.7Recording actions on the CarConfigurator Demo Fig. 2.8The Recorded Sequence Fig. 2.9The Renamed Sequence Fig. 2.10The recorded check node Fig. 2.11Start organizing the test suite Fig. 2.12The Organization of your test suite Fig. 2.13The simple cleanup sequence Fig. 2.14 The Run log of the test suite

3Writing a Procedure (Java)

Fig. 3.1Two identical test steps Fig. 3.2Create a procedure node Fig. 3.3Fill in the procedure content Fig. 3.4Insert a procedure call Fig. 3.5Select a procedure Fig. 3.6Test-suite with procedure

4Components (Java)

Fig. 4.1Addressing a table cell Fig. 4.2Locating a component Fig. 4.3Component tree Fig. 4.4Details of the Component node

5Using the Debugger (Java)

Fig. 5.1Set break point Fig. 5.2Start test run Fig. 5.3Remove break point Fig. 5.4Stepping into a node Fig. 5.5Stepping over a node Fig. 5.6Stepping out of a node Fig. 5.7Pause execution at first node of the second test case Fig. 5.8Skip over a node Fig. 5.9Skip out of a node Fig. 5.10Set debugger options to pause on error Fig. 5.11Test run paused by error Fig. 5.12Error Dialog Fig. 5.13Update check node with current data Fig. 5.14Corrected check node

6Variables and Procedure Parameters (Java)

Fig. 6.1Two almost identical test steps Fig. 6.2Procedure with hard coded value Fig. 6.3The Details of the 'Procedure' node Fig. 6.4'Check text' node Fig. 6.5Second procedure calls 'checkFinalPrice'Fig. 6.6Variable bindings Fig. 6.7Popup menu for 'Additional node operations'Fig. 6.8Variable bindings stack showing incorrect value Fig. 6.9Continue Execution from here Fig. 6.10Details of the Set variable node Fig. 6.11Procedure returning a value

7The Standard Library (Java)

Fig. 7.1The Standard Library

8Control structures (Java)

Fig. 8.1Setup Sequence with if-else structures Fig. 8.2Wait for client to connect writes the result into the variable "isSUTRunning"Fig. 8.3If node evaluates the variable Fig. 8.4Transform a node into another one Fig. 8.5Pack a node into another one Fig. 8.6Details of a Loop node Fig. 8.7The new test case Fig. 8.8Details of the Check items node

10Working with a Sample Test suite (Web)

Fig. 10.1The Test suite FirstWebTests.qft Fig. 10.2The "Test set: Simple Tests" Node Fig. 10.3The Setup Node Fig. 10.4The Sequence to start the Browser Fig. 10.5The CarConfigurator web demo page Fig. 10.6The "First" Test case Fig. 10.7Details of the first Test case Fig. 10.8The result view in the status line Fig. 10.9The Second Test case Fig. 10.10Details of the second Test case Fig. 10.11Error in the second test case Fig. 10.12Run log for the second test case Fig. 10.13Error in the second test case Fig. 10.14Screenshot node showing the error situation Fig. 10.15The Cleanup Sequence Fig. 10.16Run log for the Completed test set Fig. 10.17Report Generation Properties Fig. 10.18An HTML Report

11Creating your own test suite (Web)

Fig. 11.1Type of Application Fig. 11.2Specification of the URL.Fig. 11.3Final Information Fig. 11.4Generated Setup Sequence Fig. 11.5The "CarConfigurator Web" demo page in the browser Fig. 11.6Recording actions on the "CarConfigurator Web" demo Fig. 11.7The Recorded Sequence Fig. 11.8The Renamed Sequence Fig. 11.9The recorded check node Fig. 11.10Start organizing the test suite Fig. 11.11The Organization of your test suite Fig. 11.12The simple cleanup sequence Fig. 11.13The run log of the test suite

12Writing a Procedure (Web)

Fig. 12.1Two identical test steps Fig. 12.2Create a procedure node Fig. 12.3Fill in the procedure content Fig. 12.4Insert a procedure call Fig. 12.5Select a procedure Fig. 12.6Test-suite with procedure

13Components (Web)

Fig. 13.1Addressing a table cell Fig. 13.2Web resolvers as installed in the FirstWebTests.qft Fig. 13.3Locating a component Fig. 13.4Component tree Fig. 13.5Details of the Component node

14Using the Debugger (Web)

Fig. 14.1Set break point Fig. 14.2Start test run Fig. 14.3Remove break point Fig. 14.4Stepping into a node Fig. 14.5Stepping over a node Fig. 14.6Stepping out of a node Fig. 14.7Pause execution at first node of the second test case Fig. 14.8Skip over a node Fig. 14.9Skip out of a node Fig. 14.10Set debugger options to pause on error Fig. 14.11Test run stopped by error Fig. 14.12Error Dialog Fig. 14.13Update check node with current data Fig. 14.14Corrected check node

15Variables and Procedure Parameters (Web)

Fig. 15.1Two almost identical test steps Fig. 15.2Procedure with hard coded value Fig. 15.3The Details of the 'Procedure' node Fig. 15.4'Check text' node Fig. 15.5Second procedure calls 'checkFinalPrice'Fig. 15.6Variable bindings Fig. 15.7Popup menu for 'Additional node operations'Fig. 15.8Variable bindings stack showing incorrect value Fig. 15.9Continue Execution from here Fig. 15.10Details of the Set variable node Fig. 15.11Procedure returning a value

16The Standard Library (Web)

Fig. 16.1The Standard Library

17Control structures (Web)

Fig. 17.1Setup Sequence with if-else structures Fig. 17.2Wait for client to connect writes the result into the variable "isSUTRunning"Fig. 17.3If node evaluates the variable Fig. 17.4Transform a node into another one Fig. 17.5Pack a node into another one Fig. 17.6Details of a Loop node Fig. 17.7The new test case Fig. 17.8Details of the Check items node

19Working with a Sample Test Suite (Win)

Fig. 19.1The Test Suite FirstWinTests.qft Fig. 19.2The "Test set: Simple Tests" Node Fig. 19.3The Setup Node Fig. 19.4The Sequence to start the SUT Fig. 19.5The Windows CarConfigurator Demo Fig. 19.6The "First" Test Case Fig. 19.7Details of the First Test Case Fig. 19.8The result view in the status line Fig. 19.9The Second Test Case Fig. 19.10Details of the Second Test Case Fig. 19.11Error in the Second Test Case Fig. 19.12Run Log for the Second Test Case Fig. 19.13Error in the Second Test Case Fig. 19.14Screenshot node showing the error situation Fig. 19.15The Cleanup Sequence Fig. 19.16Run Log for the Completed Test Set Fig. 19.17Report Generation Properties Fig. 19.18An HTML Report

20Creating Your Own Test Suite (Win)

Fig. 20.1Type of Application Fig. 20.2Windows executable file selection.Fig. 20.3Final Information Fig. 20.4Generated Setup Sequence Fig. 20.5The Windows CarConfigurator Demo Fig. 20.6Recording actions on the CarConfiguratorForms Demo Fig. 20.7The Recorded Sequence Fig. 20.8The Renamed Sequence Fig. 20.9The recorded check node Fig. 20.10Start organizing the test suite Fig. 20.11The Organization of your test suite Fig. 20.12The simple cleanup sequence Fig. 20.13The Run Log of the Test Suite

21Writing a Procedure (Win)

Fig. 21.1Two identical test steps Fig. 21.2Create a procedure node Fig. 21.3Fill in the procedure content Fig. 21.4Insert a procedure call Fig. 21.5Select a procedure Fig. 21.6Test-suite with procedure

22Components (Win)

Fig. 22.1Addressing a table cell

23Using the Debugger (Win)

Fig. 23.1Set break point Fig. 23.2Start test run Fig. 23.3Remove break point Fig. 23.4Stepping into a node Fig. 23.5Stepping over a node Fig. 23.6Stepping out of a node Fig. 23.7Pause execution at first node of the second test case Fig. 23.8Skip over a node Fig. 23.9Skip out of a node Fig. 23.10Set debugger options to pause on error Fig. 23.11Test run stopped by error Fig. 23.12Error Dialog Fig. 23.13Update check node with current data Fig. 23.14Corrected check node

24Variables and Procedure Parameters (Win)

Fig. 24.1Two almost identical test steps Fig. 24.2Procedure with hard coded value Fig. 24.3The Details of the 'Procedure' node Fig. 24.4'Check text' node Fig. 24.5Second procedure calls 'checkFinalPrice'Fig. 24.6Variable bindings Fig. 24.7Popup menu for 'Additional node operations'Fig. 24.8Variable bindings stack showing incorrect value Fig. 24.9Continue Execution from here Fig. 24.10Details of the Set variable node Fig. 24.11Procedure returning a value

25The Standard Library (Win)

Fig. 25.1The Standard Library

26Control Structures (Win)

Fig. 26.1Setup Sequence with if-else structures Fig. 26.2Wait for client to connect writes the result into the variable "isSUTRunning"Fig. 26.3If node evaluates the variable Fig. 26.4Transform a node into another one Fig. 26.5Pack a node into another one Fig. 26.6Details of a Loop node Fig. 26.7The new test case Fig. 26.8Details of the Check items node

28Working with a Sample Test suite (Mobile)

Fig. 28.1The first test suite Fig. 28.2The contents of the "Test set: Simple Tests" node Fig. 28.3The Setup node Fig. 28.4The sequence to start the mobile device Fig. 28.5The CarConfigurator Android demo Fig. 28.6The "First" Test case node Fig. 28.7Details of the first test case Fig. 28.8The result view in the status bar Fig. 28.9The "Second" Test case node Fig. 28.10Details of the second test case Fig. 28.11Error in the second test case Fig. 28.12Run log of the second test case Fig. 28.13Error diagnosis for the second test case Fig. 28.14Screenshot node showing the error situation Fig. 28.15The Cleanup sequence Fig. 28.16The run log of the complete test set Fig. 28.17Report Generation properties Fig. 28.18An HTML Report

29Creating your own test suite (Mobile)

Fig. 29.1Selecting the SUT type Fig. 29.2Select device and app for Android Fig. 29.3Select device and app for Android Fig. 29.4Generated start sequence Fig. 29.5The recording window for Android applications Fig. 29.6 Fig. 29.7 Fig. 29.8The tree after recording the sequence Fig. 29.9The renamed sequence Fig. 29.10Beginning the structuring Fig. 29.11The tree after restructuring Fig. 29.12Simple cleanup sequence for Mobile

30Create a procedure (Mobile)

Fig. 30.1Two identical test steps Fig. 30.2Create procedure node Fig. 30.3Fill procedure with content Fig. 30.4Insert procedure call Fig. 30.5Select procedure Fig. 30.6Test suite with procedure

31Components (Mobile)

Fig. 31.1Addressing a list item

32Using the Debugger (Mobile)

Fig. 32.1Setting a breakpoint Fig. 32.2Starting the test run Fig. 32.3Removing a breakpoint Fig. 32.4Step in Fig. 32.5Step over Fig. 32.6Step out Fig. 32.7Execution paused at the first node of the second test case Fig. 32.8"Skip over"Fig. 32.9"Skip out"Fig. 32.10Debugger options: stop test on error Fig. 32.11QF-Test pauses on error Fig. 32.12Error message Fig. 32.13Update Check node with received data Fig. 32.14Corrected Check node

33Variables and Procedure Parameters (Mobile)

Fig. 33.1Two almost identical test steps Fig. 33.2Procedure with hard-coded value Fig. 33.3Details of a procedure node Fig. 33.4'Check text' node Fig. 33.5Procedure call to "checkFinalPrice" in the second procedure Fig. 33.6Variable definitions Fig. 33.7Popup menu for "Adjust parameters of references"Fig. 33.8Variable Definitions table shows the wrong value Fig. 33.9Continue execution from here Fig. 33.10Details of the Set variable node Fig. 33.11Procedure with return value

34The Standard Library (Mobile)

Fig. 34.1The Standard Library

35Control structures (Mobile)

Fig. 35.1Setup Sequence with if-else structures Fig. 35.2Wait for component to appear writes the result into the variable "notLoggedIn"Fig. 35.3If node evaluates the variable Fig. 35.4The new test case Fig. 35.5Details of the Check items node

37Data-driven Testing: Running one Test case with different test data

Fig. 37.1Traditional way of data-driven testing Fig. 37.2Traditional way with a nested Test set Fig. 37.3Data table dialog Fig. 37.4The filled data table Fig. 37.5Test set with Data driver Fig. 37.6Using the $(discount) parameter Fig. 37.7Full data table Fig. 37.8Name for run log and report attribute Fig. 37.9Run log with different names per Test case

38Dependencies: Automatically ensuring correct prerequisites for each Test case

Fig. 38.1First Test set of dependencies_work.qft Fig. 38.2First Test set of dependencies_work.qft Fig. 38.3Sample test suite with the first Dependency Fig. 38.4The run log of the execution Fig. 38.5Procedure startStop.startApplication Fig. 38.6The test suite with a Dependency reference Fig. 38.7Ensuring prerequisites for Test case 'Discount 15'Fig. 38.8'vehicles dialog opened' Dependency Fig. 38.9Implementation of specified test cases Fig. 38.10Run log of nested Dependencies Fig. 38.11Test-suite of Error handler Fig. 38.12Dependency with Error handler Fig. 38.13Run log for Dependency with Error handler Fig. 38.14Try-catch nodes in each Test case Fig. 38.15Test-suite with Catch Fig. 38.16Run log of a Dependency with Catch

39Automated creation of basic procedures

Fig. 39.1Screenshot of test suite Fig. 39.2The test suite automated_procedures_work.qft Fig. 39.3The recorded procedures Fig. 39.4The test suite containing the procedures Fig. 39.5The procedures for all panels Fig. 39.6The current configuration Fig. 39.7The own configuration file Fig. 39.8The checkText procedure Fig. 39.9The checkText procedure with parameters Fig. 39.10Using the <COMPID> place holder Fig. 39.11Your first automatically created procedures Fig. 39.12The configuration for the current text Fig. 39.13The created procedures with the current text Fig. 39.14The template for container procedures Fig. 39.15Usage of @FORCHILDREN tag Fig. 39.16The created container procedures Fig. 39.17Configuration of <CCURRENTVALUE>Fig. 39.18Test-suite using <CCURRENTVALUE>Fig. 39.19Parameters for container procedures Fig. 39.20Parameters for container procedures in test suite

List of figures