Kevin Martinez, a software architect, advocates for integrating testing into development (TWD) to improve coverage and reduce friction, emphasizing real-time, browser-based testing tools like TWT. TWT allows developers to write and run tests directly in the browser, offering a streamlined, accessible workflow with features like mock APIs, multi-framework support, and live feedback.

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-with-Testing-While-Developing-TWD---Kevin-Martnez-e3f562k
• Published: 2026-02-16T03:18:25Z
• Duration: 00:40:15
• Author: Mamadou N’diaye

Overview

The podcast explores the concept of Testing While Developing (TWD), a practice that aims to embed testing directly into the development process to enhance efficiency and improve test coverage. It highlights frustrations with traditional testing methods, such as testing code after it’s written and the complexity involved in setting up testing tools like Cypress and Playwright. The episode introduces a new tool, TWT (Test With Developer), designed to address these challenges by allowing developers to write and run tests directly in the browser alongside their code. This approach offers real-time feedback and a more integrated testing experience.

TWT includes features such as a browser sidebar for managing tests, the ability to mock API requests, and support for popular frameworks like React and Angular. The tool emphasizes ease of use, continuous feedback, and accessibility, while also integrating with CI/CD pipelines and AI-driven development tools. The discussion promotes the idea of making testing an integral part of the development workflow rather than a separate phase, encouraging developers to adopt a mindset of continuous testing and learning.

What If

• What if you integrated TWD into your workflow by writing tests for each feature before deploying?
  Move: Add a mandatory test creation step for every new feature, using the TWD browser sidebar to write and run tests in real-time.
  Why now: Current testing practices often suffer from “test after code” syndrome, leading to missed edge cases and poor coverage.
  Expected upside: Immediate feedback on feature correctness, reduced debugging time, and higher confidence in code stability.

• What if you replaced your current end-to-end testing tool with TWT to leverage its browser-integrated testing?
  Move: Install TWT and configure it to run tests directly in your browsers sidebar, using the same tools you already work with (e.g., Testing Library syntax).
  Why now: Tools like Cypress and Playwright require complex setups or separate environments, which discourage adoption. TWT simplifies this.
  Expected upside: Faster test execution, real-browser behavior simulation, and seamless integration with your existing development tools.

• What if you used TWTs mock API capabilities to simulate external services during development?
  Move: Implement TWTs service worker-based API mocking to test edge cases (e.g., errors, empty responses) without relying on real services.
  Why now: Testing external APIs manually is time-consuming and error-prone, especially for edge cases.
  Expected upside: Early validation of data flow and API contract compliance, reducing runtime errors and improving reliability.

Takeaway

• Adopt Test With Development (TWD) Practices: Integrate testing directly into your development workflow by writing tests alongside code using tools like TWT, ensuring tests are executed in the same browser environment as your app for real-time feedback.

• Use TWT for Real Browser Testing: Leverage TWTs browser sidebar to run tests in any browser (e.g., Chrome, Safari) directly from your development environment, eliminating the need for separate testing tools and reducing context-switching friction.

• Automate Repetitive Tasks with Mocks: Set up API mocks using TWTs service worker-based feature to simulate external services (e.g., success, error, empty responses), speeding up development by avoiding manual data setup for edge cases.

• Write Feature-Centric Tests with TypeScript: Focus on testing complete user flows (e.g., form submission, login) using TWT, and integrate TypeScript for mock validation to catch mismatches early and ensure data structure accuracy.

• Start with TWDs Official Resources: Begin by exploring the TWD.dev documentation and tutorials to familiarize yourself with setup, framework integrations, and community support, ensuring a smooth transition to TWD practices.