Upload Test Results and Evidence Through Your Agent
Running the tests is the real work. Filing the results is not: statuses to click, failures to document, bugs to raise and link. Hand the filing to your agent and the paperwork happens while you keep testing.
The results exist. Getting them filed is the work.
After a test session the truth lives in your head, a terminal, or a JUnit file. Between that truth and a tidy cycle sits the clicking: open each execution, set the status, describe the failure, raise the bug, link the bug. Multiply by fifty executions.
So results get filed late, thin, or not at all, and the reports everyone relies on quietly under-report reality. We run BesTest’s own QA through this MCP, cycles with hundreds of executions included, because filing by conversation is how filing actually happens.
The filing chore
- Open each execution and click a status, one by one
- Retype failure details from the terminal into comment boxes
- Raise bugs separately, then link them back by hand
- Skip the tedium on busy days and let reports drift from reality
Filing by conversation
- Paste or point at the results, in whatever form you have them
- The agent updates every execution in the cycle with its outcome
- It raises Jira bugs for failures and links them, in the same pass
- Reports are current the moment the test run ends
One prompt, start to finish
Here are today’s regression results (junit.xml). Update cycle REG-7 in BesTest: mark each execution passed or failed with the failure details, create a Jira bug for each new failure, and link it to the execution.- 1
Parses the results, any shape
JUnit XML, a CI log, a markdown checklist from a manual session: the agent reads whatever holds the outcomes and matches them to the executions in your cycle.
- 2
Files every execution over the MCP
Statuses and failure details land on the right executions in BesTest, fifty at a time, without a single status dropdown.
- 3
Raises and links the bugs, using both MCPs
This is the two-MCP combo at work: the Jira bug is created through Atlassian’s MCP, then linked to the execution through ours, so the evidence trail is complete in one pass.
The result
Filing stops competing with testing for your time. Cycles reflect reality the moment a run finishes, failures arrive with their details attached, and every bug is born already linked to the execution that found it.
Every bug is created already linked to the execution that found it, so the trail back to the run survives.
More prompts to steal
Mark every execution in cycle SMOKE-12 as passed except the two I describe below.
Summarize cycle REG-7: pass rate, failures by feature area, and anything still not run.
Create a Jira bug for the failure in execution EX-204 with its output, and link it.
Scoped to your permissions, granted per user
Your agent acts as you: everything it reads or writes stays inside your Jira permissions. The MCP is in closed beta while we harden it, with GA coming. The request form asks for a few details from BesTest’s Project Settings in your Jira, which is what lets us enable exactly your site and user.
Request beta accessFrequently asked questions
Can it attach screenshots as evidence?
Evidence files live on the Jira side: have the agent create or link a Jira issue for the failure and attach the evidence there. BesTest keeps the execution linked to that issue, so the evidence stays one click away.
Does this replace the REST API for CI?
They complement each other. Pipelines pushing results automatically on every run is the REST API’s job; see the test automation page. The MCP shines for everything conversational: manual sessions, one-off runs, cleanup, and questions about the results afterwards.
What about very large cycles?
The agent works in batches and reports progress, so even a cycle with hundreds of executions files in reviewable waves rather than one blind operation.
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