Simon Stewart’s background in quality assurance and testing, including his role in leading the Selenia project and creating WebDriver, informs his perspectives on the field. His current work as a software engineer at Block involves considering the broader implications of testing and quality assurance, rather than just writing and maintaining tests.

BrowserStack Talks

BrowserStack interview based podcast. Released as audio and video

• https://www.browserstack.com/community/podcast
• https://youtube.com/playlist?list=PL1vH6dHT3H7o6pnechxr17kUX---Bjj5K&feature=shared

Episode Details

• Show Notes: N/A
• Published: 2026-02-24T13:35:01Z
• Duration: 00:44:14
• Author: BrowserStack

Overview

The podcast explores Simon Stewart’s contributions to quality assurance, testing, and his pivotal role in the development of WebDriver and the Selenium project. It highlights the evolving role of QA in considering architectural design and risk management, emphasizing the value of human insight over AI in achieving high-quality outcomes. The discussion also covers the transformation of WebDriver from a personal project into a standardized open-source tool through W3C collaboration, as well as the importance of community and commercial support in maintaining project sustainability.

Key topics include Test-Driven Development (TDD), testing as a risk mitigation strategy, and the KEMPX 3X model for managing project lifecycles. The conversation reflects on the challenges and benefits of open source development, the standardization of WebDriver, and the impact of AI on development practices. It also addresses the preference for stable technologies over novelty, the significance of effective communication in testing, and concepts such as Dopamine-Driven Development and the importance of maintainability in long-term software projects.

What If

• What if you applied the Kempex 3X model to your next feature development?
  Move: Structure your project into three phasesExplore (prototype with minimal testing), Expand (stabilize with TDD), and Extract (refine with defect-driven fixes).
  Why now: As your project scales, this approach ensures you address technical debt proactively and avoid over-engineering early stages.
  Expected upside: Reduced rework, clearer API designs, and faster delivery of stable, maintainable features.

• What if you prioritized human-in-the-loop AI for test generation?
  Move: Use AI tools to auto-generate initial tests, but mandatorily validate them with manual QA sessions before deployment.
  Why now: The rise of AI in testing risks creating “averaged” test suites that miss edge cases. Human oversight ensures quality.
  Expected upside: Faster test creation with fewer false negatives, while preserving the nuance of human risk assessment.

• What if you open-sourced a critical part of your tooling and sought browser vendor collaboration?
  Move: Identify a reusable component (e.g., a testing library) and standardize it under an open-source license, inviting browser vendors to adopt it.
  Why now: WebDrivers success shows that cross-browser standardization drives adoption. This avoids vendor lock-in and attracts community support.
  Expected upside: Broader ecosystem integration, reduced maintenance burden, and potential commercial backing from industry players.

Takeaway

• Adopt Test-Driven Development (TDD) for API Design: Start by writing tests for each feature before implementing code. Use TDD to iteratively define your API, focusing on boundary conditions and key workflows (happy/unhappy paths) to build a robust foundation.
• Implement the KEMPX 3X Model in Project Phases: Structure your development process using the Explore, Expand, and Extract phases. For example, begin with rapid experimentation (Explore), stabilize ideas with testing (Expand), and refine with bug fixes (Extract) to maintain focus and quality.
• Prioritize Perceived Safety in Testing: Use tools that provide visual feedback (e.g., real browser interactions) to build trust in your tests. Avoid relying solely on headless or abstract tools like HTML Unit, which may lack trust despite technical reliability.
• Contribute to Open Source for Standardization: Engage with open-source communities to align your tools with standardized protocols (e.g., WebDriver). This increases compatibility, adoption, and long-term sustainability of your project.
• Focus on Core Functionality to Avoid Complexity: Avoid feature creep by prioritizing essential features that align with your project’s goals. This reduces maintenance burdens, as seen in the WebDriver teams focus on core automation rather than peripheral tools.