Quality Hunting: Testing for Information Instead of Bugs - Rik Marselis
Categories: Podcasts , Software Testing Unleashed
Quality hunting is a structured, collaborative approach to software testing that prioritizes gathering meaningful insights on usability, accessibility, and overall system quality over merely finding defects. Teams work in short, time-boxed sessions to explore systems, report actionable findings, and support informed decision-making in DevOps environments.
Software Testing Unleashed
Software Testing Unleashed - hosted by Richard Seidl. Different guest per episode. The official Show notes contain a comprehensive overview of the episode. Released as audio and video.
- https://www.richard-seidl.com/en/testing-unleashed
- https://www.youtube.com/playlist?list=PL48Mbm-L0hjB1OdwYi9h7jrq9t352-Zk_
Episode Details
- Show Notes: https://www.richard-seidl.com/en/podcast/quality-hunting-method
- Published: 2026-10-08T04:00:00Z
- Duration: 00:18:14
- Author: Richard Seidl | Software Development & Testing Expert
Overview
The podcast discusses the concept of “quality hunting” as a strategic and structured alternative to traditional bug hunting in software testing. Rather than focusing solely on identifying defects, quality hunting emphasizes gathering meaningful information about a system’s overall quality, particularly from the user’s perspective. This approach encourages teams to define in advance what information stakeholders need, how to collect it, and how to present findings in a structured, actionable way. It values insights on usability, accessibility, and other non-functional aspects, aiming to provide decision-makers with knowledge and confidence in the system.
Quality hunting is presented as a collaborative, time-boxed activity involving small teams - typically four members - who explore the system in an exploratory manner and report their findings within a short timeframe, such as three hours. Multiple teams can work simultaneously, generating diverse insights quickly and enabling stakeholders to gain firsthand understanding. Unlike bug hunts that prioritize the number of issues found, quality hunting focuses on the relevance and depth of information, promoting critical thinking and preparation. The practice is integrated into frameworks like the ISTQB syllabus and supports DevOps environments by balancing automation with human judgment, ultimately fostering better-informed decisions and improved system quality.
What If
-
What if you reframed your next testing cycle as a quality hunting mission instead of a bug hunt?
- Move: Before starting your next feature test, define 3 - 5 key quality questions stakeholders care about (e.g., “Is this usable for a first-time user?”, “Does it feel reliable under slow network conditions?”). Design exploratory test sessions around answering these.
- Why Now?: Traditional bug counting doesn’t reduce stakeholder anxiety - clear quality insights do. With DevOps and CI/CD, decisions happen fast; you need to deliver actionable quality signals, not just defect lists.
- Expected Upside: You shift from being seen as a “bug reporter” to a “quality assessor,” increasing your influence in release decisions and building trust with product owners.
-
What if you ran a solo 90-minute quality hunting session before every production deployment?
- Move: Block 90 minutes pre-release to simulate real user journeys with specific quality goals (e.g., accessibility, clarity, speed). Document findings in a structured one-page report using screenshots, annotations, and plain-language judgments (e.g., “Good enough for launch with minor caveats”).
- Why Now?: Automated checks cover known risks, but miss emergent quality gaps. As a solo operator, your human judgment is the last line of defense - leverage it deliberately before each deploy.
- Expected Upside: You catch usability or perception issues that automation misses, reduce post-launch fire drills, and build a reputation for shipping “calm-inducing” releases.
-
What if you redesigned your test reports to answer stakeholder concerns, not just list observations?
- Move: Replace raw bug logs with a stakeholder-focused summary: start with a verdict (e.g., “Ready to launch with monitoring”), then support it with evidence grouped by quality attribute (usability, reliability, compliance). Use visuals and avoid technical jargon.
- Why Now?: Stakeholders are overwhelmed by data. In fast-moving solo or small-team environments, clarity accelerates decisions. The ISTQB and DevOps trends now emphasize communication over documentation.
- Expected Upside: Faster approvals, fewer follow-up questions, and increased confidence in your role as a quality gatekeeper - freeing up time for higher-value work.
Takeaway
- Define the specific quality-related information stakeholders need before starting any testing, ensuring your efforts align with decision-making needs.
- Structure your test reports from the beginning - focus on delivering actionable insights in clear formats (lists, prose, visuals) rather than raw bug lists.
- Conduct short, time-boxed testing sessions (under 3 hours) focused on real user perspectives, especially for usability and accessibility, to quickly generate high-value feedback.
- Integrate exploratory testing with predefined acceptance criteria (e.g., unit tests) to balance structured validation with adaptive, human-driven quality assessment.
- Prioritize non-functional aspects like usability and accessibility alongside functional testing, using stakeholder-centered goals to guide your approach and reporting.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.