Overview
The Expert's Toolkit
Heuristics aren't rigid rules; they are fallible methods for problem-solving. They help QAs navigate complex systems without a perfect map.
Heuristics are essential for Exploratory Testing. They provide a 'starting point' when you are faced with a new feature and no documentation.
Our Recommendation
9/ 10
Best Practices
Dos and Don'ts
Avoid common mistakes that can lead to flaky tests and maintenance nightmares.
What to do
- •Use heuristics to brainstorm test ideas during sprint planning.
- •Teach junior QAs common heuristics like 'Zero, One, Many' for data testing.
- •Combine multiple heuristics to broaden your testing scope.
Common Pitfalls
- •Don't treat a heuristic as a checklist; it's a prompt for thinking, not a substitute for it.
- •Don't use the same heuristics for every project; adapt them to the context.
The Details
James Bach’s SFDPOT Heuristic
One of the most famous heuristics in QA is SFDPOT (pronounced 'San Francisco Depot'). It stands for:
- Structure (What is it made of?)
- Function (What does it do?)
- Data (What does it process?)
- Platform (Where does it run?)
- Operations (How will it be used?)
- Time (When does it do it?)
Using this as a guide ensures a highly holistic testing approach.