There are several ways to run the Chorus interpreter, depending on the needs of your project
Integrated with a Java project as a JUnit test suite:
Add Chorus as a maven/gradle dependency, or download it as a jar dependency
As a Docker container in a Docker-enabled environment:
Use a Docker image downloadable from Docker hub
From the command line:
Download Chorus and install it as a standalone installable package
No matter how you run Chorus, the same parameters are supplied to the interpreter to invoke the tests
At this point your tests will run, but they will fail because you have not yet provided an implementation for your test steps
There are several ways to provide implementations of test steps to Chorus:
Supply java classes on the interpreter’s classpath which implement the test steps in your feature files. These classes are called ‘Handler’ classes
Make use of built in step definitions from Chorus’ Built In Handlers. These provide a library of generic test steps to solve various common problems
Use Chorus’ client libraries to publish step definitions from components running in a test environment. Chorus can also start these components locally using its Process Control