Product Verification and Testing
What is a test? Why should tests be executed for a product? How much tests are necessary?
What is the focus of the tests? What types of tests exist?
This are some off
your questions you might have at the moment. We will answer your questions on the following
pages.
What is a test? What is Verification?
Testing is a process consisting of several steps with the goal to find and document errors
in a product.
Verification
is a synonym for testing and
it is used in the same fields.

Figure 1:test process
Why should You verify (test) a product?
Tests are necessary to guarantee a good quality of a product and helps to reduce and minimize
the costs of a project. How that, You are asking now. Because the later in a project a error is
found, the more expensive is it to correct. More steps of the process has to be executed again,
perhaps the time plan has to be changed, deliveries delayed or the customer has seen the error
and contract penalties has to be paid.
How many tests are necessary and what should be the focus?
The number of tests differs from product to product. They depends on the complexity and
the focus of the costumer. Do you need performance or stability or ...
Thus the test coverage and the test types must be coordinate with you and a
Test Plan and
Test Specification
has to be written.
What types of tests exists?
Depending on product and costumer several kinds of testing exist which the product should pass
through:
- Black box testing
- White box testing
- Block / unit testing
- Functional testing
- Freehand testing
- Duration testing
- Stress testing
- Performance testing
- Installation testing
- Break & destroy testing
- System integration testing
- End-to-end testing
- Regression testing
- Acceptance testing
- Usability testing
|