Issue Management Integrations

Overview

A failed test is only useful if someone fixes the data behind it. Issue management integrations hand that work to the tool your team already uses to track it: a failing test opens an issue, later failures comment on it, and a passing test resolves it. Each issue links back to the test and the failing run and carries the query that failed.

How every integration works

Each integration is a data source template for the issue tool, and they all work the same way, so a team that moves tools keeps its setup.

• Test actions open, comment on and resolve issues. A test gets a Test Ran action that calls the template's sync macro after every run; for Jira, Sync Jira Issue with Test Result (Automatic), which reads the run from Validatar and needs no settings. Test actions run after the test finishes.
• One open issue per test. The tool is the record of each issue's state. Validatar finds a test's issue by labels or tags on the issue, then confirms it by reading the issue directly. A closed issue is never reopened; a later failure opens a new one.
• A sweep repairs what actions miss. A failed action step does not fail its test, so a missed issue would otherwise go unnoticed. A reconciliation test, placed last in each scheduled job, opens missed issues, resolves issues whose test passes, closes duplicates and writes open issues onto the tables and columns each test covers.
• Shared fields. The Issue Tracking custom fields route a test's issues and show its open issue, and show open issues on catalog tables and columns. The same fields serve every tool.
• Dry Run first. New data sources decide and write nothing until you turn Dry Run off.
• Health checks. Each tool has a test pack that checks its configuration, whether the tool and Validatar agree, and the hygiene of the issues Validatar raised.

What each integration ships

Related

• What are Test Actions
• Using Template Fields in Test Actions
• Open and Resolve Jira Issues from Test Results