skills.rest
SapanPatibandha
SapanPatibandhaCOMMUNITY
Explore all skills by this author →
GitHub

testing-standards

Standardize testing practices for Incident Management AI services with layered strategies and coverage thresholds.

Updated Mar 6, 2026
Search Tags:#vitest#testing#standards#playwright#integration-tests#incident-management
One-click install
npx skills add https://github.com/SapanPatibandha/IncidentManagementAI --skill testing-standards-sapanpatibandha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-standards
Source: https://github.com/SapanPatibandha/IncidentManagementAI/tree/main/.claude/skills/testing-standards
Command: npx skills add https://github.com/SapanPatibandha/IncidentManagementAI --skill testing-standards-sapanpatibandha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes and enforces a unified testing strategy for Incident Management AI services, ensuring consistent quality, coverage and patterns across backend, frontend, API, and E2E tests.

Core Features & Use Cases

  • Authoritative reference for unit, integration, API, and E2E tests.
  • Defines test layers, thresholds, and naming conventions to improve onboarding and auditing.
  • Provides concrete patterns and examples to guide writing tests across services.

Quick Start

Start by reading this standard and apply its patterns to all unit, integration, and E2E tests you write.

Frequently Asked Questions about testing-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are testing standards for Incident Management AI services?▼

Testing standards for Incident Management AI enforce consistent, auditable quality by standardizing frontmatter metadata, coverage thresholds, layered test strategies, and structured test file naming across backend aggregates, API layers, frontend components, and end-to-end flows.

How do I structure unit and integration tests using Vitest and Playwright?▼

You structure Vitest and Playwright tests using defined test layers and structured file naming conventions, applying concrete example patterns to validate correctness, performance, and coverage within your CI pipelines.

Does this testing standard work for both frontend components and backend command handlers?▼

Yes, this testing standard applies to both frontend components and backend command handlers, ensuring unified testing practices and consistent quality across all service layers.

What's the best way to enforce coverage thresholds and naming conventions in CI pipelines?▼

The best way to enforce coverage thresholds and naming conventions is by applying frontmatter-based metadata and layered test strategies to validate correctness and coverage directly within your CI pipelines.

Why do I need frontmatter-based metadata in my test files?▼

Frontmatter-based metadata is needed to ensure consistent, auditable quality across Incident Management AI services, improving onboarding and auditing by standardizing test file documentation and patterns.

Related Skills

Explore More Software Engineering Skills→
The13thNodeThe13thNode
3

test-automation

Generate unit, integration, and end-to-end test suites for JavaScript/TypeScript projects.

Community
Advanced
mrigsbymrigsby

Code Coverage Testing

Analyze code coverage in CFML and BoxLang applications.

Community
Advanced
eventua11yeventua11y
1

writing-tests

Automate E2E and unit test setup and execution with Playwright and Vitest.

Official
Intermediate
unclenateunclenate
3

harness-testing

Validate PR test coverage against declared thresholds and test strategy documents.

Community
Intermediate