Date:  

Using Zephyr Scale as a tool for test execution

This page includes information about:

How to navigate to your test cases

  1. Navigate to "Tests" in the toolbar.

       

       2. Click on the "Test Cycles" tab at the upper left corner of the screen (bellow the project name).

       

       3. Select the correct cycle, e.g.:

       

      4. In the column to the left you will see all test cases assigned to you.

     

Note: If no testcases are assigned to your user, you can see all testcases added to the cycle by untick "Show only assigned to me" in the upper left corner.

     

Layout and execution of tests

Layout

Zephyr Scale have a vertical layout:

Each step and expected result is organized into separate boxes.

Execution

Each step has a column to the right with different choices related to that particular step.

In this column you have the choice between the following options:

  • Marking a step as "passed".
  • Marking a step as "failed".
  • Marking a step as "blocked".
  • Contains an overview of all possible ways to mark a step, select relevant step.

     

  • Works as a shortcut making it possible to e.g. create issue if a test fails and you can at attach files:   

     

When executing a test case you can choose to mark each step individually. If all step are marked as "passed" the test case will automatically change to passed. This will be visually noticeable in the column to the left. A passed test is marked whit a green color to the left.  

You can also choose to mark the test case passed in the upper right corner :

However, note that in cases where a test case failed or is blocked it is best to mark the steps individually. This is because in that way it is possible to see in which step the problem lies!

What to do if a test fails

If a test fails it is the testers responsibility to create an issue. Click on the right-hand side in a test step on the following icon . Then select "Create issue".  

The "Create issue" dialog (template) opens.

Select "Issue type" Bug.

Some of the fields are automatically filled and some will have to be filled out manually.

The following information must be filled out manually:

  • Summary – Short description of the bug, this will be the name for the bug.
  • Description – It is important to add a good description. Fill in all relevant information and specify in which step the test failed. Include a picture of the test steps. If possible, also include logs and other screenshots that are relevant.
  • Attachment – Here you can add attachments like e.g. logs, and screen shots.

Click on the Create button to create the bug. The bug is created.

In the test case you get a link to the bug (see example below):

You can also see bug's in the project in the Issue menu below "Open issues"


Test Manager/Project Manager will follow up on bugs created during testing.



  • No labels