Quick start

Applies to CucumberStudio Cloud, and to Enterprise ver. 3.3 - 3.5.1.1. Last updated on April 16, 2021

Sample projects

We recommend you to look at the project samples first. They will help you learn the basic concepts of CucumberStudio quickly: scenarios, action words, test runs, and so on. You can create them any time, and you can delete them later at any time.

Project Samples

Click the image to enlarge it.

After you got the idea, you are ready to create your first project.

1. Create a project

  1. Select + > New project from the menu on the left.

  2. In the subsequent dialog, specify the project name and select the project type:

    • BDD with Cucumber — This one is for the teams that are already using BDD and Cucumber in their QA cycles.

    • Test Management — This is for those who’ve started introducing BDD practices into their workflows. If you are a novice user, we recommend you to select this type. Click Create for that option.

    Create a new project

    Click the image to enlarge it.

You will see the project’s Dashboard:

The Project Dashboard

Click the image to enlarge it.

You may add a description to your project to help your teammates understand its purpose.

2. Create a scenario

Now, we can create a test scenario:

  1. Click Features on the left and then click Create in the Scenarios section.

  2. In the subsequent dialog box, enter the scenario name (Login in our case) and click Create:

    Creating a scenario

    Click the image to enlarge it.

  3. Click the scenario name. This will open the scenario editor:

    Scenario editor

    Click the image to enlarge it.

    Here, for example, you can enter an optional description for the scenario to help your teammates better understand the scenario purpose.

  4. We can add scenario steps now. In the scenario editor, enter the following text into the edit box at the bottom of the Test Steps section —

    Given user logs in with John as username and Newcorp as password

    — and then click Create action word:

    Adding the first step

    Click the image to enlarge it.

  5. Add another step —

    Then user should be logged in

    — and click Create action word again:

    Adding the seconds step

    Click the image to enlarge it.

Here is how your first scenario looks like:

The created scenario

Click the image to enlarge it.

Great! Let’s now run it.

3. Run scenario

  1. Go to Test runs and click Add new at the top right.

  2. In the subsequent screen, specify the test run’s name (for example, Test Sprint 1) and select the scenarios for the run:

    Creating a test run

    Click the image to enlarge it.

    In our case, we can select Include all test cases to run all existing scenarios (we have only one so far). Later, when you have multiple scenarios, you can click Select a subset of tests and choose only those scenarios that you’d like to run.

  3. After the test run is created, you will see it on the Test Runs screen. Click your test run there:

    Creating a test run

    Click the image to enlarge it.

    This will open the test run’s page.

  4. On the test run’s page, click Resume test to start the manual execution:

    Run the scenario

    Click the image to enlarge it.

  5. Manual execution implies that the QA engineers reads the test instructions on screen, performs them and then log results by changing the status of individual steps or the entire test scenario:

    Manual execution

    Click the image to enlarge it.

    To change the status of a step, simply click the status label. The statuses will switch in a loop: passed, failed, undefined, then passed again, and so on.

    Once you set the status for all the steps, CucumberStudio will automatically set the status for the entire test. Alternatively, you can set the status for the entire scenario using its status label (see the image above). In this case you have a broader range of statuses.

    Let’s change the step statuses. Click their status labels and mark both steps passed. Then click the arrow button on the right to continue:

    Setting step statuses

    Click the image to enlarge it.

  6. We’ve executed all the scenarios in our test run, so we can finish the execution cycle now:

    Finishing execution cycle

    Click the image to enlarge it.

  7. After the test execution is over, you can view summary test results:

    Summary test results

    Click the image to enlarge it.

    Click a scenario name to view results of that scenario:

    Scenario test results

    Click the image to enlarge it.

What’s next?

Below are links to some topics that will help you get most of the product and improve your BDD tests:

See Also

CucumberStudio Documentation
Project lifecycle

Highlight search results