Getting Started

There are several ways to run the Chorus interpreter, depending on the needs of your project

No matter how you run Chorus, the same parameters are supplied to the interpreter to invoke the tests

How to write Chorus tests:

  1. Write tests in plain English (as .feature files following the standard Gherkin syntax.
  2. Run the Chorus interpreter, providing it with a path to find your feature files.

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:

  1. Supply java classes on the interpreter’s classpath which implement the test steps in your feature files. These classes are called ‘Handler’ classes

  2. 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

  3. 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