Tests

The agents rely on your project’s tests: they run them before development and afterwards check that the changes broke nothing. To make this transparent, a project has a section where all the tests and their state are visible.

The “Test settings” section

The project’s left-hand menu has a “Test settings” item. It shows the full list of the project’s tests on the main branch and the status of each:

• active — the test takes part in runs;
• disabled — temporarily taken out of the run (with the reason given).

When the section appears

The item becomes available once the development tools have been prepared for the project — before that the project cannot list its tests yet. The list is produced by the project’s own development tools, so what it contains depends on which tests exist in the code.

Freshness and refreshing

The list is taken for the main branch and refreshed automatically when the project changes. Under the heading you can see how many tests are in the list and when it was taken. The “Refresh” button rebuilds the list by hand — while a refresh is running, the button is locked and shows progress (two refreshes never run at once).

What next

A separate topic is how tests that were failing before your task are handled: the agents should not spend time on them, and the decision about them is yours.