Book Image

Mastering React Test-Driven Development

By : Daniel Irvine
Book Image

Mastering React Test-Driven Development

By: Daniel Irvine

Overview of this book

Many programmers are aware of TDD but struggle to apply it beyond basic examples. This book teaches how to build complex, real-world applications using Test-Driven Development (TDD). It takes a first principles approach to the TDD process using plain Jest and includes test-driving the integration of libraries including React Router, Redux, and Relay (GraphQL). Readers will practice systematic refactoring while building out their own test framework, gaining a deep understanding of TDD tools and techniques. They will learn how to test-drive features such as client- and server-side form validation, data filtering and searching, navigation and user workflow, undo/redo, animation, LocalStorage access, WebSocket communication, and querying GraphQL endpoints. The book covers refactoring codebases to use the React Router and Redux libraries. via TDD. Redux is explored in depth, with reducers, middleware, sagas, and connected React components. The book also covers acceptance testing using Cucumber and Puppeteer. The book is fully up to date with React 16.9 and has in-depth coverage of hooks and the ‘act’ test helper.
Table of Contents (21 chapters)
Free Chapter
1
Section 1: First Principles of TDD
6
Section 2: Building a Single-Page Application
12
Section 3: Interactivity
16
Section 4: Acceptance Testing with BDD

Working with the shallow renderer

You've already seen one technique for testing child components that perform side effects. We can stub out those components and uses spies to assert that they were instantiated with the right props.

There's another technique that we can use to test components, and we'll use it for building App. It's shallow rendering, and it essentially builds us a tree of React component instances, but stops at all custom components. All primitives, such as div, ol, and table, will be rendered along with their children. Since all of the components that we've written in the book are custom components, none of them will be rendered.

The root component itself will have all of its hooks and side effects run, so we can continue to test any kind of life cycle, and we'll use that to test-drive App.

So, what does this tree of component instances...