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
Simplify Testing with React Testing Library

You're reading from   Simplify Testing with React Testing Library Create maintainable tests using RTL that do not break with changes

Arrow left icon
Product type Paperback
Published in May 2021
Publisher Packt
ISBN-13 9781800564459
Length 246 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Scottie Crump Scottie Crump
Author Profile Icon Scottie Crump
Scottie Crump
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. Chapter 1: Exploring React Testing Library 2. Chapter 2: Working with React Testing Library FREE CHAPTER 3. Chapter 3: Testing Complex Components with React Testing Library 4. Chapter 4: Integration Testing and Third-Party Libraries in Your Application 5. Chapter 5: Refactoring Legacy Applications with React Testing Library 6. Chapter 6: Implementing Additional Tools and Plugins for Testing 7. Chapter 7: End-to-End UI Testing with Cypress 8. Answers 9. Other Books You May Enjoy

Chapter 3

  1. The user-event module closely resembles events that occur when users perform actions on the DOM, such as keydown and keyup events.
  2. MSW allows you to test components that make HTTP requests to APIs. This is done by intercepting the request before it reaches the internet and instead returns controllable mock data for testing.
  3. A mock function is a test double used to make assertions. For example, we can use a mock function to verify that a method is called when a user clicks a button.
  4. The risk is that substituting actual dependencies with mocked versions to test components doesn't allow you to test resulting behaviors when integrated with real production dependencies.
  5. This is an open-response question.
  6. Use a getBy* query when you expect an element to be present in the DOM's current state. Use a findBy* query when an element's presence depends on an asynchronous action that delays the time the element appears in the DOM. Use a queryBy*...
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