testing

Name: testing
Availability: InStock
Author: AsiaOstrich

Define software testing strategies using pyramid and ISTQB frameworks with coverage targets.

70|13|Updated Dec 24, 2025

Search Tags:#testing #integration test #unit test #e2e test #coverage #test pyramid #istqb

Ready to run

npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill testing-asiaostrich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/AsiaOstrich/universal-dev-standards/tree/main/locales/zh-CN/skills/testing-guide
Command: npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill testing-asiaostrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance on the testing pyramid and best practices for writing effective tests, ensuring robust software quality.

Core Features & Use Cases

Testing Pyramid Standards: Understand and apply the industry-standard testing pyramid (UT, IT, E2E) or the ISTQB framework.
Coverage Goals: Define and track essential code coverage metrics (line, branch, function).
Naming Conventions: Implement clear and consistent naming for test files and methods.
Use Case: When starting a new feature, use this Skill to define the appropriate testing strategy and coverage targets, ensuring all levels of testing are considered from the outset.

Quick Start

Use the testing skill to understand the testing pyramid and its coverage goals.

Frequently Asked Questions about testing

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

FAQPage Schema

What is the testing pyramid and how does it structure unit, integration, and e2e tests?▼

The testing pyramid structures software tests by prioritizing a broad base of unit tests, fewer integration tests, and a minimal set of end-to-end tests. This framework optimizes execution speed and coverage reliability across system levels.

How do I set code coverage targets for line, branch, and function metrics?▼

Define code coverage targets by tracking line, branch, and function metrics to ensure comprehensive test paths. Establishing clear thresholds for each metric prevents gaps in test execution and maintains industry quality benchmarks.

What are the best naming conventions for test files and methods?▼

Effective naming conventions for test files and methods implement clear, consistent identifiers reflecting the tested scenario. Applying standardized naming across unit and integration tests avoids anti-patterns and improves maintainability.

Does this testing strategy follow the ISTQB framework standards?▼

Yes, the testing strategy explicitly maps to ISTQB framework standards. It details unit, integration, system, and end-to-end testing levels, ensuring adherence to recognized industry quality benchmarks and structured test development.

When starting a new feature, how do I define an appropriate testing strategy?▼

To define an appropriate testing strategy for a new feature, apply the testing pyramid standards to balance unit, integration, and e2e tests. Set coverage goals early to ensure all testing levels are considered from the outset.