Guests Judy Mosley and Simon Tomes discuss personal growth, communication, and quality in software development, highlighting the importance of aligning quality with business risks and goals. Religious techniques such as retrospectives, risk scenarios, and decision-making are presented as solutions to addressing and mitigating these risks.

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=o115ktpcw7
• Published: 2026-01-30T15:48:52Z
• Duration: 49:59
• Author: Unknown

Overview

The podcast focuses on themes related to personal and professional growth within the quality and software testing fields. It encourages individuals to set and share personal goals, offering examples from community members and introducing a challenge to post goals online. The discussion also highlights the recent addition of a new module in the Software Quality Engineering Certificate program, which examines the evolving role of quality engineers in various contexts and how testing strategies should align with business risks. Real-world instances of significant bugs affecting major contracts are shared, emphasizing the importance of analyzing “bugs in the wild” to improve testing practices.

The episode further explores strategies for cultivating a quality-driven culture, the effectiveness of retrospectives, and the importance of framing quality in terms of its overall impact on software defects. It includes personal reflections on testing experiences and leadership development, as well as updates on new features of the Ministry of Testing platform, such as progress and activity reports. Insights into the potential of AI in quality engineering are shared, alongside discussions on the challenges of being heard in professional environments. The overall message reinforces the value of community and collaboration as key drivers of progress in the field.

What If

• What if you started a “Quality Narrative Challenge” in your project with peers?
  Concrete move: Map your project’s quality narrative by defining three key stories linking your work to business risks, user impact, and team goals. Share these stories in your team’s Slack channel weekly.
  Why now: The text emphasizes the need to align quality with business objectives and stakeholder understanding. This approach helps bypass the “Cassandra dilemma” by making quality visible through tangible narratives.
  Expected upside: Improved stakeholder buy-in, faster risk prioritization, and a shared language for quality discussions that reduce recurring issues in retrospectives.

• What if you integrated AI-powered test automation tools into your workflow this quarter?
  Concrete move: Experiment with Playwright agents or self-healer tools for 2 weeks, using them to auto-generate tests for 20% of your feature work. Track time saved and error rates.
  Why now: The text highlights the speaker’s experimentation with Playwright agents and Darias article on AI in QE, showing practical value in AI as a productivity multiplier.
  Expected upside: Reduced manual test maintenance, faster feedback loops, and capacity to focus on higher-level quality decisions rather than routine tasks.

• What if you launched a “Goal Setter” peer accountability system for your solo project?
  Concrete move: Set 3 specific, measurable goals (e.g., “Complete automation for X feature by 12/15”) and share them with a trusted peer or community (e.g., GitHub discussions, MOT forums). Check in weekly.
  Why now: The text underscores the power of public commitment to accountability (e.g., Judys personal goals, the MOT badge challenge). Visibility creates motivation and learning from others journeys.
  Expected upside: Increased focus on long-term progress over “showing up,” reduced burnout, and community-driven feedback loops to refine your approach.

Takeaway

• Implement a “Quality Narrative” Framework
  Create a coherent story linking your testing efforts to business risks and project goals. Use this to align stakeholders, document progress in performance reviews, and propose a POC to turn test reports into strategic quality insights (e.g., using Playwright agents or self-healers for automation).

• Participate in the MOT “Goal-Setter Challenge”
  Share your personal/professional goals (e.g., automation improvements, learning paths) on ministryoftesting.com with the hashtag #mydashgoals. This builds visibility, accountability, and community engagement while earning a badge to track progress.

• Leverage “My Reports” for Career Growth
  Utilize the newly launched “My Reports” feature on the MOT platform to track your progress in courses, community involvement, and articles read. Use this data during performance reviews or job applications to quantify your learning and contributions.

• Experiment with AI in QE Practices
  Test AI tools like AI-powered test generators or self-healers (e.g., Playwright agents) to streamline automation. Share results with the community via articles or social media, inspired by Daria Zions approach to integrating AI as a collaborative tool in quality engineering.

• Conduct Regular Retrospectives with Stakeholders
  After completing sprints or projects, hold retrospectives with your team and key stakeholders to reflect on quality challenges and outcomes. Use real-world bug stories (e.g., from minutetesting.com) to frame discussions around risks and long-term impacts, ensuring continuous learning and alignment.