Quality assurance strategies emphasize streamlining workflows, automation visibility, manual testing’s role in human-like issue detection, and fostering transparency in practices like “making the invisible visible.” The discussion highlights critical thinking, ethical AI integration, leadership accountability, and balancing innovation with accountability through collaboration and retrospection.

MOT This Week in Testing

MOT - This week in Testing - Varied hosts, group chat, often with community questions and involvement. Show notes have a full transcript.

• https://www.ministryoftesting.com/podcasts
• https://www.ministryoftesting.com

Episode Details

• Show Notes: https://www.ministryoftesting.com/podcasts/this-week-in-testing?wchannelid=czgwdadw2c&wmediaid=hix4m0wo7i
• Published: 2026-04-24T14:25:04Z
• Duration: 54:32
• Author: Unknown

Overview

The podcast discusses various topics related to quality assurance and software development practices. Key points include the formation of value streams to streamline production workflows, the role of quality coaching in driving low change failure rates, and efforts to simplify quality practices for non-specialists. Automation in mobile testing via cloud-based workflows is highlighted, along with the need to make automation processes visible to teams. Community themes emphasize “making the invisible visible” through transparency and self-awareness, alongside serendipitous connections formed through shared interests or backgrounds. The importance of manual testing is underscored for its ability to uncover human-like interaction issues, contrasted with automations limitations, while advocacy for human-centric practices like “human testing” is proposed.

Critical thinking in quality assurance is framed as central to improving software quality, emphasizing the need for testers to refine their thought processes rather than just technical skills. The discussion also addresses AIs role in development, acknowledging its potential to accelerate tasks like test generation while cautioning against overreliance due to risks of bias, inaccuracy, or misalignment with project goals. Leadership is highlighted as ultimately responsible for quality, with calls to prioritize quality through resource allocation and cultural shifts. The episode explores backlog management strategies, such as archiving outdated tasks to reduce “baggage” and prioritize active issues, and stresses collaboration through cross-team learning and shared ownership of problems.

Additional themes include the importance of peer recognition, fostering open dialogue for ethical AI use, and the balance between innovation and accountability. Challenges in risk communication, the value of retrospection for learning from failure, and the philosophical tension between AIs efficiency and human judgment are also addressed. The discussion concludes with an emphasis on ongoing conversations about AI, quality, and organizational practices, encouraging stakeholders to engage critically and collaboratively.

What If

• What if you created a simplified “Idiot’s Guide” to quality practices tailored for non-specialists in your team?
  Concrete move: Draft a step-by-step guide covering value streams, observability basics, and manual testing principles, using plain language and real-world examples.
  Why now: Leadership is actively seeking to understand quality coaching, and your teams low change failure rate shows a need for better communication.
  Expected upside: Reduce confusion about quality practices, align non-specialists with team goals, and position yourself as a thought leader in visible quality practices.

• What if you implemented a “backlog detox” to remove or archive obsolete tasks and bugs?
  Concrete move: Audit your backlog, delete tasks older than six months, and archive critical but outdated items with clear documentation.
  Why now: Teams are struggling with cluttered backlogs, and prior discussions highlight the need to prioritize active issues over historical baggage.
  Expected upside: Improve team focus on high-value tasks, reduce cognitive load, and create space for innovation by clearing out unproductive “baggage.”

• What if you introduced a monthly “manual testing ritual” to complement automation?
  Concrete move: Set aside dedicated time for exploratory manual testing, focusing on edge cases and user-like interactions, and document unique findings.
  Why now: The text emphasizes manual testings role in uncovering human-like issues and stress-relieving tasks like “rage clicking.”
  Expected upside: Enhance bug detection for edge cases, foster creativity in testing, and reinforce the value of human-centric practices in an increasingly automated landscape.

Takeaway

• Develop a simplified guide to explain quality practices to non-specialists, similar to the “idiots guide” mentioned in the text, to improve internal and team-wide understanding of quality processes.
• Automate mobile testing workflows using cloud-based tools to increase visibility and tangibility of automation efforts, as demonstrated by Judys recent work.
• Archive or delete outdated backlog items (e.g., bugs older than six months) to reduce “baggage” and prioritize current tasks, ensuring focus on high-value work as discussed in backlog management strategies.
• Integrate manual testing into your workflow to identify human-like edge cases and improve system understanding, treating it as a complementary practice to automation rather than a replaceable one.
• Engage in local or online tech community events (e.g., meetups in Edinburgh, San Francisco) to build peer connections, share knowledge, and collaborate on quality practices, leveraging the emphasis on community engagement and peer recognition.