Testery Docs
TesteryFeaturesPricingRelease Notes
  • Testery Documentation
  • Release Notes
  • Get Started
    • Getting Started Guide
      • Create a Testery Account
      • Configure Your Project
      • Run Your Tests
      • Configure Slack Alerts
      • Schedule Your Test Runs
      • Invite Your Team
      • Get More From Testery
  • Get to Know Testery
    • Dashboard
    • Test Runs
      • Test Selection Rules
    • Projects
    • Test Triggers
    • Environments
    • Alerts
    • Settings
    • Test Plans
    • Test Stacks
      • Python
      • Node.js 16 End of Life
      • Default Chrome Version Change
      • Python 3.8 End of Life
    • Deployments
    • System Variables
    • Tags
    • Screenshots
    • Uploading Test Artifacts to Testery
    • Setting Test Execution Priority
    • Setting the Number of Parallel Tests
  • Integrate with Testery
    • Built-In Integrations with Testery
      • Jira
      • Slack
    • CI/CD Integration Guides
      • Azure Devops Pipelines
      • Set Up CircleCI to Run Testery Tests
      • Jenkins
      • GitHub Actions
      • Octopus Deploy
      • TugboatQA
    • Testery CLI
    • Testery REST API
      • Testery REST API Resources
    • Microsoft Teams
  • Framework-specific Guidance
    • Supported Testing Frameworks
    • Cypress
      • Updating Cypress Tests to Output in JUnit XML Format
    • Playwright
      • Update Playwright Tests to Output in JUnit XML Format for Import Into Testery
    • PyTest
      • Update Pytest to Generate JUnit XML for Import into Testery
    • TestNG
      • Updating TestNG Tests to Output in JUnit XML Format
  • How-To
    • Enable or Disable Automatic Rerunning of Tests
    • Run Cypress Tests without Connecting Repository
    • How to Store Sensitive Data Like Username and Password For a Cypress Test
    • Connect to a Private npm Repository
    • Running Scripts Before the Tests
    • Upload Test Run for Analysis
  • MISC
    • Troubleshooting Steps
  • Fixing Tests
    • Fix Common Selenium Exceptions
      • Fix a ChromeDriver Version Exception
      • Fix a NoSuchElement Exception
      • Fix a TimeoutException
      • Fix an ElementNotVisibleException
      • Fix a StaleElementReferenceException
      • Fix a WebDriverException
      • Fix an InvalidArgumentException
      • Fix a NoSuchWindowException
      • Fix an UnhandledAlertException
      • Fix an InvalidSelectorException
Powered by GitBook
On this page
  • Upload Test Run (UI Option)
  • Upload a Test Run (CLI Option)

Was this helpful?

  1. How-To

Upload Test Run for Analysis

PreviousRunning Scripts Before the TestsNextTroubleshooting Steps

Last updated 1 year ago

Was this helpful?

If you'd like to upload a test run for reporting purposes, to generate an AI-driven analysis, or to kick off alerts. You can do so either from the UI or from the CLI.

You will want to have a copy of your test run output in JUnit XML format. To generate this for your framework, see our various Framework Specific Guidance.

Upload Test Run (UI Option)

  1. Navigate to .

  2. Click Upload Test Run.

  3. Select your Project and Environment and then click Choose File to upload your JUnit XML.

Upload a Test Run (CLI Option)

Ensure you have the Testery CLI installed:

pip install testery

Once installed, you can use the following command to upload your test results to Testery:

testery upload-test-run\
  --environment-key develop \
  --project-key Your_Project_Name \
  --path target/surefire-reports/junitreports/junit.xml

Replace Your_Project_Name with your specific project name and adjust the --pathoption to point to the location of your JUnit XML file generated by TestNG.

If your junit.xml file is large, you should consider compressing it using .gz format

Updating TestNG Tests to Output in JUnit XML Format
Updating Cypress Tests to Output in JUnit XML Format
https://testery.app/testery/test-runs