Test Cases · Schema

TestResult

The outcome of executing a test case, capturing pass/fail status, execution details, and any defects found.

API TestingAutomationQuality AssuranceSoftware DevelopmentSoftware TestingTesting

Properties

Name Type Description
id string Unique identifier for the test result.
test_case_id string Identifier of the test case that was executed.
test_run_id string Identifier of the test run this result belongs to.
status string Overall pass/fail status of the test case execution.
executed_by string Username or identifier of the person or system that executed the test.
executed_at string ISO 8601 timestamp when the test was executed.
duration_ms integer Time taken to execute the test case in milliseconds.
environment string The environment in which the test was executed (e.g., staging, production).
build_version string Software build version under test when this result was recorded.
defects array List of defect or bug identifiers found during this test execution.
comment string Tester comments or observations about the test execution.
step_results array Results for each individual step within the test case.
View JSON Schema on GitHub

JSON Schema

test-cases-test-result-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-result-schema.json",
  "title": "TestResult",
  "description": "The outcome of executing a test case, capturing pass/fail status, execution details, and any defects found.",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Unique identifier for the test result."
    },
    "test_case_id": {
      "type": "string",
      "description": "Identifier of the test case that was executed."
    },
    "test_run_id": {
      "type": "string",
      "description": "Identifier of the test run this result belongs to."
    },
    "status": {
      "type": "string",
      "enum": ["passed", "failed", "blocked", "skipped", "error"],
      "description": "Overall pass/fail status of the test case execution."
    },
    "executed_by": {
      "type": "string",
      "description": "Username or identifier of the person or system that executed the test."
    },
    "executed_at": {
      "type": "string",
      "format": "date-time",
      "description": "ISO 8601 timestamp when the test was executed."
    },
    "duration_ms": {
      "type": "integer",
      "minimum": 0,
      "description": "Time taken to execute the test case in milliseconds."
    },
    "environment": {
      "type": "string",
      "description": "The environment in which the test was executed (e.g., staging, production)."
    },
    "build_version": {
      "type": "string",
      "description": "Software build version under test when this result was recorded."
    },
    "defects": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of defect or bug identifiers found during this test execution."
    },
    "comment": {
      "type": "string",
      "description": "Tester comments or observations about the test execution."
    },
    "step_results": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/StepResult"
      },
      "description": "Results for each individual step within the test case."
    }
  },
  "required": ["id", "test_case_id", "status", "executed_at"],
  "$defs": {
    "StepResult": {
      "type": "object",
      "properties": {
        "step_number": {
          "type": "integer",
          "description": "The step number this result corresponds to."
        },
        "status": {
          "type": "string",
          "enum": ["passed", "failed", "blocked", "skipped"],
          "description": "Status of this individual step."
        },
        "actual_result": {
          "type": "string",
          "description": "The actual result observed for this step."
        }
      },
      "required": ["step_number", "status"]
    }
  }
}

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-result"
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.