The episode highlights the critical difference between QA testing and quality management, stressing the need for clear roles, end-to-end oversight, and structured processes to prevent integration issues and production failures. It emphasizes risk-based testing, automation, collaboration between teams, and lessons from real-world release disasters to ensure stable, business-aligned software deployments.

How To Test This?

interview episodes where Mamadou N’diaye talks with with software testing experts

• https://podcasters.spotify.com/pod/show/spidey1944
• https://www.youtube.com/@HowToTestThis
• https://www.linkedin.com/in/mamadou-ndiaye-consultant/

Episode Details

• Show Notes: https://podcasters.spotify.com/pod/show/spidey1944/episodes/How-to-Test-a-Release--Oleksandr-Bolzhelarskyi-e3h22ou
• Published: 2026-03-27T12:47:16Z
• Duration: 00:57:34
• Author: Mamadou N’diaye

Overview

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.

What If

• What if you implemented a quality management checklist for your release process?
  Concrete move: Create a checklist of quality management tasks (e.g., environment validation, stakeholder sign-offs, regression test coverage) and integrate it into your release workflow.
  Why now: The text highlights that unclear roles between testing and quality management lead to inefficiency; this move ensures accountability and reduces post-release issues.
  Expected upside: Fewer critical bugs in production, faster resolution of quality gaps, and clearer ownership of release success.

• What if you automated a subset of your regression tests using AI tools to focus on high-risk areas?
  Concrete move: Prioritize automating regression tests for features with high interdependencies or frequent changes, using AI-powered tools like Testim or Applitools.
  Why now: The text emphasizes that testing flaws often stem from processes, not individual capability; automation in critical paths reduces human error and “sleeping” bugs.
  Expected upside: Faster feedback on critical changes, reduced rework from untested integrations, and time saved for manual testing on low-risk tasks.

• What if you established a pre-production environment sync policy with DevOps?
  Concrete move: Collaborate with DevOps to ensure your testing/staging environments mirror production in configuration, data, and dependencies.
  Why now: The text notes environment gaps (e.g., test vs. prod) cause issues; this move minimizes surprises during deployment.
  Expected upside: Fewer deployment failures, faster bug diagnosis, and alignment with production-ready setups for release confidence.

Takeaway

• Implement test management tools (e.g., JIRA) to organize test cases, track bugs, and ensure visibility across test stages.
  Based on: “Implementing test management tools (e.g., JIRA)” to systematize testing workflows and avoid missed defects.

• Create and enforce test checklists for end-to-end release testing to ensure comprehensive coverage of integration and regression risks.
  Based on: “Creating checklists or instructions to ensure comprehensive coverage during testing” to identify process flaws and prevent critical issues.

• Define a clear release management process with explicit roles for testing and quality management to avoid confusion and ensure accountability.
  Based on: “Clear separation of QA (testing) and quality management is critical” to align responsibilities and avoid bottlenecks in solo operations.

• Proactively communicate testing risks and required timeframes to business stakeholders to align on release priorities and avoid pressured, rushed decisions.
  Based on: “Engineers must communicate risks” to prevent post-release issues and manage expectations during collaborative workflows.

• Prioritize regression testing only where changes pose a risk to existing functionality, using risk-based approaches to optimize testing efficiency.
  Based on: “Regression testing is done only when changes pose a risk” to focus efforts on high-impact areas and avoid wasteful, full-scope testing.