Information Technology Reference
In-Depth Information
upgrade occurs. Regression testing is applied here so that test cases generated during
system development are reused or used after any modifications.
19.7.1
Test Data-Generation Testing
This type of testing exercises the software input and provides the expected correct
output. It can be done by two popular approaches: the black box strategy and the
white box strategy.
The black box, which is classified as a functional analysis for the software, only
considers the external specifications of the software without any consideration of its
logic, control, or data flow. It mainly concerns the selection of appropriate data as per
functionality and testing it against the functional specifications to check for normal
and abnormal behavior of the system. The tester is needed to be thorough with the
requirement specifications of the system, and the user should know how the system
should behave in response to any particular action. There are many testing types that
fall under the black testing strategy such as recovery testing, usability testing, alpha
testing, beta testing, and so on.
On the other hand, white box testing, which is classified as a structural analysis for
the software, only concern testing the implementation, internal logic, and structure
of the code. It should be used in all phases of the development cycle. It is mainly
used to find test data that will force sufficient coverage of the structures present in
the formal representation (Adrion et al., 1982). The tester has to deal with each code
unit, statement, or chuck of code and find out which one is not functioning correctly.
19.7.2
Traditional Manual V&V Testing
Desk checking is going over a program manually by hand. It is the most traditional
means for program analysis, and thus, it should be done carefully and thoroughly. This
can be done with many techniques such as walk-through, inspections, and reviews.
Requirements, specifications, and code always should be hand analyzed by walk-
through and/or inspections as it is developed, which requires teamwork directed by a
moderator and including the software developer.
19.7.3
Proof of Correctness Testing Strategy
This type of testing is classified as the most complete static analysis. It reduces step-
by-step reasoning that was mentioned in the previous method with inspection and
walk-through. This method works as a mathematical logic to prove the consistency of
the program with its specifications and requirements. Furthermore, for a program to
be completely correct, it also should be proved to be terminate. Proof of correctness
includes two approaches: a formal approach, which is the mathematical logic and
the ability of expressing the notion of computation, and the informal approach,
which requires the developer to follow the logical reasoning behind the formal proof
techniques, leaving aside the formal proof details.
Search WWH ::
Custom Search