Developers Who Test

Testery, Inc

A podcast for developers who ship better software. We talk about all things software testing.

  1. 4D AGO

    From Broadway Drummer to Senior SDET: Angel Williams on AI-Assisted Testing, Flaky Tests, and the QA Mindset

    In this episode of Developers Who Test, host Chris Harbert sits down with Angel Williams, Senior SDET at CHG Healthcare, one of the largest healthcare staffing companies in the US. Angel's journey into software quality is unlike any other—she started as a percussionist trying to make it on Broadway before discovering a knack for debugging deployment scripts during IT contract work. The conversation explores the unique personality traits that draw people to quality engineering. Chris shares his fascinating discovery that every member of one of his QA teams scored high on "restorative" in StrengthsFinder—the same trait that had Angel taking apart the family stereo as a kid just to understand how it worked. Angel provides insight into testing in healthcare, where privacy and security aren't just nice-to-haves—they're essential. She explains how protecting both provider and patient data shapes testing strategies at CHG, from scrubbing logs to ensuring sensitive information never travels over live wires. The discussion takes a deep dive into AI-assisted testing. Angel shares practical examples of using Claude Code with Playwright's MCP integration to build performance dashboards and analyze code for risks. She emphasizes that AI shines brightest not when writing tests, but when helping SDETs understand unfamiliar code, identify risks, and—perhaps most valuably—keep documentation up to date. "Every time I look at a PR with major changes, I ask AI if the README reflects the new code," she explains. Chris and Angel swap war stories about flaky tests, including Angel's mysterious 5 PM failures that turned out to be a timezone shift issue—exactly matching one of the patterns in Chris's "14 Reasons for Flaky Tests" presentation. They discuss infrastructure-related flakiness, load balancer issues, and the critical importance of running tests before merge rather than after. The episode wraps with a thought-provoking discussion about leveraging MCP servers not just for automation, but for asking questions about quality itself—combining data from Jira, test results, and documentation to get a complete picture of project health. Key Topics: The "restorative" personality trait and QA professionalsTesting in healthcare: privacy, security, and compliancePractical AI applications for SDETs Running tests before merge vs. afterMCP servers as a new layer for quality insights

    46 min
  2. JAN 13

    Developer Productivity Metrics: DORA, SPACE, and What Really Drives Team Performance with Martijn Goossens

    Martijn Goossens is Director of Advisory Services at Cerios, a Dutch QA company with approximately 450 employees. Martijn has about 20 years of experience helping teams improve their quality and implement test automation. He is a regular speaker at developer and software quality conferences. In this episode, Chris talks with Martijn Goossens about developer experience, productivity metrics, and what actually drives team performance. Martijn shares insights from his recent conference talk at Hustef and breaks down the key frameworks teams use to measure their effectiveness. The conversation explores the DORA metrics (deployment frequency, lead time for changes, change failure rate, and mean time to recovery) and the SPACE framework (satisfaction/wellbeing, performance, adaptiveness/momentum, communication/collaboration, and efficiency/flow). Martijn explains why he prefers DORA for its practical, quantifiable nature, while SPACE tends to be more subjective and developer-focused. Key topics include: The Dutch testing community: Why the Netherlands has become a hub for software testing innovation and how strong community connections accelerate professional growthMeeting culture and productivity: The value of no-meeting days, the danger of "Swiss cheese calendars," and how to prepare teams for focused work timeHackathons and innovation: Different approaches to fostering creativity, from quarterly hackathons to dedicated innovation time, plus Chris's "hackcation" conceptIndividual vs. team metrics: Why metrics should be treated as sensors providing information rather than judgment tools, and the cautionary tale of the "Cobra problem" where rewarding the wrong behaviors leads to perverse outcomesThe flight level concept: How management can monitor high-level metrics and only drill down when signals indicate a problemMartijn emphasizes that metrics don't tell the whole story --- they help you know what questions to ask and who to ask them to. A developer with fewer commits might be the team's primary reviewer or architect, while someone with many commits might just be making small edits. Context matters. The episode wraps up with Martijn's experience speaking at Hustef in Hungary (held in a train museum complete with miniature train rides) and his upcoming keynote in Tokyo.

    44 min
  3. 07/11/2024

    Risk Based Testing with Adam Sandman

    In this episode, Adam Sandman, CEO of Inflectra, discusses the importance of risk in business and software development. He explains that while revenue and expenses can be predicted and controlled, risk is often unexpected and disruptive. He emphasizes the need for businesses to understand and measure the impact and probability of risks and take measures to protect against them. Adam also highlights the role of software testers in managing risk within an organization, stating that their job is to explore and present the risks to decision-makers so they can make informed decisions. The conversation also touches on the challenges of assessing risk accurately and the potential future of regulated software development. The conversation explores risk-based testing and its role in prioritizing tests and managing risk in software development. It discusses how to identify and prioritize risks, map them to user stories and tests, and use risk scores to determine the most critical tests. The conversation also touches on the impact of observability and rollbacks on risk management, the influence of architecture on risk, and the importance of communication and collaboration between testers and developers. The pragmatic approach to risk and testing based on experience is highlighted. ⁠⁠Developers Who Test Podcast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Adam Sandman on LinkedIn Chris Harbert on ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Sponsored by ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Testery

    43 min

About

A podcast for developers who ship better software. We talk about all things software testing.