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

[00:00] The first thing I need to test this greet function is to know what is the actual greeting it returns. So let's call it with a particular argument using John as a username and store the greeting message in a new variable called "message". Then I will compare this actual message with the one I expect,

[00:15] so "Hello John". But here's the thing, I don't really care about the cases when this function works as expected. I want to have this test in place so it lets me know when the function doesn't work as expected. So I'll flip this condition and only trigger it if the actual message doesn't equal "Hello John" and if that happens I will throw an error message basically

[00:34] letting me know about this. Let's give this code now a try by running it in the terminal. So npx dsx greets dot yes and you can see that the process exited gracefully because there were no errors thrown during the execution. This means that our test was successful. This is a very minimal

[00:51] automated test on its own. So we have our system under test, the greet function, we provide a particular input, the John username, and then we compare the actual greeting message with the expected one and notice how now our intentions actually live in the test, in the code. And if those two are not the same we will throw a meaningful error message letting us know that

[01:10] our implementation doesn't really fulfill the intention.

Write an Intentional Test

[00:00] We would like to greet any user who joins our app with a nice greeting message. So if John joins, he would say, "Hello, John." If Sarah, "Hello, Sarah." To do that, we have a greet function that accepts a name, argument, which is a string, and returns a greeting string, so "Hello, name." A very simple way to test this function is just call it.

[00:19] So let's call greet and pass it a name, for example, "John." We can observe this result if we just console.log whatever this function returns. And run this greet.ts module in the terminal using npx tsx greet. So we can see that it prints, "Hello, John," which is exactly what we expect. But here's the problem.

[00:40] This expectation really only lives in our head. It would be really nice to automate this process and also put this intention into code. So this will be a task for this exercise. Write a very minimal automated task, which consists basically of three steps, calling your tested code with particular input,

[00:56] then taking its output and checking it against the expected result, and then if those two don't match, throwing an error. So give it a try, and see you in a bit.

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 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'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

Handling Promises in Tests

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.

Testing Fundamentals

Testing Fundamentals

Transcript

Implement the Automated Greeting Test

Transcript