Creating a Test Case

Creating a Test Case allows you to define a complete testing scenario inside a project. A Test Case contains metadata (such as priority and assignment) and a sequence of ordered steps that describe how the scenario should be executed and validated.

Why it matters

• Organization: Keeps testing structured and traceable.
• Ownership: Assigns responsibility to a team member.
• Execution clarity: Defines how and where the test will run.

When to use it

• You want to validate a new feature or API flow.
• A bug fix needs regression coverage.
• A backend scenario requires multiple ordered API calls.
• You want to combine manual and automated checks in one scenario.

Core concepts

• Test Case – a structured scenario composed of ordered steps.
• Execution Source – determines how the test runs (Manual, Server, Smart Agent).
• Metadata Fields – category, priority, group, assignment, and tags.

How it works

1. You create a new Test Case inside the active project.
2. You define its metadata and execution source.
3. You save the Test Case.
4. You add steps to define the testing logic.

How to use it

Step 1: Open the Add New Test Case page

Navigate to Test Cases → Add New Test Case within the active project.

Step 2: Fill in the basic information

• Title
  A clear and descriptive name of the scenario.

• Description
  Explain what this test validates and why it exists.

• Preconditions
  Any setup required before execution.

• Assign To
  Optional – assign responsibility to a team member.

• Category / Priority / Group
  Optional classification fields to help filter and organize.

• Tags
  Comma-separated keywords for search and filtering.

• Bug Link
  Optional reference to an issue tracker item.

Step 3: Choose Execution Source

Select how this Test Case will run:

• Manual – Steps are updated manually.
• Server – APIs execute directly from the backend.
• Smart Agent – Execution happens via the local agent environment.

Step 4: Save the Test Case

• You can add and modify steps dynamically before saving the Test Case.
• However, none of the steps are permanently stored until you click Create (Save).

Best practices

• Use descriptive titles that explain the scenario clearly.
• Keep one logical flow per Test Case.
• Set the execution source intentionally (do not leave default without review).
• Link related bug tickets for traceability.

Common mistakes

❌ Mistake 1: Creating overly generic titles (e.g., “Test API”)
✔ Fix: Use clear scenario-driven names (e.g., “User Login – Valid Credentials”).

❌ Mistake 2: Choosing the wrong execution source
✔ Fix: Decide early whether the test should run manually or through API execution.

Security & permissions

• Test Cases are scoped to the active project.
• Only authorized users can create or modify Test Cases.
• Execution permissions depend on project roles.

Related documentation

• Test Cases Overview
• Test Steps Fundamentals
• Using APIs in Test Steps
• Action API vs Expected API