IEEE 29119-4-2015 pdf download

IEEE 29119-4-2015 pdf download.Software-and systems-engineering一Software testing-Part 4:Test techniques.
EXAMPLE 1 In state transition testing, if there isa requirement to cover all states then the entire state model could be the test condition. Alternatively, if there is a requirement to cover specific transitions between states, then each transition could be a test condition.
In addition, since some techniques share underlying concepts, their definitions contain similar text. EXAMPLE 2 Both equivalence partitioning and boundary value analysis are based on equivalence classes.
In the test case design step (TD4) of each technique, test cases that are created may be “valid” (i.e. they contain input values that the test item should accept as correct) or “invalid” (i.e. they contain at least one input value that the test item should reject as incorrect, ideally with an appropriate error message). In some techniques, such as equivalence partitioning and boundary value analysis, invalid test cases are usually derived using the “one-to-one” approach as it avoids fault masking by ensuring that each test case only includes one invalid input value, while valid test cases are typically derived using the “minimized” approach, as this reduces the number of test cases required to cover valid test coverage items (see 5.2.1.3 and 5.2.3.3).
NOTE Invalid cases are also known as “negative test cases”.
Although the techniques defined in ISO/IEC/IEEE 29119-4 are each described in a separate clause (as if they were mutually exclusive), in practice they could be applied in a blended way.
EXAMPLE 3 Boundary value analysis could be used to select test input values, after which pair-wise testing could be used to design test cases from the test input values. Equivalence partitioning could be used to select the classifications and classes for the classification tree method and then each choice testing could be used to construct test cases from the classes.
The techniques presented in ISO/IEC/IEEE 29119-4 could also be used in conjunction with the test types that are presented in Annex A. For example, equivalence partitioning could be used to identify user groups (test conditions) and representative users (test coverage items) from those groups in test cases that are to be tested during usability testing.
The normative definitions of the techniques are provided in Clause 5. The corresponding normative coverage measures for each technique are presented in Clause 6. This is supported by informative examples of each technique in Annexes B. C. D and E. Although the examples of each technique demonstrate manual application of the technique, in practice, automation can be used to support some types of test design and execution (e.g. statement coverage analyzers can be used to support structure- based testing). Annex A provides examples of how the test design techniques defined in this standard can be applied to testing the quality characteristics that are defined in ISO/IEC 25010.
5.2 Specification-Based Test Design Techniques
5.2.1 Equivalence Partitioning
5.2.1.1 Derive Test Conditions (TD2)
Equivalence partitioning (BS 7925-2:1998; Myers 1979) uses a model of the test item that partitions the inputs and outputs of the test item into equivalence partitions (also called “partitions” or “equivalence classes”), where each equivalence partition shall be defined as a test condition. These equivalence partitions shall be derived from the test basis, where each partition is chosen such that all values within the equivalence partition can reasonably be expected to be treated similarly (i.e. they may be considered “equivalent”) by the test item. Equivalence partitions may be derived for both valid and invalid inputs and outputs.
EXAMPLE For a test item expecting lowercase alphabetical characters as (valid) inputs, invalid input equivalence partitions that could be derived include equivalence partitions containing integers, reals, uppercase alphabetical characters, symbols and control characters, depending on the level of rigour required during testing.