Structure-based
technique in software testing
·
Structure-based techniques serve
two purposes: test coverage measurement and structural test case design.
·
They are often used first to
assess the amount of testing performed by tests derived from
specification-based techniques, i.e. to assess coverage.
·
They are then used to design
additional tests with the aim of increasing the test coverage.
·
Structure-based test design
techniques are a good way
of generating additional test cases that are different from existing tests.
·
They can help ensure more breadth
of testing, in the sense that test cases that achieve 100% coverage in any measure will be
exercising all parts of the software from the point of view of the items being
covered.
Test
coverage in software testing
Test coverage measures the amount of testing performed
by a set of test. Wherever we can count things and can tell whether or not each
of those things has been tested by some test, then we can measure coverage and
is known as test coverage.
The basic coverage measure is where the ‘coverage
item’ is whatever we have been able to count and see whether a test has
exercised or used this item.
There is danger in using a coverage measure. But, 100%
coverage does not mean
100% tested. Coverage techniques measure only one dimension of a
multi-dimensional concept. Two different test cases may achieve exactly the
same coverage but the input data of one may find an error that the input data
of the other doesn’t.
Benefit of code coverage
measurement:
·
It creates additional test cases
to increase coverage
·
It helps in finding areas of a
program not exercised by a set of test cases
·
It helps in determining a
quantitative measure of code coverage, which indirectly measure the quality of
the application or product.
Drawback of code coverage
measurement:
·
One drawback of code coverage
measurement is that it measures coverage of what has been written, i.e. the
code itself; it cannot say anything about the software that has not been written.
·
If a specified function has not
been implemented or a function was omitted from the specification, then
structure-based techniques cannot say anything about them it only looks at a
structure which is already there.
Types of coverage
There are many types of test coverage. Test coverage
can be used in any level of the testing. Test coverage can be measured based on
a number of different structural elements in a system or component. Coverage
can be measured at component testing level, integration-testing level or at
system- or acceptance-testing levels. For example, at system or acceptance
level, the coverage items may be requirements, menu options, screens, or
typical business transactions. At integration level, we could measure coverage
of interfaces or specific interactions that have been tested.
0 comments:
Post a Comment
Note: only a member of this blog may post a comment.