Override HTTP interceptors for GitHub API token requests in testing, handle errors efficiently, export and access the server, and implement cleanup.

Master error case testing in a mock API environment. Verify failure handling, page redirection, and console error capture. Maintain test isolation with cleanup.

Testing Error Handling and Assertions with Mock API Calls

[00:00] We borrowed a lot of stuff from the previous test. This should look kind of familiar. We're gonna make a utility out of this a little bit later. But we want things to behave a little differently now. So instead of sending users off to onboarding, we want them to go to login. So let's add that assertion here so we get our test failing first.

[00:17] So assert redirect, the response should go to login. Now that response is gonna come from this. And I happen to know also that when there's an error, we throw a response object. And so we could do a try catch around this. I don't like doing that. So we're gonna actually just do a catch.

[00:35] And we're gonna take the response and return that response. So that turns that thrown response into just a resolved response. Now we're getting a failure because that response is actually redirecting to onboarding instead of login. And so we want to make sure

[00:51] that that is not happening that way. We also have this assert toast sent. So we wanna have that assertion as well, or that Kelly put together for us. So that is just making sure that our EN toast is gonna be sent. And I should mention also, these assertions are not the best

[01:11] and we will have custom assertions next or a little bit later. So let's assert the toast was sent on that response. And then we also want to make sure that the console error was called as well because we do log an error when that happens. So let's bring in console error.

[01:30] And because we're doing that, we're gonna have to add console error dot mock implementation and that way we don't get the throw from when that happens. So there you go. We've got all of our assertions set up. We're in a good place now. And so now we just need to make sure

[01:49] that we set things up so that this does in fact fail in the way that it's supposed to. So right here, we're gonna say, let's get rid of that as well. We're gonna say server, which is coming from our mocks dot use.

[02:07] And this is an HTTP post that's coming from MSW. And we pass the access token endpoint, which is right here. So we're gonna override that handler for this particular endpoint. And this is gonna take a request. And with that request then, actually we can ignore the request.

[02:31] And in our case, we don't care about the request. We're just gonna send back a failure. And so here we'll say, return new response error status 400. So some kind of error. That's all we're testing is what happens if there's an error. So I save that and we should get a passing test. We do, awesome.

[02:50] So the error case is being taken as a part of this flow. When the access token endpoint returns an error, then we throw the redirect response as we put together in the auth workshop. And then we're handling all of that here.

[03:07] Now, we are making a mess of the world with this server dot use. We need to clean up after ourselves. And so we're gonna add an after each from the test. And this is just going to call server dot reset handlers. And what that will do, we gotta spell it right. There we go.

[03:26] What that's gonna do is ensure that when you start up your server at first here, you provide some handlers. And then all of the handlers you add with server dot use like this are kind of like secondary handlers. They actually will come first. So if they match, then they'll be the ones that are called.

[03:46] And then the existing handlers will get called thereafter if need be. But between these tests, we're going to say, hey, reset the handlers to get rid of those ones that were added with server dot use. And we'll just use the ones that were initialized. So that's what reset handlers is doing for us. And we want that between every test

[04:06] so that we keep our tests isolated. Anytime you mess up the world, you wanna make sure you're thinking about how to clean it up again. That's a lesson for life. So let's talk really quickly about what we did here. First, we updated this to handle the fact that we're throwing a response in this error case. So we catch that.

[04:25] And then we're asserting the redirect went to login because the auth flow failed. The toast is going to be sent to explain what went wrong. We're gonna improve this later. And then we expect the console error should have been called at least once or exactly one time.

[04:44] And then we turned on this mock implementation because if we don't, then our original mock implementation is gonna throw an error and say, hey, you ended up calling console dot error. And here it is actual, let's see. It's gonna be in here somewhere where we're, oh, actually, no, that's failing for another reason altogether anyway.

[05:05] So yeah, you definitely wanna have this mock implementation so we don't log that error. And that takes care of the setup for our test. And then finally, we need to do the pre-setup for the server to make sure that we're overriding

