Versions Compared

Version Old Version 5 New Version 6
Changes made by

Angelica Salazar

Angelica Salazar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: T4J 2.1: TFJ-1334

Overview

The major tasks for executing test plans or single test cases in T4J are explained in the sections below. To execute tests in T4J, the first step is to navigate to the execution view, as follows:

  • Select the project to open, using one of the following ways:

    • Select Tests in the main navigation bar and select a project from Current Project or Recent Projects.

    • Select Tests > View all projects from the main navigation bar and select a project from the list.

    • You should now see the definition view, which is the default view of a project.

  • Select the Execution entry in the main T4J menu. You should now see the Execution View, which has two sections:

    • a list of test plans

    • a list of single test cases that have already been executed

Table of Contents
minLevel1
maxLevel7

Test Execution Tasks

Task

Action

Create a new test plan execution

  • Locate the test plan in the Test Plan Executions section.

  • Select Add Execution next to the name of the test plan.

  • Provide the name for the execution. You can optionally specify a description, an assignee, a project, components and fix versions.

  • Select Create to create the execution, which can be run in the Test Runner at a later time.

Info

To run the plan immediately select Execute instead of Create.

Create and run a new single test case execution

If the test case has not already been executed:

  • Switch to the Definition View and locate the test case in the project’s definition tree.

  • In the issue’s context menu, select Test Execution.

  • Provide the name for the execution. You can optionally specify a description, an assignee, a project, components and fix versions.

  • Select Execute to open the Test Runner.

If the test case has already been executed:

  • Locate the test case in the Single Test Executions section.

  • Select Add Execution next to the issue.

  • Provide the name for the execution. You can optionally specify a description, an assignee, a project, components and fix versions.

  • Select Execute to open the Test Runner.

Start or continue an existing test plan execution

  • Locate the test plan in the Test Plan Executions section.

  • Locate the test plan execution that was previously created.

  • Select the Continue test execution icon to open the Test Runner.

Start or continue a single test case execution

  • Locate the test case in the Single Test Executions section.

  • Locate the test case execution that was previously created.

  • Select the Continue test execution icon to open the Test Runner.

Edit a test execution

  • Locate the test plan in the Test Plan Executions section or the test case in the Single Test Executions section.

  • Select the desired test execution.

  • Select the Edit icon of the entry.

  • Update the entry and select Update to save the changes.

Note that you can only edit the metadata of an execution. Once a test case or test step is marked as failed or successful it cannot be changed afterwards.  

Delete a test execution

  • Locate the test plan in the Test Plan Executions section or the test case in the Single Test Executions section.

  • Select the desired test execution.

  • Select the Delete icon of the entry.

  • Confirm deletion.

Display execution statistics

  • Locate the test plan in the Test Plan Executions section or the test case in the Single Test Executions section.

  • Select the desired test execution.

  • Select the Show execution statistics icon of the entry.

An execution needn’t be finished to display it's statistics.

Filter executions

  • Select Filter in the main T4J menu items.

  • Set the criteria to be used - see Test Execution - Reference.

  • Select Filter to restrict the executions to those matching the given criteria.

Export executions

Test Runner Tasks

Task

Action

Review test cases

  • Use the icons located in the top right corner of the dialog to navigate through the test cases to be executed.

Although you can review the test cases in any order, they must be executed in the given sequence. 

Set the status of a test case step

  • Use the buttons next to a test step to set its status:

    • Step passed: The test step was executed successfully, and the next test step can be executed.

    • Step skipped: The test step was skipped, and the next step can be executed. This option can only be enabled in test plan execution.

    • Step failed: The execution of the test step failed. The test step and the test case are marked as failed. The execution is stopped and marked as failed. Any remaining test steps in this test case and other test cases are marked as skipped.

  • If the status is failed, a required text field appears for the test step result. You may optionally add a message if the status is passed by selecting the Add result message icon.

Info

Normally, once a test step has failed you forget about the rest of the test execution, but in case you want to run more test steps in the current test case or continue to other test cases, you have the following extra failure options available in the dropdown menu (…):

  • Step failed (continue with next test): The execution of any remaining test cases continues, even though the test as a whole failed.

  • Step failed (continue with next test step): The execution of any remaining test steps in the test case, as well as the execution of remaining test cases continues, even though the test as whole failed.

Set the status of a test case

  • Use the buttons in the bottom left corner of the dialog to set the status of the complete test case:

    • Test case passed: The test case was executed successfully, and the next test case can be executed. Any remaining test steps are also marked as passed.

    • Test case skipped: The test case was skipped, and the next test case can be executed. Any remaining test steps are also marked as skipped.

    • Test case failed: The execution of the test case failed. The test case is marked as failed. The execution is stopped and marked as failed. Any remaining test steps in this test case and other test cases are marked as skipped.

  • If the status is failed, you must provide a comment in the Test Result field. You may optionally add a comment if the status is passed

Info

Normally, once a test case has failed you forget about the rest of the test execution, but in case you want to run more test cases, you have the following extra failure option available in the dropdown menu (…):

  • Test case failed (continue with next test): The execution of any remaining test cases continues, even though the test as a whole failed.

Interrupt an execution

  • Select Close to interrupt the current execution and close the dialog. The state of the execution is saved, and the execution can be resumed later.

Add an attachment to a test case

  • Use one of the following options in the attachments area at the bottom of the dialog:

    • Select the Attachments link to open a file explorer.

    • Drag and drop attachments into the target area.

    • Paste images into the target area.

Create Jira issue

  • Select Create Issue to create a Jira issue linked to the test case.

  • Choose a link type.

  • Select Create Issue to create the issue.

Tip

This is a very convenient way to create a linked bug when a test case fails.

Show execution statistics

  • After completion of a test execution, select Show Execution Statistics.

Info

An execution is considered to be completed if either all test cases and test steps are marked as passed or a single test case or test step is marked as failed.