Challenges in quality engineering, including flaky tests and mobile testing, are addressed alongside community-driven learning initiatives, AI-focused collaboration, and structured onboarding resources. Themes of collaboration, intentional practice, and peer support underscore efforts to advance testing practices, adapt to career shifts, and foster shared problem-solving in evolving tech landscapes.

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=itpj0zo3bm
• Published: 2026-04-10T14:05:00Z
• Duration: 51:20
• Author: Unknown

Overview

The podcast discusses challenges and developments in quality engineering, focusing on recurring testing issues like “flaky tests,” mobile testing complexities, and accessibility audits requiring community support. It highlights learning initiatives, such as the MOT chapter responsibilities and a proposed AI-focused learning group, emphasizing collaborative knowledge-sharing. The speaker also reflects on adapting to new roles, balancing work demands, and the importance of structured onboarding resources for career transitions.

Community engagement and collaboration are central themes, with initiatives like the Software Quality Engineering Certificate (SQUEC), which includes 9 modules and an exam, and the “Call for Insights” program for peer discussions on AI, automation, and career shifts. The community extends beyond professional topics, with informal chats about hobbies and personal interests, and resources like glossary expansions and on-demand courses to support continuous learning. Participants are encouraged to contribute to community projects, share expertise, and leverage peer interactions to deepen understanding and address challenges in testing and software quality.

The conversation also underscores the value of foundational knowledge in leveraging AI tools effectively, the critique of rushed processes, and the need to “slow down to speed up” through intentional improvements in testing practices. Personal updates and celebrations, such as career transitions and certification completions, illustrate the communitys role in fostering growth and mutual support. Themes of collaboration, reflection, and shared problem-solving are reinforced through discussions on mentorship, team dynamics, and the evolving role of quality professionals in a rapidly changing field.

What If

• What if you launched a community-driven AI testing accelerator group?
  Concrete move: Start a monthly peer-led session where solo developers share AI tool experiments (e.g., prompt-based testing apps) and co-identify use cases for quality engineering.
  Why now: The text emphasizes AI as a tool for prototyping and democratizing innovation, and the Mottaverse community actively shares AI-inspired experiments.
  Expected upside: Rapid skill development, shared insights on AI tooling, and fostering a niche network of quality engineers leveraging AI for productivity gains.

• What if you leveraged the SQUEC certificate to redesign your career roadmap?
  Concrete move: Complete the SQUEC modules and publish your “portfolio of evidence” on your Mottaverse profile, highlighting contributions to community projects or AI testing experiments.
  Why now: The certificate is fully live, and the text stresses its value for professional credibility, community recognition, and transitioning to consulting roles.
  Expected upside: Strengthened industry visibility, eligibility for consulting opportunities, and a structured framework for continuous learning aligned with market demands.

• What if you applied the Kwaki framework to clarify your teams testing roles?
  Concrete move: Document your current testing workflows and assign Kwaki roles (Who is accountable, responsible, consulted, etc.) between developers and QA engineers using the framework.
  Why now: The text highlights Kwaki as a pragmatic tool for stakeholder clarity, and its inclusion in the Mottaverse glossary signals relevance to modern quality practices.
  Expected upside: Reduced ambiguity in responsibilities, streamlined collaboration, and a scalable model for integrating testing into agile or developer-led workflows.

Takeaway

• Prioritize Addressing Flaky Tests: Dedicate time to systematically identify and resolve recurring test instability issues in your workflows, as this is a common challenge in testing environments.
• Leverage Community Support for Specialized Testing: Engage with the testing community (e.g., via Slack channels, learning groups) to gain expertise in niche areas like accessibility audits or AI tooling, which may require external knowledge.
• Form Structured Learning Groups for AI/Testing: Propose or join a collaborative learning initiative within your network (e.g., an AI-focused group) to share knowledge, troubleshoot challenges, and accelerate skill development.
• Complete the SQUEC Certification for Portfolio Building: Enroll in and complete the Software Quality Engineering Certificate (SQUEC) program, emphasizing module completion and portfolio documentation to validate your expertise.
• Use the Kwaki Framework to Clarify Roles: Implement the Kwaki framework (a playful adaptation of RACI) with developers or stakeholders to define accountability and responsibilities, improving team collaboration and reducing ambiguity.