[05:22] the access token HTTP post endpoint so that when the request comes in, we actually make it fail and then we can test the failure case in this case. And then finally, we want to restore the balance in the force. We want to restore things to their natural order

[05:41] having the happy path implemented in our GitHub API mocks. And so we say reset handlers back to the happy path. And that is overriding mocks with MSW.

Testing Error Handling in GitHub API Interceptor

[00:00] The way we've got this written is that any time anybody asks us for any access token, we will gladly create a new GitHub user for them and return an access token. So, it's not exactly the way that the GitHub API actually works, but it works really well for our local development.

[00:18] So, the trick is, we do have logic for what happens if we can't get an access token, if there's some sort of problem there, like maybe GitHub is down, or the code that was provided is invalid, or something like that. And so, we want to test that logic to make sure that never breaks,

[00:35] but our HTTP interceptor handler here is actually not coded in a way that lets us test that. So, we kind of need to override that for this particular test, and there's a way to do that. So, if we come over to our test, you're going to be writing a server.use,

[00:55] which will allow us to override a particular handler for this particular test, so that we can make sure that our logic for handling those errors is correct, and what we would expect what we want it to be. So, this is going to require that we export our server and make it accessible,

[01:14] which is exactly what we are doing right here. So, you need to import this server, and then add a server.use, but we want to make sure we clean up after ourselves as well, and so you're going to be handling that too. So, a couple of things to do on this one. Have a good time.

We all know the drill. The code works on your machine but you didn’t realize the impact of the change you made and it breaks in production. This problem grows exponentially as your application’s size and usefulness grows. Unpredictability can be a developer's worst nightmare.

However, many developers find it difficult to effectively test their code. Manual testing gets tedious fast. Complex logic and async code can be tricky to test effectively.

The Full Stack Testing Workshop will equip you with the tools you need to ensure your app works now and in the future. You'll learn how to write modular, maintainable tests that cover all of your code, from the backend to the frontend.

As the author of the de-facto standard testing library for web development (called eh… Testing Library), I have some solid opinions that have led many teams to much more confidence shipping their code. Let’s get you some of that confidence.

## End-to-End Testing with Playwright

With end-to-end (E2E) testing, you can validate a web app from the user's perspective. This is the closest you can get to a real user interacting with your app. In this section, you'll learn the ins and outs of writing a test with Playwright:

- Best practices for setup before running tests
- Simulating user actions like interacting with the UI to perform a search
- Creating a new user in the database
- Cleaning up after tests have run
- Using playwright fixtures for reliable setup/teardown

## Mocking & Authentication for E2E Tests

When your application relies on external services, you need to have a way to test them without actually using them. Similarly, you don't want to fully onboard a new account every time you test an authenticated user flow. In this section, you'll learn how to re-use the same mocks we’ve been using for development to mock third-party services and simulate logging in:

- Use Mock Service Worker to intercept network requests
- Replace email verification with a local file solution
- Attach cookies to Playwright
- Reusing 2FA logic for local testing
- Testing behavior with different HTTP responses

## Unit Testing

Sometimes you’ve got some really complicated business logic in your app. Business logic that is critical to your application. For this stuff, it’s nice to package it up in its own function or module to keep all that logic in one place. This is the perfect situation where lower level unit testing comes in handy. Here, we'll dive into unit testing with the Vitest framework to ensure that each function and module behaves as expected:

- Organizational best practices
- Asserting outcomes with `expect`
- Recording function calls with spies
- Specifying test behavior with Vitest hooks
- Keeping test output clean to avoid cluttering up the terminal

## Component and Hook Testing

When building React components, you should focus on two users: the user who interacts with a component, and the developer who renders it. By using Testing Library, we can avoid mocking React and its hooks and instead test components as they would be used in a real app:

