Use BDD - Gherkin to describe a test scenario as its starting conditions, action, and expected outcome. This format helps testers and other team members review the intended behavior in familiar language.
Select BDD - Gherkin
Open the Test Case and select the intended version.
Open the Test Script tab.
Use the script-format selector to choose BDD - Gherkin. Resolve any unsaved-change prompt first.
The screenshot shows an older layout of the format selector.
Write one scenario’s steps
Enter the scenario’s steps directly in Vansah. The editor supplies its own Feature and Scenario wrapper for validation, so do not paste a full feature file with Feature: or Scenario: headers into this step editor.
Given a customer is signed in
And the customer has an empty cart
When the customer adds one available product
Then the cart shows that product with quantity 1
And the cart total matches the product price
Keyword | Purpose |
Given | Set the starting conditions. |
When | Describe the action or event being tested. |
Then | State the observable expected outcome. |
And / But | Continue the preceding conditions, actions, or outcomes. |
Use specific outcomes that a tester can check. Keep unrelated behaviors in separate Test Cases. For general Gherkin guidance, see the Cucumber Gherkin reference.
Save and check the script
Review the sequence and expected outcome.
Select Save.
If Vansah reports invalid syntax, correct the script and save again.
Reopen the script to confirm the saved text.
Use the standard spelling Given, When, Then, And, and But. Vansah normalizes their capitalization for validation; lowercase alone is not a reason to assume the current editor will reject the script.
Resolve a syntax error
Start with at least one valid step. A heading or description alone is not a test scenario.
Remove Feature, Scenario, and Scenario Outline headers from this scenario-step editor.
Check keyword spelling and complete any data table or multiline text correctly.
Use ordinary text for values; do not include Markdown code fences around the whole script.
Saving Gherkin documents the scenario. It does not create automation step definitions or run your application automatically. For manual execution, see Execute a BDD Test Case. For structured manual steps, see Multi Steps Test Scripts.