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

Was this helpful?

Export as PDF
  1. Testing in ATM

Test Executions

How to document test executions in ATM? Find out below.

PreviousTest PlansNextTest Case Executions

Last updated 3 days ago

Was this helpful?

Test executions are a step where theory is turned into practice. In these moments, the software goes through multiple trials and a variety of cases - and all of these efforts are focused on quality. So this step has to be well-documented in order to properly identify and fix the problematic areas.

Test Management and Templates go together! Creating templates for a work item like Test Executions can help testers maintain consistency across items and save their time. Check out our Issue Templates Agent on and for more details!

Test Execution item

Test Executions are another Jira work item in ATM. This characteristics allows to create this test element right from the native Create button, or with the shortcut in the board. While configuring the work item, the users need to remember to match the item type to the one chosen in a Testing Setup. The newly created Test Executions will be automatically added to the project selected in the Testing Setup.

The Create work item dialog will also display 3 custom fields - ATM Test Plans, ATM TE Status and ATM Environments - which cna be filled in by the users in order to make sure that the Test Execution contains all of the valuable details.

Test Execution view

In the Test Management panel, the users can find functionalities dedicated specifically to this testing step - the Test Case Executions (TCE) and Defects tabs. They provide a quick overview of crucial testing elements, helping tie the executing process together. These tabs will be described in detail in the corresponding pages of the documentation.

Creating a Test Case Execution

TCEs can be created by clicking the Add a Test Case Execution button in the TCE tab of Test Executions. The new window will allow to configure the object.

Defects

The Defects tab contains a list of defects related to a Test 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

Custom fields

For an improvement of the information flow, we have added 4 custom fields, which provide unique information for Test Executions and help users stay on top of the testing process.

  • ATM Test Cases

  • ATM Test Plans

  • ATM Test Execution (TE) Progress

  • ATM TE Status

Best Practices Tip

In order to quickly access the custom fields, we suggest pinning them to the top of the panel on the left side. This way, the users do not have to wander through the collected information and view what's necessary without losing focus.

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

Following are available in the Details Panel on the right side:

Defects page
custom fields
Marketplace
app documentation