react.tar.gz

Run Tests

Run Tests - No Reset

Jest is a framework for testing applications developed in JavaScript. It has a well-documented and well-maintained range of tools to run tests in parallel. It is simple and works with projects using Babel, TypeScript, Node, React, Angular, Vue, etc. It works well for both client and server testing. 

This course covers Jest in-depth and is agnostic of any specific JavaScript framework. The course begins with the fundamentals of Jest testing, deconstructing the components of a test and covering how to compose basic unit tests and snapshot tests with Jest correctly. Next, it shows the testing of asynchronous code and the code that relies on external dependencies. Lastly, this course illustrates how Jest testing can effectively integrate into the real-world software development cycle through CI/CD pipeline.

It gives you hands-on experience in setting up Jest, types of testing, testing coverage, mocking, and native tooling depth.

…. To come 

… to come 

Mastering Jest: A Complete Guide to Testing

Which is _not_ an option for configuring our test setup?


Which is not an option for configuring our test setup?

Which is _not_ an option for tearing down our test configurations?


Which is not an option for tearing down our test configurations?

They help keep our tests isolated from each other.


They run our expectations and assertions for us.


They allow  us to abstract repeated work, like making custom matchers available.


They provide additional resources for debugging our tests.


**(Select all that apply.)** Why is test setup and teardown important?


(Select all that apply.) Why is test setup and teardown important?

**(Select all that apply.)** Which options are valid setup and teardown hooks?


(Select all that apply.) Which options are valid setup and teardown hooks?

The `setupFilesAfterEnv` code runs at the same time that the `process.env` variables are made available, whereas `setupFiles` occurs before.

The `setupFilesAfterEnv` code runs after our test environment has fully executed, where as `setupFiles` runs before our tests have fully executed.

The `setupFilesAfterEnv` code runs after Jest is installed in our test environment, where as `setupFiles` runs before Jest is installed.

The `setupFilesAfterEnv` code runs after Jest is installed in our test environment, where as `setupFiles` runs just after `setupFilesAfterEnv`.

What is the difference between `setupFiles` and `setupFilesAfterEnv`?

What is the difference between <code>setupFiles</code> and <code>setupFilesAfterEnv</code>?

A hook inside of a `describe` block is scoped to which test?


A hook inside of a <code>describe</code> block is scoped to which test?

Quiz yourself on setting up and tearing down Jest tests.

Introduction

Setting Up Jest

Jest Matchers

Writing Unit Tests

Writing Snapshot Tests

Asynchronous Code

Mocking

Mocking External Libraries

Working with Jest Mocks

Setup & Teardown

Test Coverage & CI/CD Pipelines

Test Coverage in Jest

Conclusion

Bonus: Best Practices

Bonus: Resources for Continued Learning

Appendix

Quiz on Setup and Teardown