The Software Testing Unleashed podcast discusses improving quality and developer experience through metrics and collaborative approaches like DORA and SPACE.

The podcast focuses on balancing metrics with actual test coverage and quality, emphasizing tangible DORA metrics, good test coverage, and quality gates for effective team performance.

Software Testing Unleashed

Software Testing Unleashed - hosted by Richard Seidl. Different guest per episode. The official Show notes contain a comprehensive overview of the episode. Released as audio and video.

• https://www.richard-seidl.com/en/testing-unleashed
• https://www.youtube.com/playlist?list=PL48Mbm-L0hjB1OdwYi9h7jrq9t352-Zk_

Episode Details

• Show Notes: https://www.richard-seidl.com/en/blog/devex-dora-space
• Published: 2026-01-08T05:00:00Z
• Duration: 1482
• Author: Richard Seidl | Software Development & Testing Expert

Overview

The podcast examines the impact of developer experience (DevEx) on software development, underscoring the value of using measurable metrics such as DORA and SPACE to enhance quality and test coverage. It discusses the difficulties teams encounter when trying to balance these metrics with actual development outcomes, emphasizing the need for a collaborative and focused strategy. Through a case study with Vestas Wind Turbines, the episode demonstrates practical efforts to improve DevEx, focusing on key indicators such as time to repair and deployment frequency. The discussion also highlights the significance of ongoing iteration, shared understanding among team members, and the alignment of QA practices with DevOps to achieve better development outcomes.

What If

• What if you integrate QA into your daily DevEx workflow by setting up automated tests aligned with DORA metrics?

  • Concrete move: Create a small set of automated tests (e.g., unit, integration, or CI/CD pipeline tests) that directly tie to DORA metrics like change failure rate or lead time for changes.
  • Why now: DORA metrics are widely adopted and provide tangible outcomes for QA work, making it easier to justify QA efforts to stakeholders or align with company goals.
  • Expected upside: Improved process visibility, faster feedback loops, and measurable quality improvements that reduce rework and downtime.

• What if you implement a personal integrated test environment to speed up QA and reduce risk?

  • Concrete move: Set up a lightweight, self-contained local test environment (e.g., Dockerized or VM-based) that mirrors your production or staging setup.
  • Why now: The Vestas case study showed that shared environments slow down testing and increase risks; a personal environment allows you to test safely and independently.
  • Expected upside: Faster test execution, reduced dependency on external resources, and higher confidence in test reliability during development.

• What if you map QA activities to specific DORA metrics to prove their business value?

  • Concrete move: Track how changes in QA practices (e.g., increased test coverage, faster feedback) correlate with DORA metrics like deployment frequency or mean time to restore.
  • Why now: Aligning QA with DORA metrics (as emphasized in the text) helps quantify qualitys impact on business outcomes, making QA more strategic for solo operators.
  • Expected upside: Data-driven arguments for QA investments, better alignment with dev teams, and potential for scaling QA practices within your organization.

Takeaway

• Track DORA Metrics to Improve Quality and Process Efficiency
  Implement and monitor key DORA metrics (lead time for changes, deployment frequency, MTTR, change failure rate) to identify bottlenecks in your workflow and measure the impact of testing practices on software quality.

• Enhance Test Coverage with Quality Gates
  Integrate automated testing and quality gates into your development pipeline to ensure code changes meet predefined standards before deployment, reducing the risk of failures and improving reliability.

• Run Short, Iterative Experiments to Test Process Changes
  Conduct small-scale experiments (e.g., 46 weeks) to test improvements in tools, workflows, or testing strategies. Use metrics to evaluate outcomes and refine practices incrementally.

• Implement Personal Integrated Test Environments
  Set up isolated, self-contained testing environments for your projects to speed up testing, reduce dependency on shared resources, and minimize the risk of breaking critical systems.

• Engage with QA and DevEx Communities for Collaboration
  Follow QA leaders like Martijn Hossens on LinkedIn and participate in events or forums (e.g., Husteth Conference) to stay updated on best practices, tools, and community-driven solutions for improving developer and QA workflows.