INTEGRATION • CIRCLECI

CircleCI test management, in Jira

CircleCI runs your tests. AgileTest puts the results in Jira, next to your requirements, manual tests and bugs.

Try it freeBook a demo
4.6/5 on Atlassian MarketplaceFree for up to 10 users
Test ExecutionsSHOP-131×
91%Test Case passed
Total 128Pass 117Fail 3To do 4
AssigneeEmma Clark
Fix versions4.2
Test EnvironmentsStaging
MilestoneRelease 4.2
Started onNov 04, 09:10
Finished onNov 04, 09:14
«‹Test 13 of 128›»
☰ Test list
SHOP-226Fail Export PDF
PaymentTest.card3dsChallenge
Test CoveragesTests1
Preconditions0
CircleCI pipeline #482128 results imported to SHOP-131
Works withJUnitNUNUnitTeTestNGxUxUnitRobot FrameworkCucumberBeBehave
AUTOMATIC IMPORT

CircleCI results, where QA signs off

Stop sharing job links in chat. Every run’s results are in Jira, ready for review and sign-off.

Create or updateA new Test Execution per run, or add to an existing one.
No duplicatesMatching tests are reused on every run.
Statuses mappedPass, Fail, Skipped and more, read from the report.
Screenshots attachedEvidence from the report lands on the test run.
shop-web / main / build-test-and-upload-report / build-and-test
build-and-testSuccessDuration 4m 11s
Spin up environment6s
Preparing environment variables0s
Checkout code2s
Build and Test with Maven3m 47s
Setup a remote Docker engine9s
Upload test report7s
Classic Test / Automated Tests
Test ExecutionSourceFrameworkStatusCreated at
SHOP-131ImportJUnitSuccess1 minute ago
SHOP-129ImportJUnitSuccess3 hours ago
SHOP-127ImportJUnitSuccessYesterday
Test Executions
Classic Test / Test Executions
Key or summaryAssigneeStatusMoreBasicJQL+ Test Execution
KeySummaryNumber of testsExecute statusAction
SHOP-131Execution results - 177243174128212894% PassRun
SHOP-130Regression · Sprint 244072% PassRun
SHOP-128Execution results - 177234521880412892% PassRun
SHOP-125Smoke tests · Staging12100% PassRun
SHOP-121Test Execution for Test Plan SHOP-1202040% PassRun
SHOP-118Execution results - 177225880311712697% PassRun
SHOP-114Checkout · Manual round 21861% PassRun
SHOP-110Execution results - 17721723915601240% PassRun
‹123›Rows per page 10
CircleCI pipeline #482128 results imported to SHOP-131
RUN HISTORY

Every run, on the record

Compare this week’s pass rate with last week’s without digging through old CircleCI jobs.

  1. 1
    CircleCI runs your testsYour workflow builds and tests as usual.
  2. 2
    One step sends the reportThe upload step adds the results to AgileTest.
  3. 3
    Each run is keptEvery run is a Test Execution with its own pass rate, ready to compare.
TRACEABILITY

Coverage that includes your CircleCI tests

Requirements show automated and manual results side by side, so gaps are easy to spot before release.

Linked to requirementsLink each automated test case to the requirement it checks.
Latest statusOK or NOK on each requirement after every run.
Defects from failuresLog a bug from a failed run, linked back to it.
Reports in JiraTest Coverage and Traceability reports.
ReportsTest Coverage
ShareUpdateExport
Fix version: 4.2Environment: Staging
OKNOKNOT RUNUNKNOWN
SHOP-87Guest checkout78%
SHOP-88Card payments64%18%
SHOP-91Saved addresses100%
SHOP-95Order emails50%50%
SHOP-97Coupons70%20%
SHOP-99Account recovery40%40%20%
Project Settings / shop-web
Environment VariablesAdd Environment Variable
NameValueCreated
BASE_AUTH_URLxxxx.comNov 04, 2026
BASE_URLxxxx.appNov 04, 2026
CLIENT_IDxxxx9f2cNov 04, 2026
CLIENT_SECRETxxxxa81eNov 04, 2026
PROJECT_KEYxxxxSHOPNov 04, 2026
.circleci/config.yml
- run:
    name: Upload test report
    command: |
      export token=$(curl "${BASE_AUTH_URL}/api/apikeys/authenticate" \
        -X POST -H 'Content-Type:application/json' \
        --data '{"clientId":"'"$CLIENT_ID"'","clientSecret":"'"$CLIENT_SECRET"'"}' | tr -d '"')
      curl "${BASE_URL}/ds/test-executions/junit?projectKey=${PROJECT_KEY}" \
        -X POST -H "Content-Type:application/xml" -H "Authorization:JWT $token" \
        --data-binary "@target/surefire-reports/TEST-calculateTest.xml"
SETUP

One more step in .circleci/config.yml

Your build step stays the same. Add the upload step and you’re done, on Jira Cloud or Data Center.

API or CLIA curl call, or the CLI image via setup_remote_docker.
Cloud and Data CenterClient ID and Secret, or a Jira personal access token.
Project variablesCredentials stay in CircleCI environment variables.
Any repositoryGitHub, GitLab or Bitbucket code, the upload works the same.
HOW IT WORKS

Set up with the official guides

FAQ

Questions, answered

Does AgileTest run my automated tests?

No. CircleCI keeps building and running your tests. AgileTest imports the results into Jira after each run.

Should I use the AgileTest CLI or the REST API?

Either works. The REST API is two curl calls in a run step. The CLI runs the ghcr.io/agiletestapp/agiletest-cli Docker image; the docs example adds setup_remote_docker for it.

Which report formats are supported?

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.

Do I need to change my build?

No. Keep your existing build and test step, and add one step that uploads the report.

Does it matter where my code is hosted?

No. CircleCI builds code from your connected GitHub, GitLab or Bitbucket repository, and the upload step works the same either way.

Does it work on Jira Cloud and Data Center?

Yes. Cloud uses an AgileTest Client ID and Client Secret. Data Center uses a Jira personal access token.

Bring your CircleCI test results into Jira

Try it freeRead the docs

Questions? Contact us · Visit the 24/7 Support Desk

ALSO WORKS WITH