Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering React Test-Driven Development

You're reading from   Mastering React Test-Driven Development Build rock-solid, well-tested web apps with React, Redux and GraphQL

Arrow left icon
Product type Paperback
Published in May 2019
Publisher Packt
ISBN-13 9781789133417
Length 496 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Daniel Irvine Daniel Irvine
Author Profile Icon Daniel Irvine
Daniel Irvine
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Section 1: First Principles of TDD FREE CHAPTER
2. First Steps with Test-Driven Development 3. Test-driving Data Input with React 4. Exploring Test Doubles 5. Creating a User Interface 6. Section 2: Building a Single-Page Application
7. Humanizing Forms 8. Filtering and Searching Data 9. Test-driving React Router 10. Test-driving Redux 11. Test-driving GraphQL 12. Section 3: Interactivity
13. Building a Logo Interpreter 14. Adding Animation 15. Working with WebSockets 16. Section 4: Acceptance Testing with BDD
17. Writing Your First Acceptance Test 18. Adding Features Guided by Acceptance Tests 19. Understanding TDD in the Wider Testing Landscape 20. Other Books You May Enjoy

Handling server errors

The Git tag for this section is handle-server-errors.

The /customers endpoint may return a 422 Unprocessable Entity error if the customer data failed validation. That could happen if, for example, the phone number already exists within the system. If this happens, we want to withhold calling the onSave callback and instead display the errors to the user and give them the chance to correct them.

The body of the response will contain error data very similar to the data we've built for the validation framework. Here's an example of the JSON that would be received:

{
"errors": {
"phoneNumber": "Phone number already exists in the system"
}
}

We'll update our code to display these errors in the same way our client errors appeared. Since we already handle errors for CustomerForm, we'll need to adjust our tests...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image