1. Purpose

2. Benefits of negative testing

3. Parameters for writing Negative test cases

4. References

Negative testing is a method of testing an application or system that ensures that the plot of the application is according to the requirements and can handle the unwanted input and user behavior. Invalid data is inserted to compare the output against the given input. Negative testing is also known as failure testing or error path testing. When performing negative testing exceptions are expected. This shows that the application is able to handle improper user behavior. Users input values that do not work in the system to test its ability to handle incorrect values or system failure.

Purpose

• The purpose of negative testing is to prevent the application from crashing and it also helps improve the quality of an application by detecting defects.
• Negative testing helps you to improve the testing coverage of the application.
• Negative testing makes the application more stable and reliable.
• Negative testing together with positive testing allows users to test the application with any valid or invalid) input data.

Benefits of negative testing

Negative testing is done to check that product deals properly with the circumstance for which it is not programmed. The fundamental aim of this testing is check that how bad data is taken care of by the systems, and appropriate errors are shown to client when bad data is entered. Both positive and negative testing play important role. Positive testing ensures that application does what it is implied for and perform each function as expected. Negative testing is opposite of positive testing. Negative testing discovers diverse approaches to make the application crash and handle the crash effortlessly.

• If there is a text box that can only take numeric values but the user tries to type a letter, the correct behavior would be to display a message such as "(Incorrect data) Please enter a number."
• If user is to fill the name field, there are ground rules that name text is mandatory to fill, name box shouldn't have values other than letters (no numeric values and special characters). Negative test cases could be a name containing numeric values or special characters. The correct behavior of the system would be to not display those invalid characters.

Parameters for writing Negative test cases

There are two basic techniques that help to write the sufficient test cases to cover the most of the functionalities of the system. Both these techniques are used in positive testing as well.

The two parameters are:

Boundary indicates limit to something. In this parameter, test scenarios are designed in such a way that it covers the boundary values and validate how application behaves on these boundary values.

If there is an application that accepts Ids ranging from 0–255. Hence in this scenario, 0,255 will form the boundary values. The values within the range of 0–255 will constitute the positive testing. Any inputs going below from 0 and input going above from 255 will be considered invalid and will constitute negative testing.

References

• Rules of Rock-paper-scissors-lizard-Spock
• Rules of rugby union
• Rules of Rugby Union
• Rules of scope
• Rules of succession to the British throne
• Rules of the City of New York
• Rules of the Game (book)
• Rules of the Game: Master the Art of Attraction in 30 Days
• Rules of the Game (Neil Strauss)
• Rules of the King's Bench
• Rules of the road (disambiguation)
• Rules of the road in the People's Republic of China
• Rules of the Supreme Court 1965
• Rules of War
• Rules of water polo
• Rules (Shakira song)
• Rules to consider/Confer in e-mail debate
• Rules to consider/Do not include primary sources debate
• RulesToConsider/Establish Context
• Rules to consider/Make links relevant
• Rules to consider/Make links relevant talk
• Rules to consider/Pay attention to spelling debate
• Rules to consider/Usefulness for readers debate
• Rules to consier/Make only links relevant to the context debate
• Rule Supreme