The Chorus interpreter includes some built in Handler Classes
Each of these provides step definitions which can be used to accomplish various common tasks. These handler classes provide definitions for steps in your feature files, just like your own handler classes.
In addition, some extra Handler Classes are provided as Chrous extensions. These are included automatically when you install the interpreter as a command line tool, or via the Docker image
When you use Chorus within a Java project as a JUnit Suite, you will need to declare an additional dependency on these extension libraries. Using them may bring some additional transitive dependencies onto your test classpath.
Handler Name | Description | Type |
---|---|---|
Remoting | Connecting to run steps on Java/JVM components | Built In |
Processes | Starting and stopping processes | Built In |
Chorus Context | Manipulate a map of variables within each Scenario | Built In |
Timers | Timing and sleeping | Built In |
Web Sockets | Web Sockets support for Browser clients | Extension |
Selenium | Using Selenium to interact with Browsers | Extension |
SQL | Running SQL Scripts on Databases | Extension |
You need to use the Chorus keyword Uses:
to indicate you want to use the steps in a built in handler, just as you
would with your own handler classes:
Uses: Processes
Uses: Remoting
Feature: My feature using both processes and remoting
Scenario: Scenario one