Skip to content
The docs are now organized by product area. Old links still work. Report a broken link

Frequently Asked Questions

Answers to common Qualflare questions about getting started, features and concepts, the web UI, the qf CLI, account and billing, and technical details.

Last updated

Find quick answers to common questions about Qualflare. For error messages and fixes, see Troubleshooting; for sign-in problems, see Sign-in and account problems; for release notes, see What's new; for what a term means, see the Glossary; and to reach a person, see Contact support.

Getting Started

What is Qualflare?

Qualflare is an AI-driven test management and observability platform. Teams use it to organize, run and track their software testing: a web application for manual test management, and a CLI that uploads automated test results from CI/CD pipelines.

See also: Quickstart, Overview

How does Qualflare work?

Qualflare works by organizing your testing efforts into workspaces (for teams/organizations), projects (for products or applications), and test cases (individual test scenarios). You can group test cases into suites and plans, then execute them as launches. Test results are tracked as case runs, and any issues found are recorded as defects.

See also: Concepts Overview, Organizational Entities

Do I need the CLI tool?

You need the CLI tool if you want to:

  • Integrate automated test results from CI/CD pipelines
  • Upload test results from 27 frameworks and 4 generic formats (JUnit, pytest, Jest, Cypress, etc.)
  • Enrich test runs with Git metadata (branch, commit)
  • Run tests in automated workflows and report results to Qualflare

If you only do manual testing, the web UI may be sufficient.

See also: Install Qualflare CLI, Upload results with qf collect

Is there a free plan available?

Yes. The Starter plan is free. It includes:

  • 3 team members
  • 2 projects
  • Up to 1,000 test cases and 100 test reports (launches) per month
  • A separate allowance of 25 AI report analyses per month
  • Quo, with 100 messages per month

Projects with a public, OSI-licensed GitHub repository can use the free Open Source plan instead. Paid plans add more seats, higher limits, and features such as AI Insights and Quo Pro.

See also: Plans and limits

How do I get started?

  1. Sign up at https://app.qualflare.com/register and name your workspace and first project
  2. Upload results: install the qf CLI, run qf login <identifier> and approve in your browser, then qf <identifier> collect <report>
  3. Test by hand: with no automated tests yet, write test cases and record verdicts in the Test Wizard

See also: Quickstart, Tutorial: run a manual regression cycle

Features & Concepts

What's the difference between test cases, suites, and plans?

  • Test Case: A single test scenario with steps and expected results
  • Test Suite: A collection of test cases grouped by feature, module, or type
  • Test Plan: A saved selection of test cases, picked one by one or a whole suite at a time, that you run by hand in the Test Wizard. Plans don't run on a schedule

Think of it like files, folders, and playlists: cases are individual tests, suites organize them, and plans are ready-to-run test playlists.

See also: Test cases: fields, states and steps, Test suites and Browse, Test Plans

What are environments?

Environments represent different deployment targets where you run tests (e.g., Development, Staging, Production). Each launch can be associated with an environment, allowing you to track test results across different stages of your deployment pipeline.

See also: Environments, Launches

How do launches work?

A launch is a single test run. When you execute a test plan or collect results via the CLI, Qualflare creates a launch containing case runs (individual test executions) for each test case. Launches capture the state of your tests at a point in time, including results, duration, and environment.

See also: Launches, Run tests: manual and automated

What are shared steps?

Shared steps are reusable test step sequences that can be referenced across multiple test cases. They help you:

  • Avoid duplicating common test procedures
  • Maintain consistency across tests
  • Update steps in one place

For example, a "Login" shared step can be used by any test that requires authentication.

See also: Shared Steps

What are case runs?

A case run is a single execution of a test case within a launch. Each case run has a status (Passed, Failed, Skipped, etc.), a duration, failure details, steps and attachments. Launches contain multiple case runs — one for each test case executed.

See also: Case Runs, Launches

Using the Web UI

