Two MoTacon attendees are on the left. The MoTaacon logo is in the center, and to the right a prompt to Get Your Ticket.
Testing meets fun: How we accidentally created the best testing icebreaker using sticky notes and a whiteboard image
  • Christine Pinto's profile
Dynamically connect cross-functional team roles, build trust, lower stress and naturally reinforce software testing terminology.
How I measure quality without looking at bug counts image
  • Sanjeev Kumar's profile
Redefine software quality by replacing bug counts with metrics that track rework rates, the survival of assumptions in production, and the speed of recovery from system friction.
Lean testing under pressure: How small teams deliver high-impact quality in highly constrained environments image
  • Matthew Whitaker's profile
Implement lean testing strategies that enable small teams to deliver high-quality software efficiently within resource-constrained environments.
The forgotten part of quality: paying attention to production image
  • Stuart Thomas's profile
Integrate monitoring, observability, and alerting into the core quality engineering process to ensure systems are as diagnosable as they are functional
Testing with feature flags: what we expected and what actually happened image
  • Daria Tsion's profile
Feature flags entered our workflow as a quality safeguard.
Creating a resilient test framework with the Playwright Page Object Model (POM) image
  • Shawn Vernier's profile
Implement the Playwright Page Object Model (POM) to build maintainable, resilient test suites by centralizing page interactions and separating them from test logic.
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements image
  • Richard Adams's profile
  • Emily O'Connor's profile
Apply the "5 Whys" technique to both technical debugging and organisational workflows to uncover deep-seated root causes and implement sustainable continuous improvements.
Why software testers should write documentation even if no one else reads it image
  • Shawn Vernier's profile
Cultivate professional trust and accountability by using detailed documentation to demonstrate due diligence and quantify risk for stakeholders.
Coaching with code: using AI to learn how to automate tests image
  • Megan Ozanne's profile
Leverage AI as a personalised "code coach" to bridge the gap between manual testing and automation by translating plain English into executable scripts and providing line-by-line logic explanations.
Product-minded testing: choosing what matters when everything feels important image
  • Ishalli Garg's profile
Prioritise high-impact user journeys and critical risks over exhaustive checklists to ensure essential product functions remain reliable and user-focused through a product-minded testing approach.
Stop delegating your thinking: Using 5 whys to check AI documentation image
  • Cristina Lanca Carrageis's profile
Shift from treating AI as a "single source of truth" to using it as a "clarity booster" for human-led ideas.
Subscribe to our newsletter