Modern Quality Engineering
built for Software Teams
Receive your CI results as JUnit XML, review the cases Aeris (AI) proposes from your existing tests, and link each run to recent code changes.
Dashboard
Track pass rate, activity and delivery health across every project.
Executed cases
Runs
Failed cases
Runs with failures
Executed cases
Aug 30 – Sep 28
| Day | Current period |
|---|---|
| Aug 30 | 287 |
| Aug 31 | 264 |
| Sep 1 | 309 |
| Sep 2 | 227 |
| Sep 3 | 213 |
| Sep 4 | 268 |
| Sep 5 | 199 |
| Sep 6 | 199 |
| Sep 7 | 268 |
| Sep 8 | 213 |
| Sep 9 | 227 |
| Sep 10 | 309 |
| Sep 11 | 264 |
| Sep 12 | 287 |
| Sep 13 | 375 |
| Sep 14 | 333 |
| Sep 15 | 356 |
| Sep 16 | 441 |
| Sep 17 | 393 |
| Sep 18 | 407 |
| Sep 19 | 482 |
| Sep 20 | 421 |
| Sep 21 | 421 |
| Sep 22 | 482 |
| Sep 23 | 407 |
| Sep 24 | 393 |
| Sep 25 | 441 |
| Sep 26 | 356 |
| Sep 27 | 333 |
| Sep 28 | 375 |
Projects
| Project | Suites | Cases | Pass rate |
|---|---|---|---|
Typescript Ingestion SDK Last run 4h ago | 8 | 195 | 97% |
Billing & Subscriptions API Last run 45m ago | 16 | 420 | 98% |
Qably Platform Core Last run 18m ago | 24 | 840 | 99% |
Auth & Identity Service Last run 2h ago | 12 | 310 | 100% |
Cases by priority
Notification channels
Qably
| Date | Deliveries |
|---|---|
| 22 sep | 45 |
| 23 sep | 62 |
| 24 sep | 38 |
| 25 sep | 88 |
| 26 sep | 120 |
| 27 sep | 42 |
| 28 sep | 58 |
Slack #qa-incidents
| Date | Deliveries |
|---|---|
| 22 sep | 18 |
| 23 sep | 24 |
| 24 sep | 12 |
| 25 sep | 35 |
| 26 sep | 48 |
| 27 sep | 15 |
| 28 sep | 22 |
Discord #engineering
| Date | Deliveries |
|---|---|
| 22 sep | 10 |
| 23 sep | 15 |
| 24 sep | 8 |
| 25 sep | 20 |
| 26 sep | 33 |
| 27 sep | 12 |
| 28 sep | 16 |
| Date | Deliveries |
|---|---|
| 22 sep | 4 |
| 23 sep | 6 |
| 24 sep | 2 |
| 25 sep | 8 |
| 26 sep | 12 |
| 27 sep | 3 |
| 28 sep | 5 |
Recent activity
Qably Platform Core
Billing & Subscriptions API · Nightly E2E Regression #412
Auth & Identity Service
Typescript Ingestion SDK · Integration Tests CI
Works with any runner or CI that produces JUnit XML
- Jest
- Playwright
- Python (pytest)
- Go
- GitHub Actions
Quality management and test results for engineering teams
Centralize your CI results, spot unstable tests, and document cases from the tests that already exist in your code.
Case documentation from your test code
When a push changes test files, Aeris (AI) reads them and proposes documented cases (objective, steps, expected result) for your team to review.
Retries the webhook on a 429 response
- Objective
- Check that the webhook is retried when the service answers 429.
- Steps
- Configure retries with 3 attempts and a 2 s delay.
- Make the target service answer 429.
- Trigger the webhook.
- Expected result
- The webhook is retried up to 3 times and the final response is 200.
Quality review inbox
Your team reviews each proposed case, with a diff against the published version when one exists, before publishing it as an official case in Qably.
Example
JUnit report ingestion from your CI
Receives JUnit XML reports from your CI and records duration, run history, and pass rate.
Flaky test signal
Flags as unstable the tests that alternate between pass and fail across recent runs.
Repository traceability
Links each run to the commit and branch your CI reports.
Engineered to drop into your existing pipeline
Qably reads the JUnit XML your runner already writes: Vitest, Jest, Playwright, pytest or any runner that produces JUnit XML. No agents, no proprietary plugins and no changes to your tests.
# Any runner that writes a JUnit XML file works:
# npx vitest run --reporter=junit \
# --outputFile=junit.xml
# jest --reporters=jest-junit
# PLAYWRIGHT_JUNIT_OUTPUT_NAME=junit.xml \
# npx playwright test --reporter=junit
# pytest --junitxml=junit.xml
URL=https://api.qably.dev/runs/ingest/junit
curl -X POST "$URL?externalId=$RUN_ID" \
-H "Authorization: Bearer $QABLY_API_KEY" \
-H "Content-Type: application/xml" \
--data-binary @junit.xmlPlan limits
Each plan sets how many members, projects and Aeris credits your organization can use.
Free
Try Qably on one real project.
- 3 members
- 1 project
- 25 Aeris credits per month
- The whole team reviews and decides on Aeris proposals, and every decision records who made it.
- JUnit report ingestion from any CI with an API key
- Traceability across code changes, proposals, cases and runs
- Flaky test signal and case health tracking
- API keys for your CI integration
- Aeris proposes documented cases and answers questions in the project chat
- Dashboard with pass rate and recent activity
Team
For product and engineering teams that already run CI.
- 10 members
- Up to 5 projects
- 300 Aeris credits per month
- The whole team reviews and decides on Aeris proposals, and every decision records who made it.
- JUnit report ingestion from any CI with an API key
- Traceability across code changes, proposals, cases and runs
- Flaky test signal and case health tracking
- API keys for your CI integration
- Aeris proposes documented cases and answers questions in the project chat
- Dashboard with pass rate and recent activity
- Slack and Discord notifications
Enterprise
For organizations running several teams and projects at once.
- 25 members
- Unlimited projects
- 1000 Aeris credits per month
- The whole team reviews and decides on Aeris proposals, and every decision records who made it.
- JUnit report ingestion from any CI with an API key
- Traceability across code changes, proposals, cases and runs
- Flaky test signal and case health tracking
- API keys for your CI integration
- Aeris proposes documented cases and answers questions in the project chat
- Dashboard with pass rate and recent activity
- Slack and Discord notifications
Accounts start on the Free plan. Billing and plan changes are not part of this version.
Start elevating your software quality today
Connect your GitHub repository. Free plan available.