Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Use the following to navigate to the following sections:

You can also create new tests or import existing ones.

Viewing and Modifying Tests

A test can be viewed and modified just like any other issue in JIRA. If you know the issue key of the test, you can enter that in any search field or search through the Issue Navigator.

The view test screen shows the following:

  • Header: This displays the project to which this test belongs, the issue key of the test and its one-line Summary
  • Toolbar: This toolbar allows you to access often used functionality
    • Edit: This button takes you to the edit mode of a test where many of the fields can be edited. This is very similar to creating an issue. Please note that Test Details have to be edited from this View Issue screen.
    • Clone: 'Cloning' (copying) a test allows you to quickly create a duplicate of the test within the same project. The clone test is a replica of the original test, containing the same information stored in the original test— e.g. Summary, Labels, Components, Test Details, etc. except for Test Execution details.

      A clone issue is a separate entity from the original issue. Operations on the original issue have no effect on the clone issue and vice versa.

    • Link: Allows you to link another issue or a web link to this test, typically a requirement or a story or an epic.

    • Add to Test Cycle(s): Under the "More Actions" drop-down, this allows you to add this test to an existing Test Cycle. That then also shows in the Test Executions section below.

    • Attach Files: You can attach one or more files to a test (Note: Your JIRA Administrator must have enabled file attachments. You will also need "Create Attachments" permission in the appropriate projects).
    • Attach Screenshots: You can attach a screenshot to a test if your Administrator has configured JIRA and your permissions correctly.
    • Comment: Adding a comment to a test is a useful way to record additional details about a test, and collaborate with team members. Comments are shown in the Comments tab of the Activity section.
    • Execute: This button allows you to immediately execute this test, either in an ad hoc manner or as part of a Test Cycle.
  • Details: This section is almost exactly like the one for any other issue-type but note the following:
    • Fix Version/s: This field is the one that is used to organize tests i.e. make it belong to a Version.
    • Status: By default, the workflow statuses for tests are turned off. Modify workflow options to turn it on.
    • Resolution: Just like Status, these do not apply until workflow is turned on
  • Description: this section is exactly like the one for any other issue-type and can be useful for adding a high level description or pre-conditions for the test.
  • Test Details: This section allows you to enter detailed test steps, any accompanying test data and expected results. Test steps can be reordered, cloned or deleted.
  • Test Executions: This section shows the details of all scheduled and previous executions of this test. It also allows you to execute a test.
  • Attachments: This section is exactly like the one for any other issue-type
  • Issue Links: This section is exactly like the one for any other issue-type
  • Activity: This section has a Test Details History tab that shows all the changes made to the test with respect to its step, test data and expected results.

Customize Test Details Columns

Users can customize which columns appear in Test issues Test Details area.

These changes will persist for that user permanently until the user changes them again.

Users can freeze and unfreeze the Test Step ID and Test Steps column to make it easier to reference the test step when viewing additional columns to the right in the table.

Using Wiki Markup in Test Details 

Users can use the wiki markup language to edit your test steps. By clicking on the visual editor tool, users are able to bring up the wiki markup visual editor that allows them to edit and format the contents of their test steps details. The visual editor provides users with an easy way to utilize wiki markup formatting for the field.

Once you are done with any changes to the formatting of the test step field, you can click "Save" to add the wiki markup.

You can click on the preview icon to verify the changes that you've made using wiki markup and to make sure you've got it right. After you are done previewing, you can click on the "Add" button to add the test step.

Clicking on the preview icon when there is wiki markup will display the following:

Click on the help icon to get a list of available markup options if you need any additional help or context.

Test Step Reorder

Rearrange the order of steps by selecting and holding them on the far-left side handle and dragging them to the desired location. Release the click to drop them into their new location. This change is automatically saved.

Cloning Test Steps

To speed up the test creation process, test steps can be easily cloned. Click on the copy icon in action column for the test step.

Selecting the "Clone" option allows for that test step to be cloned and inserted into a number of positions - either above the current test step, below it, at some specific number in the list of steps or appended at the very end.

Deleting Test Steps

Just next to the Copy button, there is an option to delete a step. This deletion will remove the step completely and renumber the remaining steps. This cannot be undone.




  • No labels