Test Case

Overview

A test case validates one endpoint behavior (functional outcomes, schema correctness, and contract expectations). Test cases are designed to be:

• fast to create (no-code)
• easy to repeat across environments
• clear to debug when failures happen

Create a test case (no-code)

Typically you will:

1. Select an endpoint.
2. Choose Create test case.
3. Configure:
   • inputs (params, headers, request body)
   • expected status codes and response shape
4. Save and run the test once to validate connectivity and auth.

Parameterize inputs

Parameterization keeps tests reusable and CI-friendly:

• store tokens, base URLs, and IDs as variables
• reuse variable sets per environment
• generate unique values per run to avoid collisions

Related: Test configuration and Configuration fundamentals.

Assertions and validations

Good baseline assertions include:

• status code validation
• required headers
• schema validation (JSON/XML)
• business-rule checks for key fields

Use conditional assertions when behavior varies by feature flag, role, or environment.

AI-generated suggestions (optional)

Total Shift Left can suggest additional cases (edge cases, invalid values, boundary conditions) to expand coverage faster.

Related: AI-generated tests.

Best practices

• Start with read-only endpoints: stabilize auth + environment before write flows.
• Keep tests deterministic: minimize dependency on existing data.
• Prefer clear failures: assert only what matters for the contract and business outcomes.

Related articles

• Endpoint management
• Test run
• Test run pack