Exporting Reports
Test report export from ContextQA — share execution URLs, download evidence packages, export Playwright code, and embed results in Jira and Slack notifications.
Who is this for? QA managers, engineering managers, and VPs who need to share test results with stakeholders, create defect tickets with embedded evidence, or archive execution records for compliance.
Test report export: The set of mechanisms ContextQA provides to share, download, and embed test execution results outside the portal — including shareable URLs, downloadable artifact packages, Playwright TypeScript code generation, and defect ticket creation with embedded evidence.
Test results only create value when the right people can see them. A QA lead needs to share a failure with a developer, a release manager needs to verify a suite passed before deploying, and a compliance auditor needs a portable record of what was tested. ContextQA provides several export paths for each of these use cases. This page covers all of them.
Sharing execution reports via URL
Every execution report in ContextQA has a permanent URL that can be shared with any user who has portal access. To obtain the link:
Navigate to Test Plans → select the plan → Executions tab.
Click the execution run you want to share.
Copy the URL from your browser's address bar. The URL includes the execution ID and resolves directly to the execution report.
Paste this URL into a Slack message, a Jira comment, a pull request description, or an email. The recipient clicks the link and lands on the full execution report, including all test case results, failure categories, and artifact tabs. No special steps are needed to generate a shareable link — the execution report URL is the shareable link.
If ContextQA is configured with SAML SSO, recipients who are not logged in will be redirected to the identity provider login before reaching the report. Plan accordingly when sharing links with stakeholders who do not have portal accounts.
Downloading the evidence package
Each test case execution produces a complete evidence package: per-step screenshots (JPG), session video (WebM), network HAR, browser console log, and Playwright trace (ZIP). To download any of these:
Open the execution report for the target run.
Select a test case row to expand the step-level detail panel.
Use the artifact tabs — Video, Network, Console, Trace, AI Reasoning — at the top of the detail panel.
Click the download icon on any tab to download the artifact directly.
Downloaded artifacts are raw files: .webm for video, .har for network data, .zip for the Playwright trace, .txt for console logs. These files can be archived, attached to tickets, or loaded into external analysis tools.
S3 URL expiry: Artifact download URLs are pre-signed S3 URLs that expire after 1 hour. If you open an artifact tab and do not click download immediately, the URL may expire before the download starts. Navigate away and back to the execution report to generate a fresh URL.
Using the Playwright trace as a portable audit artifact
The Playwright trace ZIP is the most complete portable artifact ContextQA produces. It contains DOM snapshots, network waterfall, console timeline, and interleaved screenshots for every step. Critically, it requires no ContextQA account to view.
To use it as a portable audit artifact:
Download the trace ZIP from the Trace artifact tab.
Open trace.playwright.dev in any browser.
Upload the ZIP file using the drag-and-drop interface or the Upload button.
The viewer is a static web application — it works entirely in the browser with no server communication. This makes the trace ZIP a self-contained compliance record. You can attach it to a Jira epic as an audit trail, store it in a compliance evidence repository, or share it with a client who has no access to your ContextQA instance.
Exporting test case definitions as Playwright code
ContextQA test cases can be exported as executable Playwright TypeScript code. This enables two workflows: migrating test cases to a code-based repository, and running ContextQA-authored tests in a self-hosted Playwright runner outside ContextQA infrastructure.
Via MCP tools:
The export_test_case_as_code tool exports a single test case:
The export_to_playwright tool exports an entire test suite as a structured Playwright project:
Both tools produce standard Playwright TypeScript that can be added to a tests/ directory and executed with npx playwright test. The exported code uses the same selectors ContextQA uses internally, including any AI-optimized selectors generated during execution.
Embedding result links in Jira and Slack
ContextQA's Jira and Slack integrations automatically post execution result links as part of their notification payloads. The result URL embedded in these notifications points directly to the execution report.
Jira: When ContextQA is configured with the Jira integration, a test plan completion can automatically create or update a Jira issue with the execution result. The issue body includes a direct link to the execution report.
Slack: The Slack integration posts a result message to the configured channel. The message includes the plan name, pass/fail counts, and a link to the execution report. Users can click the link directly from Slack without navigating through the ContextQA portal.
If you want to manually embed a result link — for example, in a pull request comment — use the execution report URL from the portal (see the sharing section above) and paste it directly.
Creating defect tickets with embedded evidence
When a test case fails, ContextQA can create a defect ticket directly in Jira (or other connected issue trackers) via the create_defect_ticket MCP tool. The created ticket automatically includes:
The test case name and the failing step number
The error message from the failing step
A screenshot of the failing step (as an attachment or inline image, depending on Jira configuration)
A direct link to the full execution report in the ContextQA portal
The AI-generated root cause classification and fix suggestion
To create a defect ticket manually from the portal:
Open the execution report and navigate to the failing test case.
Click the Create Defect button on the failing step row.
ContextQA opens a pre-populated ticket creation dialog with the evidence fields already filled in.
Review the fields, select the target Jira project, and click Create.
The defect ticket provides enough context for a developer to investigate the failure without needing portal access — the screenshot and error message are attached, and the execution report link provides the full trace for deeper analysis.
Frequently Asked Questions
Can I export a full test plan result as a PDF or CSV?
ContextQA does not currently produce a PDF or CSV export of execution results from the portal UI. The recommended approach for compliance or management reporting is to share the execution report URL (which is always live and up to date) or to download individual artifacts. If you need structured data, the get_test_case_results and get_test_step_results MCP tools return JSON that can be transformed into any format.
Are exported Playwright test files immediately runnable?
Yes, with the caveat that they require a valid playwright.config.ts and the @playwright/test package installed. The export_to_playwright tool produces a complete project structure including a basic config. You may need to configure baseURL and authentication setup in the config to match your target environment.
How long does ContextQA store execution reports?
Execution reports and their associated artifacts are retained according to your organization's storage policy, which is configurable in Settings → Organization Settings. The reports themselves (metadata, pass/fail results, step data) are retained independently of artifact storage and may be available for longer periods than the raw artifact files.
Can I share an execution report with someone outside my organization?
Currently, execution report URLs require portal authentication. To share results with external stakeholders, download the relevant artifacts (trace ZIP, screenshots) and share the files directly, or export the test case as a Playwright code file and share that.
Related
Get release readiness reports your stakeholders understand. Book a Demo → — See the analytics dashboard, failure analysis, and flaky test detection for your test suite.
Last updated
Was this helpful?