Test Case Categories
Form Locking Testing - Key Test Cases for Preventing Concurrent Edits in Web Applications
Form locking mechanisms prevent data conflicts in multi-user environments. This guide covers test cases for form locking functionality, including lock acquisition, release, timeout handling, and concurrent user scenarios.
| Nr | Test Idea | |
|---|---|---|
| 1 | Check if opening the form adds lock with correct data (lock time, locked by, etc) | |
| 2 | Check if opening component directly by URL adds the lock | |
| 3 | Check if another user can open the form while you have an active lock (maybe it should be possible but fields should be disabled) | |
| 4 | Check how locking works if you open the same page in another tab | |
| 5 | Check how page refresh affects the lock | |
| 6 | Check if leaving to other pages at you system removes the lock | |
| 7 | Check if closing the tab removes the lock | |
| 8 | Check if closing the browser removes the lock | |
| 9 | Check if there is a need for automatic lock removing after some time | |
| 10 | Check if locking is added when opening form from all the possible places in the application | |
| 11 | Check if only users can acquire lock or system can/should also acquire the lock (background jobs that work with same data) | |
| 12 | Check if system lock blocks users and if user lock blocks system |