write-canary-tests

Included with Lifetime

$97 forever

Write correct test blocks and assertions for Mission Control canary health checks. Use when creating canaries that need pass/fail conditions, adding test expressions, or writing assertions based on HTTP status, JSON response, exec output, or Kubernetes health.

Cloud & DevOps

What this skill does


# Write Canary Tests

## Goal

Write correct `test` blocks for canary checks.

---

## Golden Rules

- The test result must be boolean (`true` / `false`).
- Use null-safe access for optional fields (`.?` + `orValue(...)`).
- Tests add assertions; they do not bypass built-in check failures.

---

## Test Fields

| Field        | Description                                             | Example                              |
| ------------ | ------------------------------------------------------- | ------------------------------------ |
| `expr`       | CEL expression that evaluates to boolean                | `code == 200 && json.status == 'ok'` |
| `javascript` | JavaScript expression/script returning `true` / `false` | `code === 200`                       |
| `template`   | Go template rendering `true` / `false`                  | `{{ eq .code 200 }}`                 |

---

## Common Test Context

> Exact fields vary by check type.

| Variable              | Description                                     | Example                            |
| --------------------- | ----------------------------------------------- | ---------------------------------- |
| `results`             | Primary result payload for many check types     | `size(results) > 0`                |
| `code`                | HTTP status code (HTTP checks)                  | `code in [200, 201, 301]`          |
| `json`                | Parsed JSON response body (HTTP checks)         | `json.headers['User-Agent'] != ''` |
| `headers`             | HTTP response headers                           | `'Content-Type' in headers.keys()` |
| `sslAge`              | SSL validity duration (HTTP TLS checks)         | `sslAge > Duration('7d')`          |
| `outputs.<checkName>` | Previous named check outputs (with `dependsOn`) | `outputs.getUuid.json.uuid != ''`  |
| `check`               | Current check metadata                          | `check.name != ''`                 |
| `canary`              | Current canary metadata                         | `canary.namespace == 'prod'`       |

---

## Canonical Snippets

### 1) HTTP status + JSON assertion

```yaml
test:
  expr: "code == 200 && json.uuid != ''"
```

### 2) HTTP header assertion

```yaml
test:
  expr: "! ('Authorization' in headers.keys())"
```

### 3) Exec stdout assertion

```yaml
test:
  expr: 'results.stdout == "hello"'
```

### 4) Kubernetes health assertion

```yaml
test:
  expr: dyn(results).all(x, k8s.isHealthy(x))
```

### 5) JUnit summary assertion

```yaml
test:
  expr: results.failed == 0 && results.passed > 0
```

### 6) dependsOn output assertion

```yaml
test:
  expr: "code == 200 && outputs.getUuid.json.uuid != ''"
```

### 7) Nil-safe list check

```yaml
test:
  expr: results.?files.orValue([]).size() > 0
```

---

## References

- Canary Checker spec reference:
  https://flanksource.com/docs/reference/canary-checker/llms.txt

Files: 1

Size: 3.1 KB

Complexity: 8/100

Category: Cloud & DevOps

Source: https://github.com/flanksource/claude-code-plugin/tree/main/skills/write-canary-tests

Related in Cloud & DevOps

appbuilder-action-scaffolder

Included

Create, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.

Cloud & DevOpsscripts

orchestrating-datacloud

Included

Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).

Cloud & DevOpsscripts

github-project-automation

Included

Automate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error

Cloud & DevOpsscripts

sf-datacloud

Included

Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).

Cloud & DevOpsscripts

fabric-cli

Included

Use this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.

Cloud & DevOpsscripts

lark

Included

Lark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.

Cloud & DevOpsscripts