In Part 1 of this post, I defined positive and negative testing and gave simple, real life examples of what happens if both are not utilized. Side effects may be found, possible alternate uses may be discovered, perhaps a whole rethink of the product is required, or less frequently that the product works exactly as intended and it is ready for market.
In this part of the blog, I’ll provide some simple, generic examples of how we can use positive and negative testing with our solutions here at ToolBox. We know that a few issues will always be found but we also know that by using both positive and negative testing we can reduce the number found.
Positive Testing at ToolBox Solutions
- Add 5 specific products to only Client A and make sure that Client A can see all 5 products
- Add a new user (User1) associated to Client C and make sure that User1 can log in successfully to Client C’s site
Negative Testing at ToolBox Solutions
- Test to make sure that Client B cannot see the 5 products added specifically to Client A
- Test to make sure that User1 cannot log in to Client A or Client B’s site
Sometimes testing has a ripple effect. For example, the text field we are testing might accept numbers and letters but then fail horribly when a period is added to the end. Did it fail because we entered one more character than was expected? Or because it was not a number or a letter? Or because of some completely unexpected reason? What is that reason? How can we prevent it from happening again?
Once we find one issue, we go digging for more…leading to more positive and more negative testing. Testing involves asking a lot of questions, seeking answers, making guesses, finding proof. And there you have the yin and yang of testing…two very different concepts that work together to make sure that the ToolBox Solutions applications we release are complete.