(That's a picture of a stale hamburger bun. My wife hates when I store bread on top of the refrigerator)


Think about your AUT. Is it possible for a user to see something on their screen that has been altered since the last time their screen refreshed? If so, you’re in luck. You can execute some stale data tests that may be fruitful.


Think of an item that can be edited. Let's call it "ItemA".

1. UserA opens the UI, and sees ItemA.
2. UserB opens the UI, and modifys ItemA. (now UserA is looking at a stale item.)
   
3. UserA attempts to modify ItemA.
   

Expected Results: UserA is not able to modify the stale version of ItemA. A user message explains this to the user and helps them figure out what to do next.


Much of this will depend on how locking is handled by your AUT. However, if you’re creative enough with various types of updates to ItemA, you’ll probably find some unhandled scenarios. For example: can you drag and drop ItemA? Can you delete it? Does ItemB reference a stale version of ItemA (mess with ItemB then)?

If you are able to find a bug with this technique, please share your test as a comment.

Happy testing!