- Using a Custom NPM Registry
- GitHub Committing and PRs
- Importing Sandboxes
- Collaboration with Live
- How does CodeSandbox runs tests?
- How to write tests in the CodeSandbox Client Sandboxes
- Test Failures
- Deploying your Sandbox
- Preferences Profiles
- Uploading Static Files
- Explore Page & Curators
- CodeSandbox CI
CodeSandbox has a native integration with a test runner.
CodeSandbox uses Jest library to run the tests directly in the browser. That means you can write tests, but adding additional plugins is not possible in the Client Sandbox experience.
In Client sandboxes you can run Jest tests by creating
files that end with
will automatically detect these test files and show the results in the Tests
Note: In Container sandboxes you can still use Jest (or whichever test framework you want), but we don't auto-detect these and you'd need to set it up yourself as you would locally.
The left side of the test view is an overview of all test files. The right side shows the details of a file when you select it. You can decide re-run tests manually by clicking on the Play icon. We automatically watch for file changes, but you can disable this by clicking on the 'Refresh' icon on the left side.
We show failed tests in two ways: in the test overview and in the code editor itself.
A failed test looks like this in the Test View:
And will also show squiggles in the editor:
Here's a failing Jest test running in a sandbox: