Celebrate the creativity and courage of testers and quality engineers as they share stories, lessons, and ideas in just 99 seconds.

Map your skills, set learning goals, and grow as a testing generalist using the Periodic Table of Testing.

The SDLC is a structured and iterative framework that outlines the entire process of building and maintaining software. It is essentially a roadmap or a plan that takes you from the initial idea for a piece of software all the way to its refinement or removal. Instead of just jumping in and hoping for the best, the SDLC provides a structured approach to ensure everything is done to the best of the team's ability.While there are different versions, most SDLCs include several key stages. It starts with planning, where you figure out the project's scope and goals. Then you move on to gathering and documenting requirements. After that, there's design, where the architecture and user interface are planned. Then you have the actual development or coding. This is followed by testing, where we try to find all the bugs. After deployment, where the software is released, we observe the product's behaviour and provide maintenance, which involves ongoing monitoring, support and updates.For testers, the SDLC is a crucial concept. It's a reminder that testing is not just something you do at the end. A modern approach involves testers interacting right from the very first planning stages to identify risks, prevent problems and catch potential bugs as early as possible. Following a clear SDLC helps teams manage complexity, reduce risk, and produce a higher-quality product in a more predictable way. It’s all about bringing order to the creative chaos of building software.

Developer Experience or DevEx describes how easily developers can go from an idea to running code in production. It focuses on identifying bottlenecks in workflows, including slow builds, failing CI/CD pipelines, unclear documentation, and flaky tests in continuous integration. By removing friction and creating faster feedback loops, developers focus on writing quality software. While it is called developer experience, any improvement should lead to a better overall team experience.Improving DevEx involves automating repetitive tasks (which frees up testers' time for deeper testing), providing clear guides for setting up environments, and integrating CI/CD pipelines that deliver real-time feedback on code health. Imagine a pipeline that flags a typo before you finish your commit or a local setup script that starts containers in seconds. Those small gains add up to shorter lead times and better morale.You can measure DevEx by tracking the time it takes to onboard new team members, even if they are not a developer, measuring build failure rates, and tracking team satisfaction. Each metric can uncover potential hidden blockers and can also show where it might be best to invest for the biggest return. As the experience improves, teams are better positioned to ship features faster, catch bugs early, and deliver higher-quality software.

Hear how the community is discovering new ways to think about quality through SLOs, accessibility, and better listening.

Celebrate the quality community’s creativity and courage as folks share lessons, ideas, and stories in just 99 seconds.

Discussing all the accessibility content on the Ministry of Testing at A11y North 9th meet-up

Celebrate the launch of This Week in Quality as the community tests a new platform, shares MoTaCon highlights, and reflects on how quality connects us all.

02/10/25. It's Thursday. The time is 16:03. It's Day 2 of MoTaCon. And I've never seen the 99-Second Talks queue grow so quickly. And even after this photo more people turned up. Such is the...

Big thanks to everyone who supported us through this wild year of building Epic Test Quest from early interviews to testing our prototypes and giving us honest feedback. It was amazing to meet so ...

Enjoying the banter, chemistry and passion for testing, quality and people, from the, err, Morecambe and Wise of our industry ⭐️👏🏽