Manual test execution

Applies to CucumberStudio Cloud, and to Enterprise ver. 3.3 - 3.5.6.0. Last updated on November 17, 2023

The scenarios written within CucumberStudio can be manually executed.

Once your test run is created (see the instructions to create one), you can start a test execution cycle.

Test Execution Cycles

You can start or resume a cycle from the current test run page, on the top-right corner:

Starting and Resuming of Tests

Click the image to enlarge it.

If you do so, the cycle will automatically start from this test.

You can pause your test execution cycle at any time from the execution window:

Pausing of Tests

Click the image to enlarge it.

You can end the test execution cycle on the Test execution summary page when the tests have been executed:

Test Execution Done

Click the image to enlarge it.

Note: If some tests haven’t been run (their status is set to ‘not run’), the last screen will let you inform about them

You can get some metrics about the executions through the life of your test run from its page:

Viewing Test Metrics

Click the image to enlarge it.

Execute a Test

The test execution itself is pretty simple.

From this window, you can:

  1. Navigate to the previous or next test within your execution cycle.

  2. Set a global status for the test, and attach a comment and/or files.

  3. Set a global status for the test and go to the next one.

  4. Set statuses step by step.

  5. Pause the current execution cycle.

The Test Execution

Click the image to enlarge it.

Highlight search results