Glossary - QA Testing Terms & Definitions
Complete glossary of QA testing terms used in Qualflare. Definitions for workspaces, projects, test cases, launches, defects, and more.
Glossary
Quick reference for key terms and concepts in Qualflare. For general QA and testing definitions — flaky tests, test observability, test management, and more — see the Qualflare QA glossary.
A
Access Token
A project-scoped API key used to authenticate the Qualflare CLI and other integrations. Access tokens are created and managed in Project Settings → Access Tokens. See Access Tokens.
AI Credits
A monthly usage quota that limits AI-powered operations (coverage analysis, case suggestions, launch analysis, etc.). Quota varies by subscription plan. See AI Credits by Plan.
Audit Log
A workspace-level record of every significant action taken by team members or the system. Used for compliance and security review. See Audit Logs.
Automated Testing
The practice of using software to execute tests automatically, without manual intervention. Results can be uploaded to Qualflare via the CLI. See Executing Tests.
C
Case Run
An individual test result within a Launch. Represents the outcome (pass, fail, skip) of executing a single Test Case. See Case Runs.
CI/CD
Continuous Integration / Continuous Deployment. The practice of automatically building, testing, and deploying code. Qualflare integrates with CI/CD pipelines via the CLI. See CI/CD Integration.
CLI
Command Line Interface. The qf command-line tool that uploads test results from 23 frameworks to Qualflare. See CLI Tool.
Cluster
A group of test failures identified as similar by Qualflare's AI. Also called a Failure Cluster. Clusters help identify recurring root causes across multiple test runs. See Failure Clusters.
Coverage Score
An AI-generated score (0–100%) representing how thoroughly a test suite covers different test types, priorities, quality dimensions, and scenarios. Generated by the Quo Agent.
D
Defect
A bug or issue found during testing. Defects can be linked to failed test cases and tracked through their resolution lifecycle. See Defects.
E
Environment
The system where tests run (dev, staging, production). Test results in Qualflare can be tagged with environment information. See Environments.
F
Failure Cluster
See Cluster.
Flaky Test
A test case that passes after being retried, indicating non-deterministic or environment-sensitive behavior. Qualflare detects flaky tests automatically based on retry patterns. See Launch Analytics.
L
Launch
A test execution event that captures results from running tests. Contains pass/fail summary, individual case runs, and analytics. Can be created manually or via CLI upload. See Launches.
M
Manual Testing
Testing performed by humans, as opposed to automated scripts. Qualflare supports tracking both manual and automated test execution. See Executing Tests.
Milestone
A release version or sprint used to organize defects and launches. Helps track quality progress toward a release. See Milestones.
O
Open Source Plan
A free Qualflare plan for public, OSI-licensed GitHub repositories: Scale-tier volume limits, a public report page, and a README badge/banner. Activated per-workspace by linking an eligible repository. See Open Source.
P
Pass Rate
The percentage of tests that passed in a launch or across multiple launches. Used to track quality trends over time. See Pass Rate Calculation.
Project
A container within a Workspace that organizes test cases, launches, and results around a specific product or component. See Projects.
Q
Quo Agent
Qualflare's AI assistant (also called "Quo"). Used for coverage analysis, test case generation, step generation, and answering questions about test management. See Quo Agent.
S
Saved Query
A named, reusable filter combination on the Explore page. Saved queries can be loaded to instantly apply a set of filters to the case table. See Exploring Cases and Saved Queries.
Shared Steps
Reusable test steps that can be referenced by multiple test cases. Examples: login procedures, setup steps, common actions. See Shared Steps.
T
Team
A group of project members. Suites and defects can be assigned to teams for filtering and responsibility tracking. See Teams.
Test Case
An individual test that defines what to test, steps to execute, and expected results. The fundamental building block of testing in Qualflare. See Test Cases.
Test Plan
A schedule for test execution. Selects test cases from suites, assigns testers, and tracks completion status. See Test Plans.
Test Runner Wizard
A guided interface for manually executing test cases from a test plan. Records passed, failed, blocked, or skipped verdicts for each case. See Running Tests with the Test Runner Wizard.
Test Suite
An organized collection of test cases grouped for management and execution. Examples: "Authentication Tests", "Smoke Tests", "Regression Suite". See Test Suites.
Two-Factor Authentication (2FA)
An account security feature that requires a second verification step (usually a code from an authenticator app) when logging in. See Two-Factor Authentication.
W
Webhook
An HTTP callback that Qualflare sends to an external URL when specific events occur (e.g., test results collected, defect created). Configured per project. See Webhooks.
Workspace
The top-level container in Qualflare where teams collaborate. Contains projects, manages team members, and controls access. See Workspaces.
See Also
- Concepts - Detailed explanations of core concepts
- Quick Start - Get started with Qualflare
- FAQ - Frequently asked questions
Project Settings
Project settings reference. Configure test case templates, custom fields, integrations, and project-level preferences in Qualflare.
Integrations
Connect Qualflare to your existing tools. Integrate with GitHub, Slack, GitLab, Jira, and more to sync defects, receive notifications, and automate your QA workflow.