How to Test a Release Oleksandr Bolzhelarskyi

The podcast episode focuses on the complexities of software release testing, emphasizing the distinction between QA (testing) and quality management as separate processes. Aleksandr Bojelanski, a release management director, highlights the challenges of unclear roles between testing and quality teams, the need for end-to-end quality oversight, and the risks of conflating QA responsibilities with broader quality management. Key topics include the importance of rigorous release testing to prevent integration issues, the limitations of bug bash testing, and the role of test management tools and checklists in improving coverage. The discussion also addresses common pitfalls, such as flawed processes leading to undetected bugs, and the necessity of clear permissions for testers to influence quality beyond mere testing. Strategies for effective release management include aligning with business needs while prioritizing stability, implementing code freeze policies, and ensuring environment synchronization to avoid production issues.

The episode further explores the balance between speed and stability in releases, stressing the need for collaboration between engineering and business teams to avoid rushed, poorly tested deployments. Examples like CrowdStrikes catastrophic release and GTA 6s delayed launch underscore the business impact of poor release practices. Practical advice includes focusing on risk-based regression testing, leveraging automation where feasible, and fostering continuous improvement through incident analysis and process refinement. The discussion also touches on the evolution of testing roles, from manual methods to AI-driven approaches, and the importance of curiosity and technical skills for modern testers. Resources for new QA professionals, such as books on testing principles and hands-on experience with real teams, are recommended to build practical expertise. Overall, the episode advocates for a structured, process-driven approach to testing and releases, emphasizing accountability, clarity of roles, and the integration of quality management throughout development cycles.