TDD

Stakeholders demand quick fixes for a buggy app release. Such patching is costly, and does not always offer a complete solution. Break the cycle with unit testing, a worthwhile investment in project quality.

Employing a test-driven development (TDD) approach in React projects tends to be straightforward, especially with the aid of Jest and Enzyme. However, there are a few things to look out for.

In this article, Toptal JavaScript Developer Dave Hyungmok Lee demonstrates his React TDD process, from epics and user stories to development and production.

Testing. It always seems to get left to the last minute, then cut because you’re out of time, budget, or whatever else. Management wonders why developers can’t just “get it right the first time”, and developers (especially on large systems) can be taken off-guard when different stakeholders describe different parts of the system.

With behavior-driven development, you can turn testing into a shared process that focuses on the behaviors of the system, why they matter, and who cares.