quality-assurance

Define testing strategies with pyramid principles and 90% code coverage.

1|2|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/SEBAKHI/Auth --skill quality-assurance-sebakhi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-assurance
Source: https://github.com/SEBAKHI/Auth/tree/main/.claude/skills/quality-assurance
Command: npx skills add https://github.com/SEBAKHI/Auth --skill quality-assurance-sebakhi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of ensuring high-quality, reliable software by providing comprehensive guidance on testing strategies, standards, and coverage requirements.

Core Features & Use Cases

  • Testing Pyramid Guidance: Understand and implement the optimal distribution of unit, integration, and end-to-end tests.
  • Test Quality Standards: Adhere to best practices for writing clear, focused, and well-named tests.
  • Code Coverage Enforcement: Mandate and achieve a minimum of 90% code coverage across all layers of the application.
  • Use Case: When starting a new feature, use this Skill to define the testing strategy, ensuring all critical paths are covered by appropriate test types and that the codebase meets the minimum coverage threshold before deployment.

Quick Start

Ensure all new code adheres to the 90% code coverage requirement and follows the testing pyramid principles.

Frequently Asked Questions about quality-assurance

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

FAQPage Schema
What is the testing pyramid and how does it structure quality assurance?

Code coverage requirements mandate a minimum 90% threshold across all application layers. Enforcing this standard before deployment ensures critical paths are fully tested and adherence to best practices for maintaining high code quality.

How do I write unit and integration tests that follow best practices?

Writing unit and integration tests that follow best practices requires focusing on clear, well-named, and targeted tests. Adhering to specific naming conventions and testing standards ensures tests remain focused on critical paths without becoming brittle.

What's the best way to define a testing strategy for a new feature?

Defining a testing strategy for a new feature involves applying testing pyramid principles to distribute unit, integration, and e2e tests appropriately. This approach ensures all critical paths are covered and the codebase meets the minimum coverage threshold.

When should I use e2e tests instead of unit or integration tests?

E2e tests should be used sparingly at the top of the testing pyramid instead of unit or integration tests when verifying complete application workflows. Reserving them for critical paths prevents slow test suites while ensuring end-to-end reliability.

Does this quality assurance guidance require specific testing frameworks?

This quality assurance guidance does not require specific testing frameworks. It provides framework-agnostic guidelines for testing strategies, naming conventions, and code coverage thresholds, ensuring best practices are applied regardless of the underlying tools.