Empty field submit.
[Moderators Edit so this can appear]
Empty field submit.
[Moderators Edit so this can appear]
State machine stress fuzzing testing
Performance/Load fuzzing testing
Do not overengineer and/or overtest
Simulating realistic user interactions extensively.
Follow ALL the links
(not just the nav bars)
Good old Bobby tables
Have you considered 508 compliance?
Shields up
(more than 1/2 of US users use ad blockers)
a little to the left
(check alignment on all pages)
High Contrast
(system setting will undo all your pretty)
Permissions testing
(I can’t tell you how many regression cycles I’ve seen people complete only with an admin user)
I’m a roles breaker
(directly go to pages role doesn’t have permission to)
I grant myself permission
(try to (d)escalate roles through the UI on your user)
Do it through the API
(a lot of APIs let you do things the UI won’t)
Hackerman!
(through dev tools monkey with fields and permissions)
Time out!
(test around user timeouts)
I ain’t got no cookie
(delete browser data and log in)
Who me?
(log in a 2 different users in the same browser, log in as the same user in 2 browsers)
Click count
(what are most users doing in your system? how many clicks to get to those?)
Fit check
(match the requirements to the software)
These were ones I didn’t see on the sheets.
@rosie I hope I’m doing it right, or am not too late.
Type and confirm just whitespace
Do it again but offline
Delete what’s just been deleted.
Validate user login with emoji.
Try visiting restricted routes directly.
PUT where POST is expected.
Let your Toddler take control
Here is some detailed information for Use a screen reader:
https://mindfultester.com/test-idea-number-1-part-1/