How do I create a test case?

  1. Click Browse in your project's sidebar, click a suite and open its Test Cases tab. To start a new suite, click Create Suite first
  2. Click Create Case, enter a Name and click Create. The dialog saves only the name
  3. Open the case and add steps on its Steps tab. Write the expected result as a step of type Expected Result
  4. Set the priority and description from the ⋯ menu next to the case name

See also: Create and edit test cases, Test cases: fields, states and steps

How do I organize tests into suites?

  1. Navigate to Browse in your project
  2. Click Create Suite
  3. Enter a name and description, pick a priority, and click Create
  4. Open the suite and add cases from its Test Cases tab with Create Case

Each case belongs to exactly one suite. You can organize suites by feature, module, priority, or any criteria that suits your workflow, and assign each one to a team.

See also: Test suites and Browse

How do I run tests?

Manual execution:

  1. In Test Plans, click Create Run (play) on a plan. Or go to Launches, click Start Launch and pick suites.
  2. Check the environment and language: in the Start Launch dialog, or in the Test Wizard before your first verdict
  3. Work through each test case, recording verdicts (Passed, Failed, Blocked, Skipped)
  4. Click Finalize Launch when all cases are complete

Automated execution:

  • Use the CLI tool (qf <identifier> collect) to upload results from your CI/CD pipeline

See also: Test Wizard, Run tests: manual and automated

How do I view test results?

Navigate to Launches in your project and click on a launch to see:

  • Overall pass/fail statistics
  • Individual case run results
  • Duration and environment details
  • AI launch analysis, for launches you upload (Starter includes 25 per month, independently of report uploads)
  • Comments on the launch

Filter the Launches list by platform, automation (automated or manual), environment or language, or search it.

See also: Launches, Analytics

How do I collaborate with my team?

Qualflare supports team collaboration through:

  • Comments: Add comments to test cases, defects, launches, and milestones
  • Assignments: Assign people to milestones
  • Teams: Group project members into teams and assign suites or defects to a team
  • Tags: Use tags to categorize and filter items
  • Project invitations: Invite people to a project by email; their role decides what they can do

See also: Invite and manage users, Project teams

What roles can people have in Qualflare?

Qualflare has five roles, from least to most access: Guest, Viewer, Editor, Maintainer and Owner. The same roles apply to a workspace and to each project, and in a project you get the higher of your workspace role and your project role. Each role has the permissions of the one before it: a Viewer can read, an Editor can also write, a Maintainer can also manage members, and an Owner can also delete. A Guest is someone a project invitation brought into the workspace, with no workspace permissions of their own.

See also: Roles and permissions

CLI Tool

Why should I use the CLI tool?

The CLI tool enables you to:

  • Integrate with CI/CD: Upload test results from automated builds
  • Support 27 frameworks and 4 generic formats: JUnit, pytest, Jest, Cypress, Playwright, and more
  • Enrich with Git data: Automatically capture branch and commit information
  • Validate locally: Check test result files before uploading
  • Query your data: List suites, cases, launches, defects, and more via JSON output

See also: CLI Overview, Installation

What frameworks are supported?

The CLI supports 27 frameworks and 4 generic formats, grouped in six categories:

CategoryFrameworks
Generic (JUnit-compatible)JUnit XML, CTRF, Allure results, qualflare-json
Unit Testingpytest, Go testing, Jest, Vitest, Mocha, RSpec, PHPUnit, TestNG
BDDCucumber, Karate
E2E / UI / MobilePlaywright, Cypress, Selenium, TestCafe, Maestro, XCTest, Espresso, Detox, WebdriverIO, Appium, Flutter
API TestingNewman (Postman), k6
SecurityOWASP ZAP, Trivy, Snyk, SonarQube

Run qf list-formats to see the full list with --format values.

See also: Supported formats

How do I install the CLI tool?

macOS or Linux (Homebrew):

brew install qualflare/tap/qf

macOS, Linux or Windows (npm):

npm install -g @qualflare/cli

Docker (no qf install needed):

docker run --rm ghcr.io/qualflare/qf:0.7.0 version

Release binaries: download the archive for your OS and CPU from the GitHub releases page.

See also: Install Qualflare CLI

How do I integrate with CI/CD?

