Section 173 · Chapter 20, The Practical Playbook
Make Testing Interesting
Quality work gets better when people actually want to read the failures.
make interesting
What to do
- Do not make a test cute at the expense of clarity.
- Do not hide severity behind jokes.
- Do not let personality make a failure seem less important than it is.
- Use AI to test more, test differently, and test earlier.
- Use it to summarize clusters, title incidents, rewrite failure reports for different audiences, generate readable scenario names, and explain why a weird case matters.
Evidence to preserve
- Preserve the inputs, versions, configurations, raw outcomes, and results for make interesting needed to reproduce work on Make Testing Interesting.
- Report results for make interesting by relevant slice, separate blocker failures from averages, state uncertainty and blind spots, and connect the result to a release decision.
Expert note
When the system matters, treat interesting test design as part of quality communication. A useful eval artifact has technical fidelity and human salience. It preserves exact inputs, outputs, versions, scores, traces, and statistics, but also gives people names, narratives, and summaries they can remember.
Continue the conversation
Apply this to your context.
Save your product context once, then open a focused conversation that combines it with this concept.
Cite this page
Jason Arbon. "Make Testing Interesting." Testing AI Knowledge Edition, section 173.
https://jarbon.ai/testing-ai/knowledge/ch173-make-interesting.html