Test Cases

What a test case is in Qualflare and why it's kept separate from automation scripts, plus its structure, lifecycle states, and relationships to suites and plans.

A test case is an individual test that defines what to test, how to test it, and what the expected result should be. Because a test case describes intent rather than implementation, it stays valid even as the underlying automation framework changes — a whole team (QA, product, support) can read and agree on what's being tested without knowing Selenium, Cypress, or Playwright.

Test Cases vs Test Scripts

Test Cases describe what to test in a framework-agnostic way. They focus on behavior and outcomes, not implementation details.

Test Scripts (automation) implement test cases in code using frameworks like Selenium, Cypress, or Playwright. A single test case can have multiple automated test scripts.

What is a Test Case?

Test cases are the fundamental building blocks of testing in Qualflare. Each test case documents:

Title: Clear, descriptive name for the test
Description: What is being tested and why
Steps: Step-by-step instructions to execute the test
Expected Result: What should happen if the system works correctly
Priority: Importance level (critical, high, medium, low)
Tags: Labels for categorization and filtering

Test Case Structure

## User Login with Valid Credentials

**Steps:**
1. Navigate to login page
2. Enter valid email and password
3. Click login button

**Expected Result:** User is redirected to dashboard
**Priority:** Critical
**Tags:** auth, smoke

Test Case Lifecycle

Test cases have four states:

Active: Ready to be executed
Review: Flagged for review before next execution
Outdated: Content may no longer reflect current behavior
Draft: Being written, not yet ready for execution

Test cases and suites can also be archived (a separate toggle), which hides them from default views while preserving their history.

Test Case Relationships

Test Suites: Test cases are organized into suites for group execution
Test Plans: Test cases are selected for specific test runs
Launches: Test cases are executed and produce results
Defects: Failed test cases can be linked to defects

Creating Test Cases - Step-by-step workflows for creating and managing test cases
Test Cases Reference - Complete UI reference for test case fields and actions
Test Suites - Organizing test cases
Test Plans - Selecting test cases for execution
Launches - Executing test cases and viewing results
Shared Steps - Reusable test steps

Test Cases - Concept, Structure & Lifecycle