You have written the tests. The CI pipeline runs them. The gap analysis has helped you fill the blind spots. Quality checks are passing. The work is solid. And yet — ask a product manager what your test suite actually covers, and you will get a blan...

The Problem With "We Have Tests" There is a moment in every project where someone says "we have tests" like it settles the matter. The CI pipeline is green. The coverage number is somewhere north of 70%. Everything is fine. Until a bug slips throu...

You've wired up your test suite. CI is green. You're shipping. And then a bug lands in production on a route nobody thought to test. It's not that your tests are bad. It's that you didn't know what was missing. That's the problem /twd:test-gaps is ...

Why Set Up CI Early Once you have tests worth running, the natural next step is making sure they run on every push. The sooner you do it, the fewer surprises down the road — things like env vars that only exist locally or paths that work on your ma...

In the previous articlehttps://coderlegion.com/17453/stop-letting-ai-write-untestable-code-add-determinism-back-with-twd, we talked about /twd:setup — the skill that analyzes your project and generates .claude/twd-patterns.md, a file that teaches you...

Now that AI is generating a big portion of our frontend code, speed is no longer the main bottleneck. Confidence is. We’ve seen this before: when teams wanted to move fast, the real enabler wasn’t “more code” — it was having a solid testing strate...

AI is changing the way we work as developers. We are moving from writing code to writing specifications. Instead of implementing features ourselves, we rely more on agent modes and tools like Claude Code, Codex, or Gemini CLI. This works incredibly...

A few weeks after releasing TWDhttps://brikev.github.io/twd/, a tool designed to integrate testing directly into the development workflow. I started creating testing recipes for different frontend frameworks. While doing that, a few patterns became v...

One of the biggest milestones we’ve been working on is now live: TWD 1.3.x brings full multi-framework support with a single unified setup. This means you can now drop TWD into React, Vue, Solid, and Angular projects using the exact same initializat...

In this part, we’ll look at a new feature in TWD: support for Testing Library–style selectors. These selectors are widely known in the community, and while you could technically use them before TWD is very flexible, now they’re fully integrated — inc...

TWD still has many more advanced features — such as function mocking — but with what we’ve covered so far, you already have everything a solid testing tool needs. In this step, we’ll see how to collect code coverage from your TWD tests and visualize ...

In Part 3https://coderlegion.com/7371/testing-while-developing-part-2-selectors-assertions-and-user-events, we explored one of TWD’s core features — network mocking — and completed our first full set of tests. Now, it’s time to take the next step: ru...

In Part 2https://coderlegion.com/7371/testing-while-developing-part-2-selectors-assertions-and-user-events, we explored assertions, selectors, and user interactions in TWD. We used those tools to test the homepage, which only had a single button. N...

In the previous posthttps://coderlegion.com/7370/testing-while-developing-part-1-installation-and-first-test, we set up our basic testing configuration and used the visit command to load our app. Now, we’re ready to make our tests a little more meani...

Let’s start our journey learning how to use TWD Test While Developing! In this first part, we’ll work with a small finished project that includes two pages: A Hello World page perfect for our first test A Todo List page that makes requests to an AP...

A few months ago, I wrote about Testing While Developing, where I rethought how we add tests — not as an afterthought, but as part of the development process itself. You can read that article herehttps://dev.to/kevinccbsg/rethinking-testing-why-i-tes...

We continue with the sixth part of this series on React Router Data Mode. This time, we'll talk about actions: one of the key pieces for data handling that React Router offers. If you're coming from the previous posthttps://coderlegion.com/4297/rea...

We continue with the fifth part of this series on React Router Data Mode. This time, it will be a brief post where we’ll do some refactors, review the useParams hook, and improve navigation with NavLink. If you’re coming from the previous posthttps...

We continue with the fourth part of this series on React Router data mode. This time, we’ll dive deeper into loaders, first by adding a contact detail screen and then exploring hooks like useRouteLoaderData and useParams. If you’re coming from the ...

Let's move on to the third part of this tutorial series. In this case, we'll look at a concept that comes from Remix and can now also be found in React Router: loaders. If you're coming from the previous tutorialhttps://coderlegion.com/3682/react-ro...