React Testing Strategy: What to Test and Why
Learn what to test, what to skip, and how to keep tests maintainable. This course focuses more on how to know what to test.
Testing Fundamentals
Why Bother Writing Tests?
Pro
Unit vs Integration vs E2E: The Argument That Never Ends
Current
Your Tests Shouldn't Know How Your Code Works - testing behaviour not implementations
Pro
What to Test
Not Everything Deserves a Test. Here's How to Choose
Pro
Testing Logic and Pure Functions
Pro
How to write good integration tests so you know everything will work when wired together
Pro
Common Pitfalls
Brittle Tests - How to avoid them by thinking about your tests before you write them
Pro
What are flaky tests and approaches to avoid having them in your test suite
Pro
Why assertions that pass don't always mean your app works (false positives & false negativesin tests)
Pro
Code Smells, but for Your Tests - Testing Mistakes Everyone Makes
Pro
React Testing Strategy: What to Test and Why: Unit vs Integration vs E2E: The Argument That Never Ends
Unit vs Integration vs E2E: The Argument That Never Ends
When talking about automating tests, there are a few terms that have a few definitions.
- unit tests
- integration tests
- E2E (End to end) tests
On a team of five engineers, ask for the difference between unit tests and integration tests and you will probably get five different interpretations.
In this lesson I will explain the difference, and how each test is suitable for different things.
And not to spoil it, but I'll also cover why you normally get most value out of integration tests.
Loading full lesson...
Share this lesson with your teamTweet (X) it
Invite a teammate to learn with you by sharing this lesson or dropping the link in your team chat.