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

Shifting workflow to Redux

The Git tag for this section is redux-workflow. This tag contains additional code since the last section, so you may wish to switch to it now, or add the differences yourself, which are described next.

For more detailed instructions, see the To get the most out of this book section in the Preface.

Putting aside the question of how to complete our test coverage, how can we fix the problem?

Let's see whether we can restate it. Previously, our onSave callback was used to notify App that a customer had been saved. That callback was passed a customer object, but now the callback is gone and the customer is safely tucked away in our Redux store.

We can split the problem into two distinct subproblems:

  • How can we trigger workflow and render the AppointmentForm?
  • How can we pull out the customer from Redux?

As we solve these problems, we have to keep in...