- Render components with Testing Library
- Simulate the DOM environment on a per-test basis
- Querying for missing elements
- Testing hooks in isolation from React
- Stubbing React context
- Cleanup after testing

## Authenticated Integration

Similar to higher-level E2E tests, it is often necessary to simulate an authenticated user. However, we don't want to test the entire user flow every time we make a change. In this section, you'll learn how to test authenticated operations without the overhead of a full E2E test:

- Generating random session IDs
- Associating sessions with users
- Testing authenticated routes
- Asserting user state in responses

## Custom Assertions

Writing tests is good; writing readable and maintainable tests is better. Custom assertions can make your test code easier to understand and modify. Here you'll learn to encapsulate complex checks into simple, understandable assertions:

- Create matchers for specific states
- Share assertions across tests
- Add custom assertions to TypeScript definitions
- Format test output with colors for readability

## Test Database

There are some decisions to make when writing tests that interact with the database. Testing with the development database has benefits, but requires us to remember to delete data after each test. By using a test database, we can avoid accidents while still being able to run our test suites:

- Set up a test-specific database instance
- Seeding a minimal amount of data
- Defining a global setup for Vitest
- Understanding the importance of module import order

Learn how to write tests that cover all of your backend and frontend code. Web Application Testing covers unit testing, E2E, integration testing, and more!

Web Application Testing

Kent C. Dodds

Full Stack Vol 1

Intro to Web Application Testing Workshop

Intro to Web Application Testing 

Intro to End-to-End

Automate tests seamlessly in Playwright UI mode, mirroring manual tester actions. Validate search feature with Playwright's robust tools and intuitive interface

Playwright tests for user interactions, page navigation, search box inputs, and assert URLs, list elements, and items to test web app search functionality.

Writing and Asserting Playwright Tests for Search Functionality

Writing Automated Tests with Playwright UI Mode

Master isolated tests in Playwright and Node for better control, independence, and reliability. Import and run essential APIs for self-sufficient testing.

Create, manipulate URL with search parameters, display user data using encoding. Elevate your app's user data handling skills.

Creating and Interacting with User Data

Isolating Tests for Better Reliability and Flexibility

Clean up test data to maintain test isolation in end-to-end testing. Prevent data buildup in the development database, ensuring smooth, reliable workflows.

Incorporate user deletion in setup and teardown for a pristine testing environment, eliminating unwanted data and ensuring a clean slate for every test.

Proper Setup and Teardown of Testing for Database Cleanup

Test Isolation in End-to-End Testing

Utilize Playwright fixtures to guarantee thorough database cleanup, eradicating test-created user data, bypassing potential pitfalls from alternative methods.

Use Playwright fixtures for custom test objects, properties, behaviors, execute functions strategically, and manage data cleanup efficiently.

Playwright Fixtures for Testing

Implementing Fixtures to Ensure User Deletion in Playwright Tests

Take a break, nourish yourself, hydrate, and jot down your learnings to keep your brain sharp. Let's continue the great work with more testing ahead!

Dad Joke Break E2E

End-to-End

Address HTTP/S validity with a mock server and stub, this makes it easy to ensure that a client's response is consistent

Intro to E2E Mocking

Capture, save verification codes for smooth server-test automation communication.

Master Node.js email read/write with the File System module. Save, retrieve email data for testing efficiently.

Handling Emails in Node.js using File System

Writing Emails to the File System for Test Automation

Quickly grasp requiring and using disk-stored email data in tests for successful content reading. Crucial for test setup and execution.

Enhance process-to-process communication in Node.js using the secure file system method. Elevate data transfer and parsing capabilities.

Communicating Between Processes with File System in Node.js

Reading Email from Disk in Test Environment

Quickthink about the punning methods you will employ to share skeins of mirth with your fellow yo-cards

Dad Joke Break E2E Mocking

End-to-End Mocking

Learn how to simulate an authenticated user in your tests by generating and adding cookies to the browser context, improving test efficiency and isolation.

