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

Exercises

The work we started in this chapter is only the beginning of the refactor to Redux. I'd encourage you to continue the process in your own codebase, using the following exercises as a starting point:

  • Modify the customer reducer to ensure that error is reset to false when the ADD_CUSTOMER_SUCCESSFUL action occurs.
  • Update AppointmentForm to submit its data via Redux in the same way as we've done with CustomerForm. Pull out the history change from App into its own saga that is triggered when an action of type ADD_APPOINTMENT_SUCCESSFUL occurs.
  • Repeat the process for CustomerSearch. This time, you can add to the existing customer reducer rather than create a new one.
  • Now that you have Redux actions for CustomerSearch, remove the last of the transition logic from App and push it into a saga.