Skip to content
Skills Library
DevOps & cloud · Planning

testing-for-reliability

/testing-for-reliability

Build a reliability testing strategy: unit→integration→canary→fault injection→DR, plus emergent agentic testing themes from SRE Book 2e. Use when improving test strategy for production confidence.

Licence
MIT
Last repository change
30.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build a reliability testing strategy: unit→integration→canary→fault injection→DR, plus emergent agentic testing themes from SRE Book 2e. Use when improving test strategy for production confidence.

Original author description

Build a reliability testing strategy: unit→integration→canary→fault injection→DR, plus emergent agentic testing themes from SRE Book 2e. Use when improving test strategy for production confidence.

How it works

  1. When to use
  2. Principles
  3. Workflow
  4. Decision guide
  5. Output template
  6. Anti-patterns
  7. Related skills
  8. Canonical references
  9. Agent notes
Original SKILL.md headings · 60 lines, 212 words
SKILL.md preview
---
name: testing-for-reliability
description: >-
  Build a reliability testing strategy: unit→integration→canary→fault injection→DR, plus emergent agentic testing themes from SRE Book 2e. Use when improving test strategy for production confidence.
---

# Testing For Reliability

**Domain:** `delivery`  
**Sources:** SRE Book 1e Ch17, SRE Book 2e Ch14

## When to use

- Strengthening release confidence
- Introducing chaos/fault injection
- Emergency rollout testing gaps

## Principles

- Tests reduce uncertainty; they do not create certainty.
- Production-like environments and progressive delivery catch what labs miss.
- Fault injection finds cascade and degrade bugs traditional tests miss.
- Test the emergency path (rollback, flag off) regularly.

## Workflow

1. Map riskiest failure modes → missing tests.
2. Ensure critical CUJ integration coverage.
3. Add canary metrics as production tests.
4. Pilot fault injection in nonprod then limited prod blast radius.
5. Schedule DR / restore / failover tests.

## Decision guide

- If only unit tests gate prod → raise bar for critical services.

## Output template

```markdown
# Reliability test plan
- Critical risks:
- Current coverage gaps:
- New tests / fault drills:
- Cadence:
```

## Anti-patterns

- Chaos without observability or abort.
- Never testing rollback.

## Related skills

`canarying-releases`, `disaster-planning`, `designing-for-resilience`

## Canonical references

- [Testing for Reliability](https://sre.google/sre-book/testing-for-reliability/)

## Agent notes

- Prefer live data (metrics, tickets, pages) over generic advice.
- Cite which Google SRE source informed a recommendation when useful.
- Keep outputs tactical: decisions, owners, next actions.
Files in this package (2)
  • SKILL.md 2 KB
  • reference.md 1 KB

Versions

The database has no other skills named testing-for-reliability.

Database snapshot: 13.11.2026 · package version 66b4e8a4f0f7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91sre-reliability-engineering
    Use when building reliable and scalable distributed systems.
  • 95sre
    Act as a responsible, experienced Site Reliability Engineer, grounded in Google's "Site Reliability Engineering" book, "The Site Reliability Workbook" and LinkedIn's School of SRE. Use whenever the user does reliability or production-operations work — SLIs/SLOs/error budgets,…
  • 100testing-strategy
    Formulates a comprehensive testing strategy (Pyramid vs Trophy) and selects appropriate tools. Use when: test plan, testing strategy, qa strategy, e2e testing, integration testing, contract testing.
  • 100engineering-sre
    Use when Codex should act as the SRE (Site Reliability Engineer) specialist from Agency Agents. Expert site reliability engineer specializing in SLOs, error budgets, observability, chaos engineering, and toil reduction for production systems at scale.
  • 95qa-strategy
    Testing strategy and QA patterns. Use for test pyramid design, E2E test architecture, test automation frameworks, performance testing, and bug triage processes.
  • 90reliability-sre
    Apply SRE principles (SLO, Error Budget, Chaos Engineering). Use when: sre, reliability, slo, sli, error budget, chaos engineering, postmortem, incident, oncall.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.