Basic integration steps:

  1. Install the CLI in your CI environment
  2. Create an access token in your project under Settings → Access Tokens, and store it as a CI secret named QF_TOKEN
  3. Run your tests
  4. In the same job, run qf login ci --force (it reads QF_TOKEN), then qf ci collect <files>

Example (GitHub Actions):

- name: Run tests
  run: pytest --junitxml=results.xml

- name: Upload to Qualflare
  if: ${{ !cancelled() }}
  run: |
    qf login ci --force
    qf ci collect results.xml
  env:
    QF_TOKEN: ${{ secrets.QF_TOKEN }}

On GitHub Actions you can also use the qualflare-action, which installs qf for you.

See also: CI/CD Integration

How does auto-detection work?

The CLI automatically detects your test framework based on file name patterns and content. For example:

  • *.xml files with JUnit structure → JUnit
  • *playwright* JSON files → Playwright
  • *cypress* JSON files → Cypress
  • *trivy* JSON files → Trivy

If auto-detection fails, specify the format explicitly with --format:

qf myapp collect results.json --format jest

See also: How qf picks a format

Account & Billing

What are the user limits per plan?

Each plan has a team member limit:

  • Starter (free): 3 members
  • Core: up to 10 members
  • Scale: up to 50 members
  • Enterprise: Custom (contact us)

On a paid plan, the limit is the number of seats you buy, up to the plan's maximum. During a trial, Core has 10 seats and Scale has 25.

See also: Plans and limits

What pricing tiers are available?

Qualflare has four plans:

  • Starter: free. 3 members, 2 projects and 1,000 test cases.
  • Core: up to 10 members, 5 projects and 5,000 test cases. Adds AI Insights and Quo Pro.
  • Scale: up to 50 members, 25 projects and 50,000 test cases. Adds audit logs, SAML single sign-on and verified domains.
  • Enterprise: everything in Scale, plus SCIM provisioning and the highest limits.

Core and Scale start with a 14-day free trial when you choose the plan at sign-up. You don't need a credit card. For prices, see qualflare.com/pricing.

See also: Plans and limits

What happens when my workspace reaches a plan limit?

At a plan limit, Qualflare refuses only the request that would go past it, and nothing already stored is lost. At the monthly test report limit, uploads and runs started in the app are refused until the monthly reset or an upgrade. At the test case or suite limit, creating, cloning and importing are refused, and so is an upload that contains tests the workspace hasn't seen before; an upload of tests it already has is still accepted. To continue, wait for the monthly reset, delete what you don't need, or upgrade. A workspace with more members or projects than its plan allows is frozen until it fits.

See also: What happens at a limit, A frozen workspace

How do I upgrade my plan?

Only the workspace Owner can change the plan:

  1. In the workspace sidebar, open Plan & Billing
  2. Select Upgrade Plan
  3. Choose Monthly or Yearly, then select Get Core or Get Scale
  4. Set the number of seats and select Continue to Checkout
  5. Pay in Stripe Checkout

If the workspace already pays for a plan, step 3 shows Upgrade in billing portal instead, and lower plans show Downgrade in billing portal. You switch the plan and set the seats in the Stripe billing portal, which also moves a subscription from Scale to Core or between monthly and yearly billing. A change takes effect at once, and Stripe invoices the difference at that moment.

For Enterprise, select Contact Sales. During a trial, Plan & Billing shows Subscribe and pay instead of Upgrade Plan. Subscribing ends the trial and starts billing immediately.

See also: Changing plans, Workspaces and Workspace Settings

How do I cancel my subscription?

Only the workspace Owner can. Open Plan & Billing, select Manage Billing, and cancel your subscription in the Stripe billing portal that opens. When the paid period ends, the workspace moves to Starter. Cancelling is how you return to Starter; to move from Scale to Core, switch the plan in the same portal instead.

See also: Changing plans

How long is test data retained?

Retention is the same on every plan, and there is no retention setting. Test cases, launches and results are kept until someone deletes them.

