Stop digging through CI logs. Read results in Jira.
Keep your frameworks and pipelines. AgileTest brings every result into Jira, next to your manual tests and requirements.
Works with the tools you already use
Plus any tool that exports JUnit XML, such as Playwright, Cypress and pytest.
Automation runs fine. The results are hard to use.
When results live in CI logs, only the people who read logs can act on them.
[INFO] Running CheckoutTest…
[WARN] Tests run: 128, Failures: 3, Skipped: 5
[ERROR] PaymentTest.cardDeclined:42
[ERROR] CheckoutTest.taxRounding:88
[ERROR] CartTest.maxQuantity:17
… 2,418 more lines
BUILD FAILURE
Results buried in CI logs
Manual and automated tests live apart
No link to requirements
Rewriting tests isn't an option
Your automation runs where it runs. The quality record lives in Jira.
AgileTest doesn’t run your tests. It collects and reports on their results.
Import result files
Push results by API
Connect your CI/CD pipeline
Run pipelines from Jira
Add release context
Trace to requirements
From pipeline to Jira in four steps
Run your tests
In the framework and pipeline you already use.
Any frameworkProduce a report
A supported XML or JSON result file.
XML · JSONSend it to AgileTest
Upload in Jira, call the API, or add a pipeline step.
Upload · API · CIReview in Jira
Next to manual runs, linked to requirements and defects.
Executions · ReportsResults that arrive ready to use
No mapping spreadsheets and no manual clean-up after every build.
<testcase name="applyValidCoupon" time="1.2"/>
<testcase name="taxRounding">
<failure>expected 4.50</failure>
</testcase>
</testsuite>
Test cases created for you
Built from the test names in your report.
No duplicates on re-runs
Re-imports skip existing test cases.
Statuses mapped automatically
The most severe status wins.
Evidence comes with it
Screenshots in the report are attached.
BDD results update existing tests
Cucumber and Behave match by issue key.
Clear upload feedback
See each import's status and any error.
Frequently asked questions
No. Your frameworks and pipelines run the tests. AgileTest collects and manages the results in Jira, and can start a configured pipeline from a Test Execution.
Yes. Authenticate with a Client ID and Client Secret on Cloud, or a Jira personal access token on Data Center, then post the report to the endpoint for its format.
When you import into an existing execution, test cases that already exist are skipped and only new ones are added.
Yes. Importing results works the same way, and all CI/CD integrations are supported except Bitbucket Pipelines.
JUnit, NUnit, TestNG, xUnit and Robot Framework (XML), plus Cucumber and Behave (JSON). Tools that export JUnit XML, such as Playwright, Cypress and pytest, work too.
Yes. Imported results appear in Test Executions alongside manual runs, and automated tests can be linked to requirements for coverage and traceability reports.
Yes. Include the Jira issue key in the report. These results attach to existing tests rather than creating new ones.
More ways to manage quality in Jira
Bring your CI results into Jira
Start with the reports you already produce, or clone our sample repo to see the full flow end to end.