Why is Traceability important?

What is Traceability & How to use AIO Tests’ Traceability Reports

  1. Ensures the original requirements/goals have been covered by tests
  2. Acts as a plan for QA to understand the scope of testing
  3. Ability to show scope change impact on entire process
  4. Understand testing progress

As a manager, how will I know if all my requirements in upcoming release are covered for testing?

Input Screen — Traceability Summary

As a manager, how will I know if all my requirements in upcoming release are covered, executed and if bugs have been found against them?

Traceability Summary — Output
Traceability Detail — Input screen
  1. Requirement — showing specified Jira requirements in a hierarchy
  2. Cases — cases linked to these requirements
  3. Test Execution Results — execution details (status, cycle, date of execution & who executed the case)
    * Include Only Last Run checked: for each case, only the latest run status is shown
    *Include Only Last Run not checked: for each case, status of all runs in each cycle will be shown
  4. Defects — details of linked defects

Without Traceability you can never be sure of the quality of your product.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store