Frequently Asked Questions
Find quick answers to common questions about Qualflare. Can't find what you're looking for? Check the Troubleshooting guide or browse our detailed documentation.
Getting Started
What is Qualflare?
Qualflare is a QA test management platform that helps teams organize, execute, and track their software testing efforts. It provides both a web application for manual test management and a CLI tool for integrating automated test results from CI/CD pipelines.
See also: Quick Start Guide, 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 20+ frameworks (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: CLI Installation, Collect Command
Is there a free plan available?
Yes. Qualflare offers a Starter (free) tier that includes:
- 1 user per workspace
- 1 project
- Up to 500 test cases
- Basic test management features
- Community support
Upgrade to a paid plan for more users, advanced features, AI capabilities, and priority support.
See also: Plans & Pricing
How do I get started?
- Sign up at qualflare.com
- Create test cases or import existing tests
- Organize tests into suites and plans
- Run tests manually or via the CLI tool
See also: Quick Start Guide
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 collection of test suites (and individual cases) scheduled for execution together
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, Test Suites, 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, Test Execution Guide
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.), duration, and optional notes or defects. Launches contain multiple case runs — one for each test case executed.
See also: Case Runs, Launches Reference
Using the Web UI
How do I create a test case?
- Navigate to your project
- Click Browse in the sidebar
- Open a suite and click New Case
- Enter the test case title, description, and steps
- Set priority and automation status
- Save the test case
See also: Creating Test Cases, Test Cases Reference
How do I organize tests into suites?
- Navigate to Browse in your project
- Click New Suite
- Enter suite name and description
- Add test cases to the suite
- Save the suite
You can organize suites by feature, module, priority, or any criteria that suits your workflow.
See also: Test Suites Reference
How do I run tests?
Manual execution:
- Create a test plan with your test suites
- Click Launch Wizard on the test plan
- Select the environment and language
- Work through each test case, recording verdicts (Passed, Failed, Blocked, Skipped)
- Finalize the launch when all cases are complete
Automated execution:
- Use the CLI tool (
qf collect) to upload results from your CI/CD pipeline
See also: Test Runner Wizard, Executing Tests
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-generated analysis (Core plan and above)
- Associated defects and notes
Use filters to find specific launches by date, environment, or status.
See also: Launches Reference, Analytics
How do I collaborate with my team?
Qualflare supports team collaboration through:
- Comments: Add comments to test cases, launches, and defects
- Assignments: Assign defects to team members
- Teams: Group members into teams and assign suites or defects
- Tags: Use tags to categorize and filter items
- Shared Workspaces: All team members access the same project data
See also: Collaboration Guide, Teams Reference
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 20+ frameworks: 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 20 testing frameworks across five categories:
| Category | Frameworks |
|---|---|
| Unit Testing | JUnit, pytest, Go testing, Jest, Mocha, RSpec, PHPUnit |
| BDD | Cucumber, Karate |
| E2E / UI | Playwright, Cypress, Selenium, TestCafe |
| API Testing | Newman (Postman), k6 |
| Security | OWASP ZAP, Trivy, Snyk, SonarQube |
Run qf list-formats to see the full list with --format values.
See also: Collect Command
How do I install the CLI tool?
macOS (Homebrew):
brew install qualflare/tap/qfLinux/macOS (binary):
curl -sSL https://get.qualflare.com/install.sh | shWindows (Chocolatey):
choco install qfDocker:
docker pull ghcr.io/qualflare/qf:latestSee also: Installation Guide
How do I integrate with CI/CD?
Basic integration steps:
- Install the CLI in your CI environment
- Set the
QF_API_KEYenvironment variable (from Project Settings → Access Tokens) - Run your tests
- Collect results with
qf collect
Example (GitHub Actions):
- name: Run tests
run: pytest --junitxml=results.xml
- name: Upload to Qualflare
run: qf collect results.xml
env:
QF_API_KEY: ${{ secrets.QF_API_KEY }}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:
*.xmlfiles 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 collect results.json --format jestSee also: Collect Command
Account & Billing
What are the user limits per plan?
User limits depend on your plan:
- Starter (Free): 1 user per workspace
- Core: Up to 20 users per workspace
- Scale: Unlimited users
- Enterprise: Unlimited users
See also: Plans & Pricing
What pricing tiers are available?
- Starter: Free — 1 user, 1 project, 500 test cases, basic features
- Core: $19/user/month — 20 users, 5 projects, AI features, advanced reporting
- Scale: $59/user/month — Unlimited users and projects, Quo Pro AI, audit logs
- Enterprise: Custom — SAML SSO, custom branding, dedicated support
All plans include a 14-day free trial of Scale features.
See also: Plans & Pricing
How do I upgrade my plan?
- Go to Workspace Settings
- Click Plan & Billing
- Select your desired plan
- Enter payment information
- Confirm the upgrade
Upgrades take effect immediately.
See also: Workspace Settings
How long is test data retained?
- Starter: 30 days
- Core: 90 days
- Scale: 1 year
- Enterprise: Custom (up to multiple years)
Launch history, test results, and attachments are retained according to your plan.
See also: Plans & Pricing
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.
Authentication uses project-scoped access tokens (Project Settings → Access Tokens).
See also: Access Tokens
Can I export my data?
Yes. From the Browse page, click Export to download your test suites and cases as a Qualflare CSV file. You can select specific suites or export everything at once.
See also: Import & Export
What integrations are available?
Qualflare integrates with:
- Issue Tracking: GitHub Issues, GitLab Issues, Jira
- Notifications: Slack
- Custom: Webhooks (HTTP callbacks on any event)
Configure integrations in Workspace Settings → Integrations (install) and Project → Integrations (configure per project).
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 (Enterprise)
- Access Control: Role-based permissions per workspace and project
- Two-Factor Authentication: Optional 2FA for all accounts
- Session Management: View and revoke active sessions
See also: Account Security, Privacy Policy
What browsers are supported?
Qualflare supports the latest versions of:
- Google Chrome
- Mozilla Firefox
- Apple Safari
- Microsoft Edge
Still have questions? Contact our support team or check the Troubleshooting guide.