Automation and API
Your automated tests report to the same place as your manual ones.
Results from CI
- JUnit XML, which almost every test framework writes
- one run per plan and CI build; sending again updates the same run
- new tests become automated cases, matched by their key from then on
Access for CI
- CI users that work only through the API, with no password and no screens
- API keys shown once, valid up to a year
- each status mapped to yours: passed, failed, error, skipped
Tools
- a one-file upload tool for any CI
- examples for GitHub Actions, GitLab CI and Jenkins
- Import Results on a plan or run for a file saved by hand
An API for everything else
A documented JSON API reads the test design and creates runs, reports results and attaches files. Team members can make their own keys, valid up to 90 days, with their role's rights.
Want to see it live?
Look around the demo workspace, or let us show you IRWiz.