5 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" otpion on the top navigation.

 Test Case Library has two main parts: Test case list and filtering panel

1. Test Case list

The list of test cases shows the following information:

  • Name: Name of test cases
  • ID: ID of test cases
  • Status: Status of test cases
  • Assigned: Assignee of test cases
  • Hours: Effort users spent on test cases
  • Last Run 
  • Runs
  • Bugs
  • Last Edit: latest date and time test cases run
  • Tags: Tags of test cases

You can update test cases by clicking on the inline "Edit" button. The buttom 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. You will be confirmed on deletion action with a message "Are you sure you want to delete this test case?" and two buttons "Delete" and "Cancel". With "Delete" option, the test case will be deleted from system. With "Cancel" option, deletion action is canceled and the test case still exists.

2. 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 dipslay test cases matching with the selected criteria only. 

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: 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 wether 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.  
  • Linked Work Items: Other work items linked to this test case 
  • Attachments: images, text files or any other files used for the test case
  • History: date and time that any changes to the test case. This is read-only information.
  • Test Markdown: view of the test case in Markdown

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 different 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. 

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 by the following priority: 

For example, if any step is Blocked, the test case will 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

Test Cases Import

Imagine that you are using another system to manage your test cases. Now you change to use Pulse and you of course have a wonder whether Pulse supports to import your existing test cases or not. The answer is "Absolutely".

You need to access Test case library then click on "Import Test Cases" button to trigger Test Case Import pop up.  

There are just two buttons available on the pop up "Choose Files" and "Upload All". You should use "Choose Files" button to browse to the test cases file that you want to import. Currently, Pulse supports to import CSV files only. In near future, the external files that are accepted will extend to more types such as excel, xml and so on.

The imported CSV file must have a column header so that Pulse can depend on it to detect valid information to be imported. Here is the list of fields matching with Pulse test case system: Project, Name, Description, Steps, Expected results, Version, Type, Priority, Status, Effort, Tags, Is regression, Assinged in which Project and Name columns are required. Columns are seperated by comma. Column header names and their value are case-insensitive but their value type is validated by system as following:

  • Project: exact name of the project you are importing test cases to
  • Name: any text
  • Description: any text
  • Steps: any text. In case of many steps, they should be seperated by semicolon
  • Expected results: any text. If a test case has many steps, each step expected result should be seperated by semicolon. In case a step has no expected result, leave its expected result null
  • Version: any text
  • Type: should be one option between "automted" and "manual"
  • Priority: should be one option among "high", "medium" and "low"
  • Status: should be one option among "new",  "in_progress", "baselined" and "approved"
  • Effort: a number
  • Tags: any text
  • Is regression: should be one option between "true" and "false"
  • Assigned: valid email address
After specifying an imported file, you need to click on "Upload All" button. At this moment, system will validate the file structure (Project and Name must be required) and value (data type must follow rules above) before importing test cases. If any error is found in the file, an error messeage will show up to inform you. In case the file structure is passed the validation but some of rows contain invalid value, the valid rows will be imported and the invalid rows will be ignored.
Progress bar apears right after "Upload All" button is clicked to inform you the import progress.
Subscribe To Our Blog
Powered by Zendesk