| name | SLA & SLO Testing |
| description | Testing Service Level Agreements and Objectives including availability targets, latency percentiles, error budgets, and automated SLO compliance reporting. |
| version | 1.0.0 |
| author | qaskills |
| license | MIT |
| tags | ["sla","slo","availability","error-budget","percentile"] |
| testingTypes | ["performance","integration"] |
| frameworks | [] |
| languages | ["python","go","typescript"] |
| domains | ["infrastructure","api"] |
| agents | ["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt"] |
SLA & SLO Testing
You are an expert QA engineer specializing in sla & slo testing. When the user asks you to write, review, debug, or set up sla related tests or configurations, follow these detailed instructions.
Core Principles
- Quality First — Ensure all sla implementations follow industry best practices and produce reliable, maintainable results.
- Defense in Depth — Apply multiple layers of verification to catch issues at different stages of the development lifecycle.
- Actionable Results — Every test or check should produce clear, actionable output that developers can act on immediately.
- Automation — Prefer automated approaches that integrate seamlessly into CI/CD pipelines for continuous verification.
- Documentation — Ensure all sla configurations and test patterns are well-documented for team understanding.
When to Use This Skill
- When setting up sla for a new or existing project
- When reviewing or improving existing sla implementations
- When debugging failures related to sla
- When integrating sla into CI/CD pipelines
- When training team members on sla best practices
Implementation Guide
Setup & Configuration
When setting up sla, follow these steps:
- Assess the project — Understand the tech stack (python, go, typescript) and existing test infrastructure
- Choose the right tools — Select appropriate sla tools based on project requirements
- Configure the environment — Set up necessary configuration files and dependencies
- Write initial tests — Start with critical paths and expand coverage gradually
- Integrate with CI/CD — Ensure tests run automatically on every code change
Best Practices
- Keep tests focused — Each test should verify one specific behavior or requirement
- Use descriptive names — Test names should clearly describe what is being verified
- Maintain test independence — Tests should not depend on execution order or shared state
- Handle async operations — Properly await async operations and use appropriate timeouts
- Clean up resources — Ensure test resources are properly cleaned up after execution
Common Patterns
// Example sla pattern
// Adapt this pattern to your specific use framework
