testing

Enforce standardized testing workflows with Vitest 4 and coverage verification.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill testing-gerald-ica
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/gerald-ica/opencode-config-snapshot/tree/main/opencode/skills/testing
Command: npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill testing-gerald-ica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a clear, repeatable standard for creating and validating tests to improve software quality and reduce regression risks.

Core Features & Use Cases

  • Defines a structured approach for unit, integration, regression, and end-to-end testing.
  • Guides risk-based test planning, writing clear test cases, and maintaining test coverage across features.
  • Use Case: when adding a new feature, attach tests and update existing tests to preserve coverage, enabling reliable releases.

Quick Start

Run the configured test suite to validate new or updated code and verify coverage before merging.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I enforce a standardized testing workflow for Vitest 4?

Enforce a standardized testing workflow for Vitest 4 by applying policy-driven rules for risk-based planning, execution, and coverage verification across unit and integration tests.

What's the best way to structure unit and integration tests when adding new features?

The best way to structure tests when adding features is using a defined test structure that guides risk-based planning, attaches tests to new code, and updates existing tests to preserve coverage.

How does risk-based test planning improve software quality?

Risk-based test planning improves software quality by establishing a repeatable standard for creating and validating tests, which systematically reduces regression risks and software defects.

Can I use this workflow to verify test coverage before merging code?

Yes, you can verify test coverage before merging by running the configured test suite to validate new or updated code, ensuring reliable releases through coverage verification.

Does the testing workflow support end-to-end and regression testing?

Yes, the testing workflow supports end-to-end and regression testing by defining a structured approach that covers unit, integration, regression, and end-to-end testing scenarios.

When do I need a policy-driven workflow for test planning?

You need a policy-driven workflow for test planning when tests are added, updated, or required for completion, ensuring standardized execution and coverage verification across features.