APPsolute Test Isolation – Ticket-Level Test Visibility for Jira

⚠️ Prerequisite: Xray for Jira Cloud is required
APPsolute Test Isolation is a companion app that enhances Xray — it is not a standalone test management tool. You must have an active Xray for Jira Cloud subscription and Xray API credentials (Client ID + Client Secret) to use this app. The app reads Xray execution data and applies isolation logic; it does not replace Xray's test creation, mapping, or execution features.

Overview

APPsolute Test Isolation enhances Xray for Jira Cloud by providing ticket-specific test status directly within Jira issues. The app creates an Issue Panel that evaluates only the test executions associated with the current ticket — avoiding reliance on Xray's aggregated coverage model where shared tests can produce misleading results.

Key Features

Ticket-Scoped Status: Shows test status specific to the current ticket, not aggregated across requirements
Automatic Sub-Execution Detection: Subtask Sub-Test Executions are automatically included — no manual linking required
Conservative Status Calculation: Incomplete tests (To Do) take priority — won't show "Passed" or "Failed" until all tests have reached a final state
Five-Count Summary: Always displays Passed, Failed, In Progress, To Do, and Total counts
Evidence Tracking: Displays evidence file counts from Xray test runs
Jira Field Write-back: Optionally persists status to a custom field for JQL queries, dashboards, and automation
Writeback Resilience: Retry logic with exponential backoff, skip-if-unchanged optimization, configurable user permission checks, and ticket comments on failure
Admin Writeback Log: Audit log of writeback failures and permission checks (last 50 entries)
Admin Configuration: Full control over API credentials, enabled projects, write-back settings, permission model, and debug logging

Use Cases

JSM Ticket Validation: Verify that Change, Incident, or Service Request tickets have been properly tested before closure
Operational Testing: Track test status for infrastructure, deployment, or configuration validation workflows
Reused Test Scenarios: Get accurate per-ticket results when the same tests are shared across multiple requirements
Audit & Compliance: Provide ticket-level evidence of test validation with execution traceability

Xray Coverage vs. Isolated Test Status

Xray's native Test Coverage aggregates results across all tickets that share the same tests, which can produce a shared (and sometimes misleading) status. APPsolute Test Isolation scopes the status to the current ticket's executions only, eliminating ambiguity caused by reused tests and giving you a reliable, ticket-specific view.

How It Works

Tests are created and managed in Xray (the app does not replace Xray)
Tests are executed via Sub-Test Executions (subtasks) or linked Test Executions
The APPsolute Test Isolation panel reads the execution data from Xray via its API
The app computes an isolated, ticket-specific status using conservative rules
Status is displayed in the panel and optionally written to a Jira custom field

Relationship to Xray

APPsolute Test Isolation does not replace Xray and does not manage test execution or coverage.

Xray remains responsible for:

Test creation and management
Test mapping (coverage)
Test execution and evidence

APPsolute Test Isolation:

Reads Xray execution data via the Xray Cloud GraphQL API
Applies isolation and status logic scoped to the current ticket
Displays a focused, ticket-specific test status
Optionally writes the computed status to a Jira custom field

Getting Started

Before installing APPsolute Test Isolation:

✅ Ensure Xray for Jira Cloud is installed and configured on your Jira site
✅ Create an Xray API Key (Xray Settings → API Keys) with an App name
✅ Have the Client ID and Client Secret ready for the app configuration

After installation, see How to Configure Test Isolation for the step-by-step setup guide.

APPsolute Test Isolation Home