ReactTDD.com has just launched! I’m planning to get a lot of content online in the next week, together with more site features, including a newsletter.

If you’d like to have your post featured on the site, please get in touch.

—Daniel

  1. Beyond TDD: breaking the rules

    Image of Daniel Irvine
    Daniel Irvine

    Rules are made to be broken, right? TDD is a strict set of rules that define a process for building software. But experienced practitioners have moved beyond the rules and work towards something else entirely.

    Continue reading…
  2. How to achieve 100% coverage of your UI components with the fewest unit tests

    Image of Daniel Irvine
    Daniel Irvine

    One of the first decisions you need to make when testing the rendered output of a component is which parts of it to test. The straightforward TDD answer is obviously all of it, but since we like to be lazy we look for excuses to not do that. Here’s how I decide what to test and what to not.

    Continue reading…
  3. What is test surface area?

    Image of Daniel Irvine
    Daniel Irvine

    The surface area of a test is all the executed production code that happens within the “act” phase of a test. You can think of this as the code that the test covers, or the coverage of this single test.

    Continue reading…
  4. Understanding Arrange-Act-Assert

    Image of Daniel Irvine
    Daniel Irvine

    If there’s one piece of advice that will help you write better unit tests, it’s this: always, always write your tests in Arrange-Act-Assert order.

    Continue reading…
  5. Why is unit testing important?

    Image of Daniel Irvine
    Daniel Irvine

    Unit testing has fallen out of fashion within the front-end community. After half a century of structured programming, and twenty years of XP, our industry still struggles to benefit from unit testing. Why is this the case?

    Continue reading…