In this problem, you'll need to figure out how to adjust the test function to support asynchronous callbacks.

Learn how to handle asynchronous functions in tests by using the `await` keyword and marking test functions as asynchronous. 

Awaiting Async Tests

[00:00] I will start by going to the implementation of the test function that we have in set_up.ts file. Because our test, our callback, is an asynchronous function now, in order to await the promise introduced by the greet_by_response function, we also need to await it in the test, to even know its status, whether it's failing or passing, so we can properly report it in the console.

[00:19] Because we're using the await keyword now, we need to mark the whole test function as asynchronous. Once we do that, we can run the tests, and we can see this failing test being correctly reported as failing. In fact, you can see that the order of this test is a little different. So the first and the third tests run first, and then this test, which is asynchronous, concludes the last.

[00:39] Now we can take a look at this assertion, and we can see that it's failing. We're expecting "Hello, Patrick!" from here, but we're actually getting "Hello, Undefined!" So this strongly suggests that what we're passing as a username is not defined, or maybe we're accessing it incorrectly. So here, we are passing this response to the function, and it looks okay. So let's take

[00:58] a look at the function itself. We're expecting to read the response body, store it in a user object, and access the firstName property. Now, that doesn't look right. I think in our test, we're actually using the the name property. So let's adjust it to be firstName, and rerun the tests.

[01:13] With this change, the tests are passing correctly. You may be wondering, "Haven't I just learned that I should always trust the test?" That is true. You should always trust the expectations described in the test. But in this case, the expectation stays the same. The problem was in the testing setup.

[01:29] In this mock response we prepared, in order for this readByResponse function to even run, we simply prepared a response with an object that was not compatible with what we have in the function. So it was accessing the property that doesn't exist. The big takeaway from this exercise is that remember that you should always await the synchronicity you introduce. Like this,

[01:48] readByResponse function returns a promise. So make sure to await it to have this test pass reliably

Handling Promises in Tests

[00:00] We have a new function called "greetByResponse", and the purpose of this function is to accept a response, which is a Fetch API response object, read its body as JSON, and then pass the first name from that user object to the greet function that we already have. Since reading response bodies is an asynchronous operation, we await it,

[00:18] which also forces us to mark this "greetByResponse" function as an async function. We already have a test written for this function right here that basically constructs a mock response and then passes this to this greetByResponse function, awaits the result, and asserts on the proper greeting message returned.

[00:36] If we try to run this test, though, we will spot something peculiar. We can see that there is all three tests that we have, and they are marked as passing. However, right below this, there is a suspicious error that looks a lot like the failed assertion from here, because what's happening is that our test function

[00:54] executes this callback, the actual test, without awaiting any asynchronous operations inside of the test. So it prints the test as passing straight away. However, the actual promise returned by the greetByResponse function then resolves to the string that doesn't match the string that we expect.

[01:13] Your task for this exercise will be to adjust the test function to support asynchronous callbacks. And once you do, see if you can spot any issues with this test and resolve them.

Discord

Email

GitHub

Writing tests for their own sake is a pointless chore:

```tsx
describe('add numbers', () => {
  it('should add two numbers', () => {
    expect(add(1, 2)).toBe(3)
  })

  it('should add two other numbers', () => {
    expect(add(3, 4)).toBe(7)
  })
});
```

Another annoying testing problem is when tests are too brittle, and paint your logs red even though the application seems to work just fine.

When your tests lack real purpose or seem to fail for no good reason, it's no wonder you start to question their value.

Tests are supposed to give you confidence in your code, and save you from shipping broken stuff to prod. So why does writing them feel like such a burden?

The problem is that tests like these are focused on implementation details instead of the underlying behavior. Everyone talks about the importance of testing, but there's a lack of understanding about how to write tests that are actually useful.

How would it feel to have 100% trust in your tests, knowing that any failures are not a false alarm? What if you could seamlessly translate the underlying behavior of your application into tests that are easy (and even fun) to write?

It's possible, but it requires you to take a step back from just syntax.

In order to have the confidence you're testing the right things in the right ways, you need to dig into the underlying patterns behind the scenes of a testing framework.

This is exactly what you will do in Testing Fundamentals.

In this workshop, Artem Zakharchenko, testing expert and creator of the Mock Service Worker API mocking library, will guide you through creating your own version of the Vitest testing framework.

Building a testing framework from scratch will give you a deep understanding of how the pieces fit together, and change the way you think about testing for the better.

## What You'll Learn