Intro to Auth E2E

Master end-to-end user flow tests, streamline authentication, and navigate login, profile editing, 2FA, and login verification.

Simulate user login, set cookies in browser tests to mimic web app authentication accurately.

Login and Setting Cookies for Browser Testing

End-to-End User Flow Testing and Authentication Utility

Dad Joke Break Auth E2E

Authenticated End-to-End

Intro to Unit Test

Craft solid unit tests for getErrorMessage, covering various scenarios and input-based error messages. Test pure and impure aspects thoroughly.

Master unit testing for utility functions, cover error handling, and achieve full code coverage with tools like coverage reports.

Writing Unit Tests for Utility Functions

Unit Testing a Function for Error Messages

Minimize test output logs, mock console.error for cleaner testing. Master spies for focused, effective testing without excessive console noise.

Utilize spies to track, assert console.error calls in tests. Ensure correct arguments and preserve valuable error info.

Testing Console Error with Spies

Managing Test Output and Error Logging with Console Mocking

Utilize Playwright testing hooks for error restoration and default mock restoration to enhance test stability.

Learn how to restore mocks by default, capture and handle console errors, and create a shared console error setup for efficient JavaScript testing.

Effective Error Handling and Console Capture Testing

Implementing Test Hooks for Error Restoration in Playwright

Create a setup file for automatic inclusion of essential files in all test files, closely simulating the production environment for effective testing.

Set up a test directory with setup files using VTest to automate configuration and common tasks. Ensure smooth test execution and robust error handling.

Setting Up Test Environment and Utilizing Setup Files with VTest

Creating a Setup File for Test Environment Setup

Dad Joke Break Unit Test

Unit Testing

Intro to Component Testing

Efficiently test Error List component rendering with React Testing Library. Gain hands-on experience across diverse test cases.

Simulate DOM with JSDOM for React component testing, skip the browser. Utilize Testing Library, tackle challenges, and hone your skills.

Testing React Components with JSDOM

Error List Component with React Testing Library

Fix test failures from DOM manipulation with proper cleanup techniques for reliable, efficient testing.

Maintain test isolation, eliminate dependencies on test state, and ensure clean execution in Testing Library with effective test cleanup.

Ensuring Isolation and Proper Test Execution

Proper DOM Cleanup for Reliable Testing

Dad Joke Break Component Test

Component Testing

Intro to Hooks

Create a double confirmation feature in React with a custom hook. Explore implementation,testing with RenderHook and Act. Prevent accidental actions effectively

Master custom React hook testing with RenderHook and Act from Testing Library React. Access hook properties through result.current for precise testing.

Testing Custom React Hooks with RenderHook and Act

Double Confirmation Feature

Test hooks with flexibility. Use custom test components or the render hook utility. Tailor your approach to your testing needs and preferences.

Create test components for thorough React hook testing, ensuring API contracts, and validating state changes accurately with Testing Library React and UserEvent

Testing React Hooks

Custom Test Components vs Render Hook Utility

Dad Joke Break Hooks

Hooks

Ensure test-driven development (TDD) by writing testcases from the get-go and developing integration tests quickly in isolation.

Intro to Testing Remix 

Master Remix stubs for isolated component testing, handle edge cases, simulate user states without full end-to-end testing.

Use CreateRemixStub for Remix components with mock data. Test integration with React Testing Library for proper rendering and DOM element waiting.

Rendering Components with Mock Data

Creating a Stub for Testing Component Logic in Remix

Fix a failing test by adding a parent route granting access to root data. Ensure proper rendering and testing of the username route in authenticated settings.

Create authenticated integration tests in Remix by configuring root routes, loaders, and context for precise testing of user interactions.

Creating Routes and Context in Remix

Creating a Parent Route for Accessing Root Data

We interrupt your couch time for this important reminder. Oh, and to keep you feeling healthy and vibrant.

Dad Joke Break Testing Remix 

