I have no example but more of a tip; I recently saw people making songs to help with stuff like this. So a melody helps people remember things more often.
They use AI in order to create a catchy-song with lyrics specific to for example ISTQB in order to remember the things better by singing the song.
Simplist one I could think of. S was the hardest to come up with.
TEST T - Think, of all the things that could happen E - Explore, the software to discover all the things it can do, even if it shouldn’t S - Silly, what is the weirdest, silliest and out of the box thing can you try with it? T - Tell, people what you have found and why you think it might not be (pick one of these which fit your context) right, weird, wrong, odd, strange, false, misleading, distorted, immoral, concerning, broken, your own words or feelings.
When you come across a reproducible bug, be a prosecution lawyer. (Defend what is right)
When you come across an intermittent bug, be Sherlock Holmes. (Solve the mystery)
When you’re given a new system to test, (as Sebastian said) be a scientist. (Get experimental)
Spot the defects before users do. Hunt for edge cases and unexpected behaviors. Examine requirements to ensure full coverage. Reproduce issues consistently for better debugging. Log findings clearly for effective communication. Observe system behavior under different conditions. Confirm fixes don’t introduce new bugs. Keep learning and improving testing strategies.
Ugh these are all so good. Depending on what you need I have one that might also be useful in general for testers, and isn’t me just throwing things at a wall to see what stuck.
Having spent many years in testing, I could write extensively about “testing like a tester.”
However, the key distinction between a good tester and a mediocre one can be summed up in just a few words:
It’s the mindset to:
TEST T - Try to E - Explore the S - System T - Totally