The negative test (also called provocation test, robustness test, falsifying test or bad test ) is an extension of the positive test . The negative test checks whether the application reacts as expected (i.e. without program termination) to (incorrect) input or operation that does not meet the requirements of the application , e.g. B. by an error message . In the negative test, invalid values are deliberately entered, masks are not or only incompletely filled out, interfaces are supplied with incorrect values or the database is disconnected. The test case therefore checks for "correct" processing in the event of incorrect handling.
The purpose of the negative test is to prove that the application reacts robustly to operating errors . This ensures that the application is safe against incorrect operation and technical malfunctions.
The negative test case has already been fulfilled if an error message appears (e.g. "Entry is incorrect"). However, this says nothing about the user friendliness of the error message. An error message such as "The date must be in the future" or "The date must be greater than the start date" or "The value must be greater than 0.00 and less than 500.01" would be user-friendly.
- Integration test
- Module test
- Condition based test
- Keyword "Software FMEA" in: Failure Mode and Effects Analysis
- Correctness (computer science)
- Model-based testing
- Black box test
- Manuel Arnold: Soft (ware) skills in testing: To err is human. Java magazine 13th vol., 5, 2010, p. 84