Skip to main content

Features

What the plugin adds to your IDE, one area per page. The Everyday pages cover the language support and the workflow you are in all day. The As needed pages cover the features you switch on when a job calls for them.

A few words used throughout​

These pages assume you have a spec file open. If some of the words are new, this is all you need:

  • Spec file — a .feature or .specb file: the Gherkin text describing behaviour.
  • Step — one line of a scenario, beginning Given, When, Then, And or But.
  • Step method — the Java method that runs when that step runs. SpecBinder pairs the two by name, worked out from the step's wording.
  • Generated test class — the JUnit test SpecBinder writes from your spec file when the project is built. You do not edit it. You write a class that extends it, and you fill in the step methods.
  • Execution report — a JSON file SpecBinder can write when your tests run, recording what each scenario and step did. Several features here read it, and they say so where they do.