Your automated tests already produce results — pass/fail, screenshots, traces. The problem is they live in your CI logs, disconnected from the test cases and plans your team actually tracks. Arqo's automation API closes that gap: your Playwright, Cypress, or Selenium suite can create a test run, report each result, and upload evidence directly into Arqo. No more copy-paste between your pipeline and your test management tool.
How it works
Arqo exposes a small REST API for automated runs. Your CI job authenticates with a project API key, creates a run, posts results as they complete, and attaches artifacts. Everything shows up in Arqo alongside your manual runs — same reports, same PDF exports, same pass/fail history.
- Create a test run from CI (named after your build or commit)
- Report each case as passed / failed / blocked, with notes
- Upload screenshots, recordings and traces as evidence
- Complete the run — Arqo builds the summary and fires your Slack notification
Get an API key
In your project, open Settings → Integrations and generate an automation API key. Keep it in your CI secrets (e.g. a GitHub Actions secret) — never commit it.
Playwright
The cleanest approach is a small custom reporter that maps Playwright's results to Arqo cases and posts them at the end of the run. Point each spec at the Arqo test case it verifies (a tag or title convention works well), create the run at the start, and report on completion. Failed specs upload their screenshot/trace automatically as evidence.
Note: Tip: name the Arqo run after your CI build number or Git SHA so every run is traceable back to the exact pipeline that produced it.
Cypress
Cypress plugins expose after:run and after:spec hooks — perfect for reporting. Create the Arqo run in before:run, collect results per spec, and post them (with screenshots from cy.screenshot() or on-failure captures) as each spec finishes. Cypress videos can be attached as recordings.
Selenium
Selenium doesn't prescribe a reporter, so you hook in at your test-framework layer — JUnit/TestNG listeners (Java), pytest hooks (Python), or Mocha/Jest reporters (JS). Each maps the framework's pass/fail events to an Arqo result call and uploads any screenshots your teardown captures.
What you get
- One home for automated and manual results — no more two sources of truth
- Evidence attached to every failure, viewable in the run and the PDF report
- Trend and coverage reporting across your whole suite, CI included
- Slack notifications on run completion, with the pass/fail breakdown
The result: your CI stops being a black box. Every automated run lands in Arqo next to your test cases, ready to review, report on, and share — the same way your manual testing already does.