Skip to content

The State of Browser Testing

Software Engineering Daily

52m
Transcript

Original podcast

Where to listen

Summary

Written by a model from the transcript; not yet reviewed.

This episode explores the landscape of automated browser testing, the role of open source and standards bodies like the W3C, and how modern tooling fits together. The guest discusses his career path from a non-technical QA hire to a long-time Selenium and WebDriver contributor, a decade at Mozilla, and heading the open source program office at BrowserStack. The discussion covers practical testing philosophies, the shift toward Web Driver BIDI, accessibility test drivers, and the risks introduced by AI and vibe coding.

  • Write one test for every critical path instead of building bloated test suites that take too long to run. 43:05
  • Use AI as a prototyping assistant and review partner rather than relying on it blindly to protect production databases. 40:56
  • Incorporate observability and traces directly into your tests to immediately spot where and why failures happen. 45:39

Chapters

  1. 0:00
    Podcast Host Search and Intro

    The episode opens with a call for a new host for Software Engineering Daily and a brief introduction to the hosts and guests.

  2. 0:33
    Automated Browser Testing Overview

    Josh Goldberg explains the fundamentals of automated browser testing and its reliance on standardization.

  3. 9:45
    Mozilla Experience and Open Source Philosophy

    Burns discusses his decade at Mozilla, the mission of open source, and the impact of working with top engineers.

  4. 11:40
    Standards, W3C, and BrowserStack Relationships

    The conversation shifts to how standards bodies, browser vendors, and BrowserStack interact and support each other.

  5. 28:10
    Testing Philosophy and Critical Path Tests

    Burns outlines a pragmatic testing approach: one test per critical path, balancing speed, correctness, and risk.

  6. 32:03
    Accessibility Testing and the New Driver Spec

    The discussion covers accessibility testing tools, the emerging Accessibility Test Driver spec, and its benefits.

  7. 40:44
    Future of Browser Testing and AI Challenges

    Burns reflects on AI’s impact on testing, the need for guardrails, and the evolving role of human expertise.

  8. 45:39
    Observability and Continuous Delivery Events

    Burns talks about integrating observability into end‑to‑end tests and the potential of event‑driven CI/CD.

  9. 49:06
    Closing Thoughts and Next Steps

    The episode concludes with final reflections on the state of browser testing and future directions.

  10. 50:22
    Analogy to Testing and Security

    David draws parallels between Shaka’s training and the importance of hardening security and testing in a safe environment.

  11. 51:08
    Closing the Interview

    The host wraps up the conversation, thanking David and summarizing key topics discussed.

  12. 51:58
    Final Thanks and Farewell

    The host thanks David and the audience, concluding the episode with a friendly goodbye.

Highlights

  • 2:38

    From Industrial Psychology to QAstory

    The guest explains how studying computer science and industrial psychology in South Africa led to early process reengineering work and a first QA job in the UK during the emergence of Selenium.

  • 12:24

    Standardizing Browsers and Automationinsight

    The guest describes discovering how Opera integrated Selenium, which sparked the push to standardize browser automation through bodies like the W3C to achieve true interoperability.

  • 15:16

    Solving the Hard Problems of DOM Visibilityinsight

    An explanation of why defining element visibility and meaningful waits without pixel-by-pixel checks or solving the halting problem is one of the toughest challenges in automation.

  • 28:10

    The One Test Per Critical Path Strategystrategy

    A specific rule of thumb for testing: focus on a single, solid test for each critical path and rely on other layers like observability, logging, and telemetry.

  • 40:56

    The Dangers of Vibe Coding and Testinginsight

    A warning about the risks of AI-driven vibe coding without proper guardrails, citing real-world examples of unverified code destroying production databases.

Quotes

  • “Automated browser testing is a foundational technology that many web developers rely on.”
    Unnamed speaker · 0:33
  • “I think the simplest one to an executive, because executives think of everything within risks, right?”
    Unnamed speaker · 22:53
  • “I think testing is going to become far more important.”
    Unnamed speaker · 40:50
  • “I like to end each interview with something non-technical that has nothing to do with work.”
    Unnamed speaker · 49:10
  • “learn to run on thorns, because they were barefoot, running through kind of the African countryside.”
    Unnamed speaker · 49:56
  • “I think the main thing is just trying something new and then trying to harden it up, right?”
    Unnamed speaker · 50:32
  • “So I do a lot of things in the community. So browserstack.com/community.”
    Unnamed speaker · 51:17
  • “And it's called Automation Isn't Scary. So hopefully, kind of puts people's minds at ease when working in it.”
    Unnamed speaker · 51:37
  • DeepGram 17:24–17:54
  • Fingerprint 18:00–18:40
  • GuardSquare 18:48–19:25

About this episode

Automated browser testing is a foundational technology that many web developers rely on. Modern tooling lets a single test drive Chrome, Firefox, and Safari the same way, a triumph of software engineering built on years of standardization work. That standardization emerged from the interplay between open source projects, browser vendors, and standards bodies like the W3C. David Burns https://x.com/AutomatedTester is a longtime Selenium and WebDriver contributor, a veteran of Mozilla, and is currently the Head of Developer Advocacy and Open Source at BrowserStack https://www.browserstack.com/. In this episode, David joins Josh Goldberg to discuss how open source projects, browser vendors, and standards bodies fit together, a practical philosophy of testing built around one solid test per critical path, and the risks that AI and vibe coding introduce to web development. Sponsorship inquiries: sponsor@softwareengineeringdaily.com mailto:sponsor@softwareengineeringdaily.com The post The State of Browser Testing https://softwareengineeringdaily.com/podcasts/the-state-of-browser-testing/ appeared first on Software Engineering Daily https://softwareengineeringdaily.com.

Transcript

0:00
52:29

9,536 words · 6 speakers

Topics

  • BrowserStack
  • Selenium
  • Web Driver
  • Mozilla
  • Chrome
  • Firefox
  • South Africa
  • W3C
  • TypeScript
  • Safari

Page updated · transcript and summary are machine-generated