Skip to main content

Quickstart

Testiny integrates with test automation tools and frameworks to collect and manage automated test results in one place. Whether tests are run via a CI/CD pipeline or manually, Testiny helps debug, troubleshoot, and analyze failures efficiently. Learn how to submit your first automated test run to Testiny and set up reporting with your automation framework and CI/CD pipeline.

Submit your first automation results

  1. Download or install the Testiny CLI and create an API key in Testiny.

  2. Run your automated tests & generate a report. Testiny CLI supports JUnit-style XML files, Playwright JSON report, Cypress JSON reports and more. See the CLI reference for all supported report formats.

  3. Import your automated results to Testiny. Specify the Testiny API key, project ID or key, a source name, the report type and the report file(s):

export TESTINY_API_KEY=****
npx @testiny/cli automation --project ID_OR_KEY --source "unit-tests" --junit report.xml
See command output
API key: user '[email protected]' in organization 'testiny'
Using project: Demo (DE)
Import source: integration-tests
Environment: gitlab
Processing nunit file: report.xml
Submitted 168/168 results
Completed 1 automation test run(s)
Imported all 1 file(s) successfully
Submitted Testiny automated run ids: 264

The CLI will parse the report file, create an automation run in Testiny and add all results, errors and attachments to the run. The run is added to the specified project. The source name is used to group your test runs together (so choose a name that fits your test suite, e.g. frontend-tests, backend-tests, e2e-tests, api-tests, ...). In the console output, you can see how many test files have been processed and how many results and attachments have been uploaded.

If the CLI is executed in a CI environment, it auto-detects various environment variables like commit hashes and tags, pipeline and job IDs, and adds these fields to your automation run. Also see our examples for CI/CD integration.

Learn more about automation concepts, adding fields to your run and parallel testing in our detailed Automation Guide.

Reporters & examples

For some automation frameworks, we offer custom reporters where you don't need to install and handle the CLI yourself. See all available reporters and usage examples.

Next steps