The workshop is broken out into four parts, each with its own challenges and exercises that build upon the last:

### Principles

First, you'll explore the principles and mental models that underlie testing strategies. This is where you will begin to distinguish between the intention of your code and its implementation details. When you focus the intention of what your code should accomplish, you can write tests that are more resilient to change.

### Test Structure

Next, you'll do a deep dive into the structure of the testing framework. You'll create your own `expect` and `test` functions, configure your test environment, and use hooks to manage side effects in your tests.

### Testing Asynchronous Code

Testing asynchronous code requires a slightly different approach when compared to testing synchronous code. Here you'll practice with testing promises and async functions, as well as handling errors and rejections.

### Moving to Vitest

Once you've learned the fundamentals of testing and built your own mini-framework, you will migrate your tests to the Vitest framework. This process will cement your understanding of not just the "hows", but also the "whys" of testing.

## Who This Workshop Is For

This workshop is for developers who have some testing experience, but feel like they're missing the bigger picture. If you're tired of writing tests that feel like a chore, and want to understand how to write tests that are actually useful, this workshop is for you.

In the Testing Fundamentals workshop, you will learn testing principles, framework structure, async handling, and more by building a mini testing-framework!

Testing Fundamentals

Artem Zakharchenko

This workshop covers testing framework structure, asynchronous code, and migrating to Vitest.

Testing Fundamentals Workshop Introduction

Introduction

In this first section, you'll learn by example the core principle of having intentions when testing.

Overview of Testing Principles

Learn how writing an automated test captures your intentions, while manually calling console.log() and viewing the result only really lives in your head.

Learn how you can explicitly define your intentions and automatically test your code without any testing frameworks.

Implement the Automated Greeting Test

Write an Intentional Test

Learn how to create an expect function that provides a readable API for writing tests and refactor existing tests to use it.

Trusting Your Test

Debugging Intent vs. Implementation

You've completed the principles exercise!

Testing Principles Outro

Principles

In this exercise, you will learn about the setup, action, and assertion phases of automated testing and how they applied to testing our simple greet function.

Structure Your Tests

Learn how to write declarative and readable assertions in your TypeScript tests using a custom expect function.

Implement a Declarative API

Imperative vs. Declarative Assertions

In this exercise, you will figure out how to create a test function to isolate and report test results.

Learn how to create a simple testing function in JavaScript to wrap existing tests, provide meaningful test names, and display visual indicators.

Create Test Blocks for Better Organization

Isolating Tests with Test Blocks

In this exercise you'll be figuring out how to separate the test cases into a separate module and make testing functions globally available.

Learn how to gracefully move tests to a separate file, export functions, make test functions global, and run tests using Node.js.

Modular Tests and Global Helpers

Move Tests into Modules

Learn how to handle side effects introduced by the Date constructor in your JavaScript tests.

Create global hooks for setup and tear-down, mock the Date constructor using a Proxy, and then restore it after your tests are ran.

Implement Hooks for Test Setup & Cleanup

Handle Test Side Effects

You learned how to write declarative assertions, provide test isolation, put your tests in separate files, and deal with testing setup.

Test Structure Recap

Test Structure

In this exercise, you will expand your testing library to support testing asynchronous code, and then write tests for an asynchronous greet function.

Overview of Testing Async Code

In this problem, you will need to figure out how to handle a pending promise and then chain .rejects.toThrow on expect.

In this solution, you'll learn how to use the object chaining syntax to extend the `expect` function with a new assertion called `rejects`.

Handling Promise Rejections

Error Assertions for Rejected Promises

In this problem, you'll create a waitFor method that can await state changes to a notification manager.

Learn how to use a waitFor method to retry a callback until it no longer throws an error or until the maximum number of retries is reached.

Reliably Wait for Async Operations

Testing with Async Side Effects

You've learned about asynchronicity that you can and can't control, and testing strategies for dealing with both.

Recap of Testing Asynchronous Code

Testing Asynchronous Code

In this final section, you'll be migrating your tests to Vitest.

Overview of Vitest

Your task is to follow the outlined steps to migrate your project from your custom framework to Vitest.

Congrats! You are now ready to apply everything you've learned today about testing in practice!

Installing, Configuring, and Testing in Vitest

Migrate Tests to Vitest

Outro to the Moving to Vitest section of the Testing Fundamentals workshop.

Vitest Review

Moving to Vitest

After completing this workshop you are now equipped to approach any test. There is a lot more to learn about testing! Be sure to check out the linked materials.

Get access to EpicWeb.dev

And continue watching this video