As the name suggests, destructive testing (DT) includes methods where your application is made to fail in an uncontrolled manner to test the robustness of the application and also to find the point of failure.
Basically the method involves interacting with the software incorrectly, for example entering data that is corrupt or in the wrong format, to determine whether the application would fail.
Destructive testing is performed under the most severe operating conditions and it is continued until the application breaks.
Apart from finding design weaknesses if any which may not show up under normal working conditions the main purpose of destructive testing is to determine the service life of the product.
For Destructive Testing, it is not necessary to have the knowledge of the original requirements of a software product.
However, some knowledge could help in developing a good testing strategy.
Why to do Destructive Testing?
- It helps to understand predictable software behavior when the software is put under improper usage.
- It helps to check the robustness of a software product.
What you check in Destructive Testing?
In Destructive Testing, you will check for following things:
- Proper input data.
- Proper output data.
- Improper input data.
- Proper software behavior.
- Improper software behavior.
- Improper usage