Share and export results

To share test results from Qualflare, publish a public report (Open Source plan; the Editor role or higher in the workspace), post launches to Slack or a webhook, or read them as JSON or CTRF with the REST API, qf or MCP.

Before you begin

• Public report: a workspace on the Open Source plan and Editor+ · workspace (requires the Editor role or higher in the workspace). In the web app today, you also need the Editor role or higher in this project.
• API: a project access token. Reading results does not need Allow writes.

Publish a public report

Publish a public report to share launch results with people outside your workspace.

You should see the report link, https://reports.qualflare.com/p/<project-identifier>/launches, under Public report. Share that link.

After you publish, the same section shows a badge and a banner you can embed in a README. See Publishing a report.

To take the report offline, turn the switch off. If the workspace has left the Open Source plan, the section shows an Unpublish button instead, so you can always unpublish. Publishing and unpublishing need a workspace role of Editor or higher. In the web app today, you also need the Editor role or higher in this project. See Public report.

Post results to Slack or a webhook

To post results to a team channel, connect an integration such as Slack. People who work in Qualflare can open the launch directly. Each upload can post to Slack and send the launch.completed webhook; a manual launch sends neither.

Get launches as JSON or CTRF

The app has no CSV, JSON or PDF export for launches. To get launches as JSON or CTRF, or to analyze results in other tools, use one of these options:

Call the REST API

For programmatic access to test results, use the Qualflare REST API. Requests use a project access token, and the token decides which project you read from:

// Fetch launch #123 of the token's project
const response = await fetch('https://api.qualflare.com/api/v1/launch/123', {
  headers: {
    'Authorization': `Bearer ${process.env.QF_TOKEN}`
  }
});
const launch = await response.json();

For the same launch as a CTRF JSON report, request:

https://api.qualflare.com/api/v1/launch/123/ctrf

From a terminal, qf myapp launch get 123 prints the launch as JSON.

Create an access token in your project under Settings > Access Tokens. Reading results does not need Allow writes. See Access Tokens.

For scripts and other tools:

• Use qf myapp launches list --environment staging in scripts to pull recent launches for one environment
• Use the CTRF endpoint to feed results into tools that read CTRF

Report to stakeholders

Report to stakeholders with the view each audience needs:

• Release readiness: lead with the Success Rate and the open failures of the release's launches
• Developers: send a direct link to the launch in Qualflare
• Product managers: share the Overview page with the time range and environment that matter to them
• Flaky tests: call them out explicitly, and say what is being done about them
• Be transparent: share both good and bad results, and explain why quality is improving or regressing

Troubleshoot

• The public report is empty: it shows only launches uploaded while it is published. Launches from before you published, and launches you start in the app, never appear. If the report was unpublished and published again, it starts empty and shows only new uploads.
• A manual run didn't post to Slack: only uploads send Slack messages and webhooks.

Next steps

• Analyze launch results: read a launch before you share it.
• Launches: every status, field and tab of a launch.
• MCP server reference: the launch tools AI assistants can call.