Test Case Templates

Testiny test cases utilize a template system, so you can select the best-fitting template for the individual tests.
Testiny offers three templates — Steps, Text and BDD — which you choose per test case in the Template field of the details section. The template defines how the steps area of the test case looks.

| Template | Steps area | Best suited for | | --- | --- | --- |f | Steps | Numbered steps, each with its own expected result | Step-by-step procedures with a result per action | | Text | Two free-text fields: steps and expected results | Exploratory tests and less structured tests | | BDD | One Gherkin Scenarios field | Behavior specifications written in Gherkin |

All templates use our built-in text editor. In the Steps and Text templates you can format everything the way you want; in the BDD template the editor highlights the Gherkin syntax of your scenarios instead.

Steps Template

Within the steps template, an individual step belongs to an individual result. This kind of template is ideal, if you have a sequence of steps or actions with an explicit result or outcome, belonging to an individual action. The steps template also supports rich text editing.

Hotkeys

Testiny’s editor supports various keyboard shortcuts to make editing test cases easier and faster. In the steps template, you can add or remove steps, and navigate between steps using keyboard shortcuts. Please refer to the full list of keyboard shortcuts.

info

To open the help and playground directly in Testiny, click the icon in the upper right corner above the steps input field.

Text Template

The text template provides two multiline text areas, one for steps and one for expected results. This kind of template provides the most freedom when writing test cases. It is ideal for e.g. exploratory tests, where individual steps or actions don’t necessarily belong together one by one. Both fields support rich text editing, as shown in the example below.

BDD Template

The BDD template replaces the steps and expected result fields with a single Scenarios field holding plain Gherkin — the Given/When/Then language used by Cucumber, SpecFlow, Behave and Xray. Use it when the behavior under test is described in Gherkin, so that the specification and the test case are one and the same.

Testiny highlights the Gherkin syntax, validates it against the Gherkin grammar while you type, supports 20 Gherkin dialects, and exports the test case as a .feature file.

Two differences to the other templates are worth knowing before you switch:

• The test case title is the feature name. You do not need a Feature: header in the scenarios.
• There is no precondition field. Use a Gherkin Background section within the Scenarios field instead, so that setup shared by all scenarios stays part of the specification.

See BDD Test Cases with Gherkin for the full details, including the supported dialects, the feature file export, and how BDD test cases behave in test runs and reports.