LogoLogo
👉 Get a free ITSM ebook
Appsvio Test Management
Appsvio Test Management
  • Get Started
  • About ATM
    • Organizing Tests
  • Architecture
    • Objects & Relations
    • Custom Fields
  • Pricing Model
  • SETTING-UP PROCESS
    • Testing Hub
    • Testing Setup
    • Permissions
    • Environments
  • Testing in ATM
    • Requirements
    • Test Cases
      • Test Steps
        • Versioning
    • Test Plans
    • Test Executions
      • Test Case Executions
    • Defects
  • Reporting
    • Traceability
    • Test Coverage
  • Search in JQL
  • Integrations
    • Jira Automations
  • Resources
    • Roadmap
    • Release Notes
  • Contact our Support
Powered by GitBook

Security

  • Privacy Policy
  • Appsvio Trust Center

appsvio.com © 2025 All rights reserved

On this page
  • Test Case Execution tab
  • Test Case Execution view

Was this helpful?

Export as PDF
  1. Testing in ATM
  2. Test Executions

Test Case Executions

Test Case Executions allow testers to document their executions in details. Learn more about this object below.

PreviousTest ExecutionsNextDefects

Last updated 3 days ago

Was this helpful?

Test Case Executions (TCEs) are custom created objects. To be more specific, they are snapshots in time of each Test Case and allow testers to gather, document valuable results regarding each Test Case.

As TCEs are a snapshot of Test Cases, the later changes made in the Test Case won't be reflected in an already existing TCE. In order to include the updates of the Test Case, the user needs to create a new TCE.

Test Case Execution tab

TCEs can be accessed in each Test execution work item, in a corresponding tab, where they are listed in a table. The table contains following details regarding TCEs:

  • Work key of Test case (TC)

  • Individual TCE key

  • TC Version

  • Iteration

  • Number of defects

  • TCE Status

  • Date of the last update

  • Assignee

The last column is reserved for the Action buttons.

Iterations of Test Case Executions

New iteration of the same Test Case Execution object can be added by clicking the More actions button (three dots), available in every listed TCE object. New iteration enables creating another TCE and is a direct copy of the previous one.

Test Case Execution view

Clicking the play button in the last column in a TCE tab allows users to open a new window, where all of the TCE details are available.

The progress bar shows an overview of TCE statuses for each Test Step. The bar will be colored according to the color scheme of statuses. Additionally, the number of steps in each status are listed above the bar. The status of TCE can be changed in the top right corner.

The statuses available:

  • Not executed

  • In progress

  • Pass - final status

  • Fail - final status

  • Blocked

Below the progress bar, the users can find information such as Assignee, Test Case (TC) version, ATM Test Type and ATM Environment. ATM Environment custom field is copied from the same field within the Test Execution work item. From the TCE view, the users can also update the Assignee field for a selected TCE.

The rest of dialog window is divided into tabs, which gather valuable to the execution details - Test Steps, TCE Details.

Test Steps

Each of the Test Steps are listed in the same manner as in the Test Case. The user can change the status of each step individually by clicking the bar on the right and selecting an appropriate status. After the change, the color of the step title will change according to the color of the status.

The status of Test Steps can also be changed in bulk by clicking Change all the steps status and selecting one of the options.

Each test step can be completed with information of Actual results - this option is available at the bottom of each step. In order to edit it, the user has to just click on it. The text can be formatted to user's likings. Once done, click on the Save button to maintain the changes.

Actual results is the only editable field in Test Case Execution dialog window.

The user can link or add new defects to each individual step by clicking on the +Defects button at the bottom of the step. In the respectable options, the user will either search and link defects of choice, or configure new ones in a newly opened window.

In order to swiftly navigate between multiple TCEs without closing the dialog window, the users can switch between TCEs with page arrows in the top right corner of the window.

TCE Details

This tab collects additional information - Date of creation and latest update, Description and Requirements, which are linked to the Test Case. This tab is also a snapshot in time of a Test Case.

Defects

The Defects tab contains a list of defects related to a specific Test Case Execution. Following information is collected in a table:

  • Defect key

  • Summary

  • Relation

    • This column shows whether the defect relates in general to the selected TCE or has roots in a specific step of TCE

  • Priority

  • Status

  • Date of creation

  • Assignee

Defects can also be added, linked with buttons right above the listed test steps - the details are provided on the .

Within this tab, the users can also add new or link already existing Defects. More details can be found on .

Defects page
the Defects page