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

Requirements

Requirements set the base of testing and they cannot be omitted. How do they work in ATM?

PreviousEnvironmentsNextTest Cases

Last updated 3 days ago

Was this helpful?

Requirements provide a foundation of what software should do and allow testers create comprehensive test cases, that verify specific features. They are the start of testing process and a vital part of designing tests.

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

Requirements work item and list

In ATM, Requirements can be created with the native Create and later on linked with a selected Test Case.

Remember that in order for the work item to be recognized as a Requirement it needs to be a proper work type (the one defined in the Testing Setup).

Marketplace
app documentation