Testers don’t have the luxury of a friendly group of people checking our work. Instead we get an angry mob with torches and pitch forks. We have to be honest about our limitations. It’s better you reveal them at the beginning, then get bitten by them at the end.
As a rule: If you’re testing something that you can’t explain to someone else, then you probably don’t understand enough to effectively test it.
How do you approach testing something you don’t understand?
Find people who understand it better than you. Talk to them. If you can’t find real people, find Google. Regardless of your source, cross reference information and consider the author’s bias.
There are fundamental techniques in testing that apply to most problems. Use them to explore, break it down and ask good questions. A common testing pattern is:
Then expected thing
Use this to think about what you need to set up, what you need to do and what results you should expect.
Since we can’t know everything we’re always out of our depth to some extent. So don’t panic. We have touched on three techniques to approach this problem: be honest, find someone who can help and fall back on your testing fundamentals.
Sometimes the most intelligent thing you can say is “I don’t know”.