Testing
Automate testing in Conductor
After you make changes in a workspace, test them with either an action or Spotlight testing.
Actions test from the workspace directory. Spotlight testing syncs one workspace back to the repository root and tests from there.
Actions
Use an action to launch your web server, app, test watcher, or unit tests from the Run button in Conductor's workspace toolbar.
Actions execute in the workspace directory. They can use $CONDUCTOR_PORT, so multiple workspaces can run their own copy of the app without fighting for the same port.
For setup details, see Actions reference.
Spotlight testing
Use Spotlight testing when your project needs to run from the repository root instead of the workspace directory. Enable it in Repository Settings for the project you want to test, then use the Spotlight button from the workspace toolbar.
When Spotlight is on, Conductor syncs tracked workspace changes back to the repository root and opens a terminal there. Because Spotlight testing is configured per repository, you can decide which projects use root-based testing and which projects keep isolated workspace actions.
For when to use Spotlight instead of an action, see Spotlight testing.
Running microservices at once
Conductor only supports automating testing one service at a time. If your application requires microservices to be tested at once, see Linking multiple directories.