Testing Remix

Learn how to mock APIs using MSW to enhance testing reliability, handle different scenarios, avoid dependencies, and ensure test isolation.

Intro to Http Mocking

Manually test and modify GitHub sign-in callback in your app. Adjust user association, validate response cookies, and location headers for robust functionality.

Simulate OAuth2 flow, effectively mock GitHub API requests in tests. Ensure robust verification of authentication and API integration in your app.

Testing OAuth2 Flow and Mocking GitHub API Responses

GitHub Sign-In Callback

Learn how to avoid repeating test code by creating reusable functions and avoiding excessive duplication, ensuring efficient and maintainable testing workflows.

Organize code better with bottom setup functions, reduce repetition, and boost readability through parameterization and code sharing.

Efficient Code Organization with Setup Functions

Streamlining Repetitive Test Setup for Optimal Efficiency

Dad Joke Break Http Mocking

HTTP Mocking

Intro to Auth Integration

Master testing authenticated requests & connections post-login. Simulate sessions, verify for code reliability.

Master user setup, authenticate, and manage connections, including GitHub and DB users, sessions, and test cleanup. Deep dive into authentication.

Creating and Authenticating Users for Connection Setup

Testing Authenticated Requests and Connection Creation

Verify GitHub login session creation with assertions. Cover scenarios like connecting accounts and non-logged-in users.

Extract, check, parse server response's session cookie for user authentication, ensuring DB session creation.

Verifying Session Creation and User Authentication

Assertions for GitHub Login Session Creation

Swap fake data with real user info in routes, use utilities for seamless database user insertion and deletion.

Real DB interactions for user creation/deletion, image addition, request authentication in integration tests. Full UI coverage, no heavy mocking.

Authentication in Database Integration Tests

Integrating Real Database with User Routes

Dad Joke Break Auth Integration

Authenticated Integration

sanityVideoMuxId: gndUuMl8O02HCDPqYUGRa1o2oUxoiYsRoakUQ802ZtPnc

Intro to Custom Assertions

Enhance test assertion readability and functionality by creating custom matchers like assertRedirect. Elevate code clarity and error messages.

Elevate your testing game with custom assertions in Jest. Create "to have redirect" and more for precision. Organize in a test util directory for collaboration.

Custom Assertions with Jest's Expect Library

Custom Matchers for Assertions

sanityVideoMuxId: pmPD6AekZgJhQP2kES5V2aErPtkkyA00GTSVfLcRp4ys

Dad Joke Break Custom Assertions

Custom Assertions

Extend the Gradle plugin to suit the needs of your projects. Learn about exploring a Cucumber-JVM Gradle boolean condition or approach using

Intro to Test Database

Set a test database with a URL before importing Prisma for seamless client testing. Master import order and setup for success.

Learn how to properly set up an isolated database for testing purposes using Prisma and dynamic imports, ensuring a clean and efficient testing environment.

Setting Up an Isolated Database for Tests

Setting Up a Test Database for Prisma Integration Tests

Learn how to solve conflicts when running tests simultaneously by setting up individual test databases to avoid shared state and data interference.

Learn how to create and manage isolated test databases using unique identifiers, allowing for efficient and independent testing processes.

Isolating Test Databases for Efficient Testing

Managing Test Databases for Parallel Testing

Speed up test execution with a global setup module. Enhance efficiency for faster, full database tests.

Learn how to set up a base database for faster test execution, avoiding repetitive migrations, and utilizing the real database environment efficiently.

Optimizing Test Setup with Global Database Configuration

Optimizing Test Setup

Take a well-deserved break before applying the acquired knowledge to your own projects. Well done!

Dad Joke Break Test Database

Test Database

Discover how to set up and integrate various testing tools, both at the UI and lower levels, to enhance your app's stability and facilitate easier test creation

Web Application Testing

Web Application Testing

Transcript

Testing Error Handling in GitHub API Interceptor

Transcript