Scribd
Upload
27 views

Testing FAQs15

Dynamic analysis during test execution revealed that some test coverage objectives were not achieved. Further analysis was needed to determine why - it could be infeasible paths, unreachable code, or insufficient test cases. The coverage completion step aims to refine test specifications and add new test cases to improve coverage, though viewing the code may be necessary. The goal is to minimize reliance on this step and focus on thorough analysis and specification during test design.

Uploaded by

PRINCEBLR
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
27 views

Testing FAQs15

Dynamic analysis during test execution revealed that some test coverage objectives were not achieved. Further analysis was needed to determine why - it could be infeasible paths, unreachable code, or insufficient test cases. The coverage completion step aims to refine test specifications and add new test cases to improve coverage, though viewing the code may be necessary. The goal is to minimize reliance on this step and focus on thorough analysis and specification during test design.

Uploaded by

PRINCEBLR
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Dynamic analysis during execution of the test procedure will yield a measure of test

coverage, indicating whether coverage objectives have been achieved. There is


therefore a further coverage completion step in the process of designing test
specifications.
Coverage Completion
Depending upon an organizations standards for the specification of a unit, there may
be no structural specification of processing within a unit other than the code itself.
There are also likely to have been human errors made in the development of a test
specification. Consequently, there may be complex decision conditions, loops and
branches within the code for which coverage targets may not have been met when
tests were executed. Where coverage objectives are not achieved, analysis must be
conducted to determine why. Failure to achieve a coverage objective may be due to:
Infeasible paths or conditions - the corrective action should be to annotate the
test specification to provide a detailed justification of why the path or condition
is not tested. AdaTEST provides some facilities to help exclude infeasible
conditions from Boolean coverage metrics.
Unreachable or redundant code - the corrective action will probably be to
delete the offending code. It is easy to make mistakes in this analysis,
particularly where defensive programming techniques have been used. If
there is any doubt, defensive programming should not be deleted.
Insufficient test cases - test cases should be refined and further test cases
added to a test specification to fill the gaps in test coverage.
Ideally, the coverage completion step should be conducted without looking at the
actual code. However, in practice some sight of the code may be necessary in
order to achieve coverage targets. It is vital that all test designers should
recognize that use of the coverage completion step should be minimized. The
most effective testing will come from analysis and specification, not from
experimentation and over dependence upon the coverage completion step to
cover for sloppy test design.
Suitable techniques:
- Branch testing
- Condition testing
- Data definition-use testing
- State-transition testing

You might also like