Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
77 lines (51 sloc) 3.8 KB
id title permalink layout category prev next
Testing Components
Getting Started

Bit can run the component's tests in an isolated component environment.

The testing process of bit components is done in an isolated component environment, using testers, which are environments - a special kind of extension.

Executing components tests

In order to test a component, you need to have a tester defined.

Defining a tester for your project

A tester is defined per Scope, and once defined, testing a component within that Scope will test the component using the defined tester. In order to do that, just import the tester:

$ bit import bit.envs/testers/mocha --tester
the following component environments were installed
- bit.envs/testers/mocha@0.0.7

You can now go take a look at the env configuration in your bit.json and see your tester over there.

Curated list of test environments on

You can find a list of Test environments maintained by the team here.

Adding test/spec files to your components

Bit is not going to guess which files are your spec files, right? You should track your spec files correctly.

Test your component

Once you have a defined tester, you can test your component:

$ bit test foo/bar
tests passed
file: dist/test/bar.test.js
total duration - 4ms

✔   bar should do nothing - 1ms


If you have a compiler defined, testing a component will also cause Bit to build it first.

Executing component tests remotely

When staging or exporting components, Bit runs the components' extensions in an isolated component environment. So the test process for the component will run outside the context of the project. This allows Bit to make sure the component is truly isolated.

Self-managed Scope

After exporting a component to a self-managed remote Scope, the component will be built and then tested in the remote Scope in an isolated component environment. Scope

After exporting a component to a managed Scope, will create an isolated container, where the component will be built and then tested in the remote Scope in an isolated component environment. When the tests have finished running, their results will be displayed as part of the component's documentation on As the Scope owner or collaborator, you can enter the component page on, and view the CI results in the Console Output tab.

Implementing a tester

You can implement your own custom tester. See here for more details.