Menu

Test Cases

Test Case Library is a place displaying all test cases available in the system. You can navigate this page via "Test Case Library" option on the top navigation.

If you are integrated with qTest Scenario - BDD for Jira, this will also be where you store your test scenarios.

Test Case List

You can update test cases by clicking on the inline "Edit" button. The bottom will bring you to test case modal so that you can change any to the test case.  The inline "Delete" buttons are used to delete test cases. 


Filtering Panel

Pulse supports to filter test cases with Filtering panel. This panel is hidden under filter icon by default. Clicking on the icon will enable the panel.

Filtering panel has some criteria as following

  • Project: displays projects available to the organization
  • Status: contains test case status: New, In_progress, Baselined and Approved
  • Assigned: shows of members of the organization
  • Tags: lists tags available to the organization
  • Work Item Status: shows work item status: Pending, Planning, Execute, Completed
  • Work Item content: is used to input a keyword matching with a part of work item name

Once any filtering option is set, the list of test cases is updated to display test cases matching the selected criteria only. 

Test_Case_Library_Filtering.gif

Creating Test Cases

There are two ways to create Test Cases within Pulse. A quick Test Case can be created in addition to Test Cases with more information. 

Quick Add Test Cases

A quick test case can be added from a work item by clicking on "Quick Add Test Case." The following fields are available: 

  • Name: a short description that describes the test case. 
  • Type: mark a test case as manual or automated
  • Note/Description: a place to leave a note about the test case
  • Steps and Expected result: test steps the tester should take and the expected results. The order of test steps can be changed and test steps can be removed.  
  • Tags: new tags can be added or existing tags can be selected to organize test cases

Create New Test Case

There are two ways to open Test Case modal such as using "Create New Test Case" button or "Edit" button on Work Item modal and in Test Case Library. 

Test case modal contains necessary fields a test case must have:

  • Project: the project the test case is assigned to
  • Version: version that the test case should be executed. Default value is empty
  • Status
    • New: the test case has just been created
    • In Progress: the test case is in process of designing
    • Approved: the test case is approved and ready for execution
  • Priority: Low, Medium, or High
  • Type: mark a test case as manual or automated
  • Assigned: Team member(s) assigned to the test case 
  • Tags: new tags can be added or existing tags can be selected to organize test cases
  • Effort: man hours members have spent on the test case. 
  • Flag for Regression: used to decide whether the test case is regressed in different versions or not. Default value is unchecked, i.e not regression
  • Description (Optional): to add a description of the test case, click on "Add a Description" 
  • Pre-condition (Optional): to add details on the environment needed for the test case or test data, click on "Add a Pre-Condition" 
  • Steps and Expected result: test steps the tester should take and the expected results. The order of test steps can be changed and test steps can be removed.  
  • History: date and time that any changes to the test case. This is read-only information.

Running Test Cases

Test cases for a work item can only be executed once an item is in the Execute phase. To run a test case, open the work item, select some or all test cases, and click the Run button. You can choose to run one test case at a time by clicking on the in-line Run button.

A status can be set for each Test Step or for the overall Test Case. The statuses available are:  

  • Passed: The system behaves as expected when the test is completed. 
  • Failed: The system behaves differently to than the expected when the test is completed. 
  • Incomplete: The test was not executed completely. This is also the default status. 
  • Blocked: The test cannot be completed because a defect or other impediment prevents the test from being completed. 

Execute_test_Cases.gif

The overall test case status is decided by the status of the test steps. If test steps have different statuses, the overall status will be set to the following priority.

For example, if any step is Blocked, the test case will be shown as Blocked. If no step is Blocked but another is set as Failed, the test case status is set to Failed and so on.

 
Subscribe To Our Blog
Powered by Zendesk