¡Vuelvo a la @commit-conf.com ! 🚀 En 2018 hablé de testing en React; hoy el panorama ha cambiado, pero el frontend sigue sufriendo con los tests. Ven a descubrir TWD (Testing While Developing): cómo integrar tests en tu flujo real y usar la IA como amplificador. ¡Nos vemos allí!

Beware of "Guess Coders," the developers who spend days building hyper-complex abstractions for a hypothetical future that never exists, yet don’t have time to write a single unit test. Stop guessing what the future needs and start testing what your users need today.

Payment widgets. Map SDKs. Video players. Chat widgets. You can't type into the card form. You can't click a marker at a specific lat/lng. You can't force onSuccess on cue. So the API call after the callback, the analytics, the error handling. All untested. TWD swaps the SDK out.

Contract testing without a broker, without a provider verifier, without a separate suite. TWD validates the mocks you already write against your OpenAPI spec on every CI run. Required field missing? Run fails. Wrong format? Run fails. Drift caught before production.

Testing @tanstack.com Router + Query the standard way makes the test file bigger than the component. MemoryRouter, fresh QueryClient, providers, MSW handlers, assertions. All against jsdom. TWD runs the test inside your running app. Real router, real client, real DOM. github.com/BRIKEV/twd-t...

Your tests pass. CI is green. But are you testing the right things? A page that loads doesn't mean the form submission works. A route can show as "covered" while the core interaction has no test at all. /twd:test-gaps scans routes and flags the ones with real risk first.

Your mocks are lying to you. The backend renames a field, tightens an enum, makes something required. Your mock keeps returning the old shape. Tests stay green. Production breaks. That's why we included contract testing in twd twd.dev/contract-tes...

TWD started as a way to test in your real browser while you develop. Over the last months it grew into a full AI testing workflow. Six skills, one loop, your real app. Quick tour.

Testing isn't a phase. It's how you build. The moment you treat it as the thing you do after, it stops happening. The moment you treat it as the thing that runs while you write the feature, it just becomes part of the work. twd.dev

We build apps that run in a browser. Most of our tests don't. They run isolated in node. Close to a real browser. Not one. The failure that only shows up in the real DOM never gets caught. TWD runs the test where the app actually runs.

Test what you own. Mock what you don't. That's the rule. Your code is what changes, what breaks, what ships. That's where tests pay off. Map SDK, payment widget, analytics layer, third-party iframe: stub them and move on.

TWD is a testing approach that runs inside your real browser, against your real app, while you develop. A sidebar shows results in real time as you code. No jsdom. No separate test world. No waiting for CI. twd.dev