1
Download PDF version - QF-Test
Transcript
4.3. Recording checks Counter Icon 33 Description Total number of test-cases. This counter value starts with a ’>’ symbol in case there are skipped test-sets. Number of test-cases with exceptions. Number of test-cases with errors. (318) Number of test-cases with expected errors. Expected to fail if... marks a test-case expected to fail. Number of successful test-cases. (318) Number of skipped test-cases. A test-case is skipped when its (optional) Condition fails. This counter value starts with a ’>’ symbol in case there are skipped test-sets. (325) Number of skipped test-sets. A test-set is skipped when its (optional) Condition fails. Number of not implemented test-cases. A test-case is not implemented when it doesn’t contain nodes that were executed during the test-run. Number of executed test-cases. Percent test-cases passed. Table 4.1: Test result counter in the status line The final test result counts also appear in the report which can be created for any test (129) run. Reports are discussed in chapter 15 . Note (62) The counter values above can also be accessed as variables during the test-run. (728) A TestRunListener can help to keep track of counter values and trigger dependent actions. 4.3 Recording checks Though it can be quite entertaining to record sequences and watch the magic dance of the SUT as they are played back, the task at hand is to find out whether the SUT (469) actually works as expected. This is where checks come into play. The most common (470) check, the Check text node, reads the text displayed by a component, e.g. a text field, and compares it to a given value. If the values differ, an error is signaled. (469) How checks work is explained in detail in the Reference manual . There is a range (488) available from simple text check to advance Check image and even custom check (715) types can be implemented. Here we are going to concentrate on the most convenient way to create checks, which is to record them. While recording, the SUT is in record mode, which means that all events are collected and sent to QF-Test. With the help of the check button or by selecting Record→Check you can bring it into check mode, recognizable through the different
