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

**(Select all that apply.)** What are the main globals that Jest provides for organizing our test suites?


(Select all that apply.) What are the main globals that Jest provides for organizing our test suites?

`describe.each(table)(name, fn, timeout)`

Which global variable can be used to run a test suite with multiple sets of data?

Which global variable can be used to run a test suite with multiple sets of data?

Which global is useful in documenting tests that need to be written?

Which global is useful in documenting tests that need to be written?

Which global is useful when using TDD or documenting a bug that needs to be fixed?


Which global is useful when using TDD or documenting a bug that needs to be fixed?

**(Select all that apply.)** What does writing unit tests help to enforce?


(Select all that apply.) What does writing unit tests help to enforce?

**(True or False)** Tests can be nested with `describe` and `test` infinitely.

(True or False) Tests can be nested with <code>describe</code> and <code>test</code> infinitely.

One testing file for the app, including test suites reflective of individual files

One testing file for each code file in an app with either one or multiple test suites, depending on the file being tested

It doesn’t really matter as long as we have enough tests.


One test file per directory with a test suite for each file inside of the directory


Which option best describes a good testing file structure?

Which option best describes a good testing file structure?

Quiz yourself on the fundamentals of writing unit tests with Jest.

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 Writing Unit Tests