Test Automation,
Connected to Your Coverage.
Run your automated suites where you already do, then push the results into BesTest through the REST API. Manual and automated coverage, finally in one place inside Jira.
You create your own token in the app. See how →
How it works
Run in CI
Your Playwright, Cypress, or any-framework suite runs where it already does - Jenkins, GitHub Actions, GitLab, Bitbucket Pipelines, or any pipeline.
Push results via REST API
Record each result against its execution in the cycle, with a token you create in the app. Match tests by their automation key, no manual data entry.
PATCH /api/v1/test_case_executions/{id}
If-Match: "<etag>"
{ "data": {
"type": "test_case_executions",
"id": "{id}",
"attributes": { "result": "PASSED" } } }One coverage picture
Automated results sit beside manual executions in the same cycles, reports and release readiness, against the same requirements - so nothing is reported twice or missed.
Illustrative data. The request shape is real: see the API reference for every endpoint and field.
Your coverage picture, wired into your pipeline
The REST API is the programmatic door to the same requirements, tests and results your team works with by hand. A few of the things teams build first:
Push CI results into coverage
Record PASSED, FAILED or BLOCKED from Playwright, Cypress, JUnit or Postman against a cycle - automated runs sit beside your manual ones, linked to the same requirements.
Gate releases in CI
Ask the API whether a cycle is green - one request returns a count per result - and fail the build when it is not. No more shipping on a hunch.
Feed your own dashboards
Pull requirements, test cases, links and execution history into Grafana, Power BI or a data warehouse, and chart release readiness exactly the way your org wants it.
Keep test cases in sync with code
Create and update test cases and their steps from your repo, so the catalog always matches what is actually automated.
Bulk import and migrate
Move requirements and test cases over from a spreadsheet or another tool with an agent over MCP (batches of up to 100) or the in-app CSV importer, instead of re-keying them by hand.
Automate cycle setup
Spin up a test cycle per release or sprint and populate it programmatically, so the run is ready the moment the build is.
Works with your stack
Language and framework agnostic. If it runs in your pipeline and can make an HTTP request, it will report into BesTest.
Live in about a minute.
- ~30 seconds1.Install from the Marketplace
One click on "Get it now" - no sales call, no signup form, no separate login.
- ~1 minute2.Enable it on a Space
Flip it on in Space settings. BesTest shows up in the Space menu, where your team already works.
- right away3.Run your first test
Create a requirement, link a test case, hit run. No training course required.
Ready to Get Complete
Testing Visibility?
Start using BesTest today and experience complete testing visibility from requirements to release. Free to get started!
Available on the Atlassian Marketplace. Install in seconds, free for up to 10 users.
Start Free on Marketplace