Skip to main content

Execute a BDD Test Case Manually

Run a BDD scenario in Vansah, record the actual outcome and evidence, and distinguish manual execution from automated Cucumber tests.

You can execute a BDD Test Case manually in Vansah. Read the Given–When–Then scenario, perform the actions in your application, and record the actual outcome and result for the script.

Before you begin

  • Save the scenario in BDD - Gherkin format.

  • Link the Test Case to the Jira work item, Test Folder, or Test Plan you intend to test.

  • Confirm the Test Case version, execution context, and any required Environment, Version, or Sprint. In a Test Plan, also confirm the requirement and iteration.

  • Make sure your account has access to the Jira space and permission to execute Test Cases.

Start the Test Run

  1. Open the linked Test Case in the intended work item, folder, or plan.

  2. Select the execution control for the case. If prompted, choose the linked work item or Test Folder and complete Run Setup.

  3. Select Execute to open the Test Run.

  4. Confirm the run’s context and read the BDD script before testing.

For the available execution entry points, see Executing Test Cases: Overview.

Record the outcome

  1. Establish the conditions described by Given.

  2. Carry out the action described by When.

  3. Compare the observed behavior with Then and the remaining expected outcomes.

  4. Enter what happened in Actual Result, add relevant evidence, and save it.

  5. Select the appropriate result. Use an in-progress outcome if testing is not complete.

  6. Reopen or refresh the run and confirm the saved result and evidence.

BDD script alongside Actual Result and the result picker

The screenshot shows an older layout. Vansah records this BDD script as a whole-script execution log; it does not create a separate manual log for each Given, When, or Then line.

Example Actual Result

For a scenario that adds one product to a cart, a useful result is: Added Blue T-shirt with quantity 1. The cart showed quantity 1 and the expected total. No error appeared. If it fails, describe the observed difference and attach evidence that helps someone reproduce it.

Manual and automated BDD testing

Selecting Execute in this workflow opens a manual Test Run. Writing or saving Gherkin does not generate automation step definitions or automatically drive your application.

For automated BDD, your test framework needs step definitions and runs the scenario outside this manual workflow. Use the relevant Vansah automation integration to send its results. Keep automated and manual execution contexts clear when reviewing runs.

If the script changes during testing

Review the revision notice before loading changes. See Update a Test Run to the Latest Script Revision. Loading new instructions does not retest them.

Did this answer your question?