Test Result Normalize

quality.test_result_normalize

ProductionBounded custom (Class B)Deterministicstrictmoderatev1.0.0

No network

Overview

You send a published profile and a JSON payload. GENERIC_V1 reads suites and cases. JEST_JSON_V1 reads testResults and assertionResults. PYTEST_JSON_V1 reads tests. GO_TEST_JSON_V1 reads events. Status values become PASSED, FAILED, SKIPPED, ERROR, FLAKY or UNKNOWN. Stacks are capped at 16 KiB and secret-shaped assignments are redacted. This does not parse JUnit XML or run tests.

CI JSON reports disagree on status names; a published adapter turns them into one model.

Reliability

Stacks clip at 16384 characters and secret-shaped assignments become ***. TEST_RESULT_INVALID — trigger: a payload that does not match the profile; retryable: no; next: send the documented JSON shape. TEST_RESULT_LIMIT_EXCEEDED — trigger: more than 10000 cases or a payload over 10 MiB; retryable: no; next: split the report. TEST_RESULT_PROFILE_UNSUPPORTED — trigger: a profile outside the published set; retryable: no; next: send GENERIC_V1, JEST_JSON_V1, PYTEST_JSON_V1 or GO_TEST_JSON_V1.

Context footprint

Names, statuses and bounded snippets only. A successful call costs 2 execution credits.

When to use it

When a Jest, pytest, go test or generic JSON report must be normalized.

When the report is JUnit XML, or when tests still need running.

Scope

Note

Normalizes structured test JSON from a published adapter into suites, cases and totals.

Non-goals

Does not parse JUnit XML
Does not execute tests
Does not guess unknown vendor versions

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

analysis

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call2 credits

File handling

Accepts file_refProduces file_refMax input2 MB

How we handle your data

Sensitive processing

What this means

This skill is designed to detect, mask, redact, validate, or otherwise process sensitive data.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
Targets sensitive data
The response does not contain submitted content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
profile	string	Yes	Adapter that reads the payload: GENERIC_V1, JEST_JSON_V1, PYTEST_JSON_V1 or GO_TEST_JSON_V1.
payload	object	Yes	Purpose-bound vendor JSON object for the selected profile — unconstrained RFC 8259 JSON items bounded at 10 MiB serialized.

Output schema

Field	Type	Required	Description
profile	string	Yes	Adapter profile that was actually applied.
suites	array	Yes	Normalized suites in input order, 0 through 10000 closed {name, cases, tests, passed, failed, skipped, errors} objects.
totals	object	Yes	Closed aggregate counts across every suite, with durationMs JSON null when no case carried a duration.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"quality.test_result_normalize","input":{"profile":"GENERIC_V1","payload":{"suites":[{"name":"BillingSuite","cases":[{"name":"chargesInvoice","status":"PASSED","durationMs":12}]}]}}}'

Integrations

TypeScript SDK

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("quality.test_result_normalize", {"payload":{"suites":[{"name":"BillingSuite","cases":[{"name":"chargesInvoice","status":"PASSED","durationMs":12},{"name":"rejectsVoid","status":"FAILED","durationMs":4,"message":"expected 402"}]}]},"profile":"GENERIC_V1"});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.
TEST_RESULT_INVALID	400	No	The request payload failed this skill's input validation.
TEST_RESULT_LIMIT_EXCEEDED	429	No	A size, quota, rate, or time limit was exceeded.
TEST_RESULT_PROFILE_UNSUPPORTED	400	No	The skill does not support the requested variant.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not parse JUnit XML
Does not execute tests
Does not guess unknown vendor versions
Parsing Surefire XML
Running the test suite

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "quality.test_result_normalize",
  "input": {
    "payload": {
      "suites": [
        {
          "name": "BillingSuite",
          "cases": [
            {
              "name": "chargesInvoice",
              "status": "PASSED",
              "durationMs": 12
            },
            {
              "name": "rejectsVoid",
              "status": "FAILED",
              "durationMs": 4,
              "message": "expected 402"
            }
          ]
        }
      ]
    },
    "profile": "GENERIC_V1"
  }
}

Examples

A generic suite with one pass and one fail totals two tests

Inputjson

{
  "payload": {
    "suites": [
      {
        "name": "BillingSuite",
        "cases": [
          {
            "name": "chargesInvoice",
            "status": "PASSED",
            "durationMs": 12
          },
          {
            "name": "rejectsVoid",
            "status": "FAILED",
            "durationMs": 4,
            "message": "expected 402"
          }
        ]
      }
    ]
  },
  "profile": "GENERIC_V1"
}

Expected outputjson

{
  "profile": "GENERIC_V1",
  "suites": [
    {
      "name": "BillingSuite",
      "cases": [
        {
          "name": "chargesInvoice",
          "status": "PASSED",
          "durationMs": 12
        },
        {
          "name": "rejectsVoid",
          "status": "FAILED",
          "durationMs": 4,
          "message": "expected 402"
        }
      ],
      "tests": 2,
      "passed": 1,
      "failed": 1,
      "skipped": 0,
      "errors": 0
    }
  ],
  "totals": {
    "tests": 2,
    "passed": 1,
    "failed": 1,
    "skipped": 0,
    "errors": 0,
    "flaky": 0,
    "unknown": 0,
    "durationMs": 16
  }
}

Tip

Statuses stay PASSED and FAILED and totals.tests is 2.

A passed case with retries maps to FLAKY