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?
5 comments:
Subscribe to:
Post Comments (Atom)
RSS
User A , oens in edit mode makes some changes , does not save.
Opens the same in edit mode and makes changes and saves and close the first one w/o saving. and opens to see if the saved changes has been saved
UserA opens ItemA in edit mode, makes changes, and cancels out of edit mode.
UserA opens ItemA in edit mode, makes changes, save changes, closes ItemA, opens ItemA, makes new changes, saves changes.
UserA opens ItemA in edit mode, makes changes, save changes, closes ItemA, opens ItemA, makes new changes, cancels changes.
UserA opens ItemA and attempts to edit in non edit mode.
UserA opens ItemA in edit mode and removes all information, saves changes.
UserA opens ItemA in edit mode, adds unexpected customer characters, saves changes.
Michele,
I like your second test. One time I tested an app that had that bug. When UserA editted ItemA on the second try, the new info never saved back to the DB.
Hi eric, u r posts are really excellent
This is a great post about software testing. Those who are engaged in such are surely grateful of this. Thanks for sharing.