Chances are, your AUT has some items that can be deactivated somewhere; probably in an admin screen. This is a great place to catch some serious bugs before they go to prod. Here are a few tests you should execute.
Start with the easy ones:
1. Make ItemA “in use” (something in your AUT depends on itemA).
2. Attempt to deactivate ItemA.
Expected Results: ItemA cannot be deactivated. User communication indicates ItemA is in use.
1. Deactivate an unused item (call it ItemA).
2. Attempt to use ItemA somewhere (e.g., does ItemA display in a dropdown menu?).
Expected Results: ItemA cannot be used because it is unavailable.
Then try something more aggressive:
1. UserA opens a UI control that displays ItemA as a potential selection.
2. UserB deactivates ItemA (e.g., from an admin screen).
3. UserA selects ItemA from the UI control.
Expected Results: ItemA cannot be used by UserA because it is unavailable. Communication to UserA explains ItemA is inactive.
Got any good variations?
RSS
Popular Posts
-
After attempting to use Microsoft Test Manager 2010 for an iteration, we quickly decided not to use it. Here is why. About 3 years ago we ...
-
I recently read about 15 resumes for tester positions on my team. None of them told us anything about how well the candidate can test. Her...
-
Data warehouse (DW) testing is a far cry from functional testing. As testers, we need to let the team know if the DW dimension, fact, and b...
-
The first time I saw James Whittaker was in 2004 at an IIST conference . He dazzled us with live demos of bugs that were found in public so...
-
Many testers have chosen to make their jobs stressful by taking on more responsibilities than they should, obscuring their skills with those...
Blog Archive
Who am I?
- Eric Jacobson
- Atlanta, Georgia, United States
- My typical day: get up, hit the gym, listen to public radio, drink strong coffee, perform virgin software tests, break for lunch and a Euro-board game with the devs, log more bugs, walk the dogs, enjoy a meal with Melissa, an IPA, and a Netflix, look forward to a weekend with a cave trip or woodworking project.
My other passion is woodturning.
Test blogs I try to read
Depending on how the UI is setup, you can also do the third scenario with just one user (ie. instead of involving UserB).
The UI just needs to be able to support delayed saving instead of immediate saving upon any selection changes.
Crayola coder,
Ah, you mean something like a form exists on the UI, where UserA can select ItemA, go disable ItemA, then navigate back to said form and click a Save button, right?
In other words, the save is triggered by something other than the action of selecting ItemA.
si. descramble for module: mfrosat