Many of my notes from Hans Buwalda’s STPCon session are test design tips that can also apply to manual testing. One of my favorite tips was to remember to go beyond requirement-based testing. A good QA Manager should say “I know you have tested these ten requirements, now write me some tests that will break them”.
As testers, we should figure out what everyone else forgot about. These are the good tests. These are where we can shine and provide extra value to the team. One way to do this is to take a simple test and make it more aggressive.
Example Requirement: A user can edit ItemA.
Requirement-based Test: UserA opens ItemA in edit mode.
How can I make this test more aggressive? Let’s see what happens if:
- UserA and UserB both open ItemA in edit mode at the same time.
- UserA opens ItemA in edit mode when UserA already has ItemA in edit mode.
- UserA opens ItemA in edit mode, makes changes, goes home for the weekend, then attempts to save changes to ItemA on Monday.
- UserA opens ItemA in edit mode, loses network connectivity, then attempts to save ItemA.
What else can you think of?