Test Cases · Schema

TestStep

A single executable step within a test case, defining an action to perform and the expected result.

API TestingAutomationQuality AssuranceSoftware DevelopmentSoftware TestingTesting

Properties

Name Type Description
id string Unique identifier for the test step.
test_case_id string Identifier of the parent test case this step belongs to.
step_number integer Ordinal position of this step within the test case.
action string The specific action to perform during this test step.
test_data string Input data or test values to use when performing the action.
expected_result string The expected outcome after performing the action.
actual_result string The actual observed result when the step was executed.
status string Execution status of the test step.
notes string Additional notes or observations recorded during step execution.
screenshot_url string URL to a screenshot or evidence captured during step execution.
View JSON Schema on GitHub

JSON Schema

test-cases-test-step-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/test-cases/refs/heads/main/json-schema/test-cases-test-step-schema.json",
  "title": "TestStep",
  "description": "A single executable step within a test case, defining an action to perform and the expected result.",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Unique identifier for the test step."
    },
    "test_case_id": {
      "type": "string",
      "description": "Identifier of the parent test case this step belongs to."
    },
    "step_number": {
      "type": "integer",
      "minimum": 1,
      "description": "Ordinal position of this step within the test case."
    },
    "action": {
      "type": "string",
      "description": "The specific action to perform during this test step."
    },
    "test_data": {
      "type": "string",
      "description": "Input data or test values to use when performing the action."
    },
    "expected_result": {
      "type": "string",
      "description": "The expected outcome after performing the action."
    },
    "actual_result": {
      "type": "string",
      "description": "The actual observed result when the step was executed."
    },
    "status": {
      "type": "string",
      "enum": ["not-executed", "passed", "failed", "blocked", "skipped"],
      "description": "Execution status of the test step."
    },
    "notes": {
      "type": "string",
      "description": "Additional notes or observations recorded during step execution."
    },
    "screenshot_url": {
      "type": "string",
      "format": "uri",
      "description": "URL to a screenshot or evidence captured during step execution."
    }
  },
  "required": ["step_number", "action", "expected_result"]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/test-cases-test-step"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.