Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
React 16 Essentials

You're reading from   React 16 Essentials A fast-paced, hands-on guide to designing and building scalable and maintainable web apps with React 16

Arrow left icon
Product type Paperback
Published in Nov 2017
Publisher
ISBN-13 9781787126046
Length 240 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Christopher Pitt Christopher Pitt
Author Profile Icon Christopher Pitt
Christopher Pitt
Artemij Fedosejev Artemij Fedosejev
Author Profile Icon Artemij Fedosejev
Artemij Fedosejev
Adam Boduch Adam Boduch
Author Profile Icon Adam Boduch
Adam Boduch
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. What's New in React 16 FREE CHAPTER 2. Installing Powerful Tools for Your Project 3. Creating Your First React Element 4. Creating Your First React Component 5. Making Your React Components Reactive 6. Using Your React Components with Another Library 7. Updating Your React Components 8. Building Complex React Components 9. Testing Your React Application with Jest 10. Supercharging Your React Architecture with Flux 11. Preparing Your React Application for Painless Maintenance with Flux 12. Refining Your Flux Apps with Redux Index

Testing React components

Let's step back from writing code for a minute and talk about what it means to test the user interface. What exactly are we testing? We're testing the fact that our user interface renders as expected. In other words, if we tell React to render a button, we expect it to render a button—not more, not less.

Now how can we check that this is the case? One way of doing this is to write a React component, bundle our application, run it in a web browser, and see with our own eyes that it displays what we want it to display. This is manual testing and we do it at least once. But it is time consuming and unreliable in the long term.

How can we automate this process? Jest can do most of the work for us, but Jest doesn't have it's own eyes, so it will need to borrow our eyes at least once for each component. If Jest "can't see" the result of rendering a React component, then how can it even test a React component?

In Chapter 3, Creating...

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 €18.99/month. Cancel anytime