Manage Test Cases

A test case is a complete technical specification which defines how the system should perform as specified in the requirements. You can generate test cases from work items . A work item is considered complete when all associated test cases pass.

In CA Agile Central, test cases can be:

  • Created from a work item which creates an automatic association between the test case and the work item (recommended).
  • Created as a stand-alone test case.
  • Edited to add information or update changes as your requirements evolve.

Your ability to manage a test case is dependent upon the user role and permissions you have been assigned for the workspace .

Note: If you want to import test cases that contain multiple test steps, we recommend that you use the CA Agile Central Add-in for Excel.

Test cases includes the following:

Create Test Cases

Create a test case from a work item ( user stories and defects only) to verify successful and acceptable implementation and functionality of the work item. When you create a test case from a work item, CA Agile Central creates an automatic association between the work item and the test case. View the association in the sidebar of either the work item or the test case. You can create a stand-alone test case, but there is no automatic association from the test case to any work item. CA Agile Central recommends creating test cases directly from the associated work item.

You can create a test case in CA Agile Central from several locations. This flexibility allows you to progress through work activities and create a test case whenever necessary.

Create a Test Case from the Test Cases Page

Follow these steps:
  1. Select Quality, Test Cases.
  2. From Actions, select New Test Case.
  3. On the Create Test Case editor, complete the fields as necessary.
  4. Select Create.

Create a Test Case from the Test Plan Page

Follow these steps:
  1. Select Quality, Test Plan .
  2. Select the New Test Case new test case icon on the row of the test plan for which you want to add a test case.
  3. On the Create Test Case editor, complete the fields as necessary.
  4. Select Save & Close.

Create a Test Case from the Work Item Detail Page

The Work Product field is automatically populated with the ID and Name of the work item from which you chose to generate the test case.

Follow these steps:
  1. Go to a work item detail page :
    • For user stories, select Plan, User Stories.
    • For defects, select Quality, Defects.
  2. From the work item summary page, select a hyperlinked work item name.
  3. On the detail page, select the Test Cases link on the ribbon.
  4. On the Test Cases summary page, select Actions, then select New Test Case.
  5. In the New Test Case editor, complete the fields as necessary.
  6. Select Create.

Add Steps to a Test Case

Add steps to a test case to specify what must be completed in a test case in order for it to be successful. For each input executed, there is an expected system state that results from the input. All combinations of user input and expected system result culminate in the final validation step which is the actual condition that is being tested.

Note: You can also add steps to a test case on the Work Item Detail page.
Follow these steps:
  1. Select Quality, Test Cases.
  2. On the Test Cases summary page, select any hyperlinked test case name.
  3. Select the Steps icon Steps icon image
  4. In the Steps editor, select + Step.
  5. Enter each step that must be executed to achieve the state of the system as detailed in the related requirement. You can use the rich-text fields for formatting.
    • Input: Enter the action step of the test. This is a required field.
    • Expected Result: List the expected system response to the action step.
  6. After all steps for the test case have been added, enter a validation step. This is the one step that evaluates the status of the execution of the test case and sets the local verdict of the test case.
    • Validation Input: Enter the action step of the test. This is the activity that will produce the Expected Result. This is a required field.
    • Validation Expected Result: List the response that must be obtained in order to verify the correct performance of the system. The Expected Result is the comparator that demonstrates that the system has accurately fulfilled the designed functionality.
  7. Select Save & Close.

Add Defects to Test Cases

You can create a new defect from a test case from the following locations from both the Test Cases page and the Iteration Status page.

Create a Defect from the Test Cases Page

Follow these steps:
  1. Select Quality, Test Cases.
  2. Select the FormattedID of the test case.
    1. Select the Defects link on the ribbon or sidebar.
    2. Select + Add New.

Create a Defect from the Iteration Status Page

Follow these steps:
  1. On a test case under a test set on the Iteration Status page.
    • On the grid view, select the gear menu on the test case.
    • Select Add Child, then select Defect as a the Child Type.

Edit a Test Case

When you edit a test case, you can modify information such as field values and textual descriptions, reorder test case steps, or add and remove steps.

Edit a test case from any of the following locations. Each location provides two access routes to editing a test case: the summary and detail pages.

Delete a Test Case

Follow these steps:
  1. Access the detail page of the test case you want to delete.
  2. From Actions, select Delete.

Use the My Test Cases App

The My Test Cases app is part of your personalized dashboard . Only those test cases that list you as the owner display. Use this app as your daily test case workplace.

Follow these steps:
  1. Select the My Home tab, then Dashboard.
  2. From the Gear menu, select Add App.
  3. Select My Test Cases and select Add.

My test cases image

For more information on the My Test Cases app, see the App Catalog.

Test Case Fields

The following fields are available to help you describe or add detail to a test case. You can set these field values when creating or editing a test case. Required fields are marked with a red * in the detail page, or highlighted in red on the full screen editor.

Field Description
ID A system-generated ID for the test case. The ID consists of a tag prefix and a numerical value. The tag can be customized by your system administrator to reflect a differentiating prefix for each work item defined in your project, such as US for user story, DE for defect, and so on.
Name Enter a name of the test case. This is a required field.
Color Optional color indicator for the test case.
Owner The owner of the test case.
Project The project that contains this test case. This is a required field.
Description A description of the test case.
Test Folder Add, remove, or change the test folder to which this test case is assigned. Each action creates an automatic revision entry. Note: This field is displayed only if your subscription includes Quality Manager.
Objective Detail the objective of the test case.
Work Product

Specify the work item that is associated to the test case, such as a user story or defect. If you generated the test case from a work item, this association is automatically created and the name of the work item from which the test case was generated displays.

To manually associate a work item, select the Choose choose icon and select a work item from the chooser window.

Type Specify the type of test that is being performed, such as regression, acceptance, and so on. This is a required field.
Method Select either Manual or Automated to indicate the method of testing used for the test case. This is a required field.
Priority Specify the importance of this test case. These values can be customized by your subscription administrator.
Steps Validation Input and Validation Expected Result represent the actual steps entered for the test case and each validation point. Validation Input is required.
Last Verdict The verdict from the most recent execution of the test case. The field is automatically updated each time the test case is executed. Last Verdict is not displayed during an edit of a test case, but only when viewing the test case detail.
Last Run The date of the test execution. Last Run is entered on the Test Case Result page and is displayed here as a read-only field.
Last Build The number of the last software build which was tested. Last Build is entered on the test case result page and is displayed here as a read-only field.
Custom Fields This section lists any custom fields that have been added to your workspace and their related values. This section only displays if your administrator has added custom fields.

Feedback

Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.