Http Assertions (http-assertions)
Summary
List of HTTP monitors (method, headers, body) asserting status, header contains/not-contains and body contains/not-contains; alerts after N failed runs in a row (default 2).
Classification
- Category:
API_HEALTH - Plugin id:
http-assertions - Version:
1.0.0 - Target types:
WEBSITE,WEBSHOP,API - Weight class:
LIGHT - Risk level: not set on plugin object
- Browser required: No (HTTP / Node / other — see source)
- Tier / group: Tier 4 — API
Schedule
- scheduleHints:
{ defaultInterval: '*/5 * * * *', priority: 9 } - Prerequisites: None declared on this plugin.
Configurable inputs
Public keys are derived from inputSchema: z.object({ ... }) (underscore-prefixed keys are runtime-only and omitted here).
| Field | Notes |
|---|---|
| (none) | This plugin uses an empty z.object({}) or only internal wrappers — see inputSchema in the source file. |
Runtime / injected config
_priorRunMetrics— the last completed run's metrics (readsPriorRunMetrics);monitorStateholds each monitor's consecutive-failure count, so a finding is raised only afterfailuresBeforeAlertfailed runs in a row._secrets— target secrets substituted for{{secret:NAME}}in monitor header values and string bodies; redacted from evidence.- Config:
monitors(JSON list, required; seehttpMonitorSchemain the source),failuresBeforeAlert(default 2),timeoutMs(default 10000).
What it does
- Runs as part of the worker test execution pipeline; results become
Runrows and may createFindingrecords. - List of HTTP monitors (method, headers, body) asserting status, header contains/not-contains and body contains/not-contains; alerts after N failed runs in a row (default 2).
- For finding titles, metrics, and artifacts specific to this plugin, refer to the implementation linked below.
Source
packages/test-plugins/src/plugins/http-assertions.ts