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. Architecture

Objects & Relations

ATM contains multiple objects. How are they related? Read below.

PreviousArchitectureNextCustom Fields

Last updated 8 days ago

Was this helpful?

Testing elements such as Requirements, Test Cases, Test Plans, Test Executions and Defects are work items. Test Case Execution, our only non-work item, is a custom object. Throughout the app we have also created multiple custom fields, which allow to maintain the information flow across multiple work items. These are discussed .

What is the relation between elements?

Testing Setup allows to create and define the management system. The users choose projects for test elements, define links and work types. Once created, they can go on to defining Requirements and later on, Test Cases - both of which are work items. Within the Test Case, they can link Requirements using Jira links, define Test Steps and add Test Cases to the Test Plans.

For executing tests, users create Test Execution item, which contains the Test Case Execution custom object. This object also links Defects, which are based on our database and is taken care of by us.

on the next page