Code coverage is according to ISTQB definition: "an analysis method that determines which parts of the software have been executed or covered by the test suite and which parts have not been executed." (statement coverage, decision coverage, condition coverage).
Code coverage ensures that all code has been executed and tested at a component, system or integration level.
LO-4.4.2 Explain the concepts of statement and decision coverage, and give reasons why these concepts can also be used at test levels other than component testing (e.g., on business procedures at system level) (K2)
Statement coverage has to be optimized in order to ensure that maximum program statements have been executed with minimum test cases. However, it's worth to note that statements can depend on a logical structure (control flow diagram/graph) like do while, if then else, do until, go to and can drive multiple combination.
Decision testing aims to confirm that all decisions of a program have been executed at least once, it is therefore key in successful component testing as decision coverage implies branch and statement coverage.
LO-4.4.3 Write test cases from given control flows using statement and decision test design techniques (K3)
For this sections, you have essentially to practice: translate code into flow diagram and determine the root causes.
LO-4.4.4 Assess statement and decision coverage for completeness with respect to defined exit criteria. (K4)
No comments:
Post a Comment