Everyday | SpecBinder

📄️ Editing spec files

Highlighting, element folding, formatting, completion, spell checking and the structure view.

Reviewing the test class SpecBinder generates from a spec file, line by line, in the Test Code pane beside the spec.

Reading the step method behind each step, in the Test Code pane, as the caret moves down the spec file.

Running a feature, a rule, a scenario or one Examples row from the editor, and debugging in the spec file.

Bringing run results back into the spec file — the status of each scenario in the gutter and on the toolbar.

Reading why a scenario failed without leaving the spec file — the failure mark on the step and the error panel beneath it.

Finding every spec file step that a step method implements, from the Java code.

Rename and Change Signature on step methods, with the step text in the spec files changed at the same time.

A content type on a doc string, giving its body the editor support of that language and, for images, SVG and HTML, a rendered preview.