Qualflare deletes some data automatically:

  • Screenshots, videos and trace files that qf <identifier> collect uploads with test results: deleted 30 days after upload. Download any you need to keep.
  • Export files: deleted 30 days after the export is created.
  • Audit log entries: removed from the audit log after 365 days.

Trend charts show at most the last 90 days. Your launches and results stay.

See also: Data Retention, Audit Logs

Technical

Is there an API available?

Yes. Qualflare provides a REST API for programmatic access to your test data. You can create and manage test cases, upload test results, query launches, and more.

The REST API authenticates with project-scoped access tokens (Project Settings → Access Tokens). The CLI and MCP clients sign in through your browser instead, so only CI and scripts need a token.

See also: Access Tokens

Why did my access token stop working?

Access tokens expire. When you create one, you choose an Expiration of 7, 30, 60 or 90 days (30 by default), so no token lasts more than 90 days. Qualflare emails the token's creator 7 days before it expires, except for 7-day tokens. A token also stops working when it's revoked or when its creator's account is deactivated, and it can never do more than its creator's current project role allows. Create a new token, update the secret your CI uses, then revoke the old one (or ask a Maintainer or Owner to).

See also: Access Tokens

Can I use Qualflare from Claude Code or another coding agent?

Yes. The Qualflare plugin for Claude Code generates tests, runs your suite, uploads the results and fixes failures from the chat. Claude, Claude Code and Lovable, and other clients that support MCP sign-in, can also connect to the Qualflare MCP server at https://api.qualflare.com/mcp: add the URL, sign in on app.qualflare.com, pick a project, choose Allow changes or read-only and approve. You need the Editor role or higher on the project. Connections are listed under Project Settings → Access Tokens → Connected apps, where you can revoke them. A client that only sends a fixed header, such as a JSON config in Cursor, uses a project access token instead.

See also: Claude Code plugin, Connect a coding agent (MCP)

Do I still need an access token?

Not to use the CLI or connect an MCP client: qf login <identifier> and MCP clients sign in through your browser. Use an access token for CI and scripts, where there is no browser (QF_TOKEN), and for agents that can't sign in.

See also: Authenticate with qf login, Access Tokens

Can I export my data?

Yes. In Browse, open Browse actions (⋮) and choose Export to download your cases and steps as a ZIP of CSV files. You can select specific suites or export everything at once. Qualflare cannot import its own export, so it is not a way to restore cases.

See also: Import & Export

What integrations are available?

Qualflare integrates with:

  • Issue tracking: GitHub, GitLab, Jira and Linear, plus pages in a Notion database
  • Notifications and alerting: Slack, Microsoft Teams, Discord and PagerDuty
  • Webhooks: a signed HTTP POST to your own endpoint when test results are uploaded, or when a defect is created on the Defects page, through the API or MCP, or for a flaky test, set up per project in Project Settings → Webhooks

Install integrations in Workspace → Integrations, then configure each project in Project → Integrations.

See also: Integrations Overview

How is my data secured?

Qualflare implements multiple security measures:

  • Encryption: All data encrypted in transit (TLS) and at rest
  • Authentication: Secure access tokens, SSO support (Scale and Enterprise)
  • Access Control: Role-based permissions per workspace and project
  • Two-Factor Authentication: An authenticator app or passkeys on any account. Workspace Owners can require it for every member.
  • Session Management: View and revoke active sessions

See also: Account Security, Privacy Policy

Does Qualflare use my data to improve its AI?

The Help improve Qualflare AI setting on the Workspace Settings page is on by default. While it's on, Qualflare keeps a record of AI requests from your workspace: the prompt, the result, and the failure messages and test names involved. Email addresses and common token, key and password formats are removed first. Other text, such as names, hostnames and internal URLs, is kept as written. Anyone with the Editor, Maintainer or Owner workspace role can turn the setting off, and collection stops within about five minutes. Records collected before then can't be withdrawn, because they carry no workspace or project ID.

See also: Shared responsibility

What browsers are supported?

Qualflare supports the latest versions of:

  • Google Chrome
  • Mozilla Firefox
  • Apple Safari
  • Microsoft Edge

Still have questions? Contact support or check Troubleshooting.