testing-guidelines

Name: testing-guidelines
Availability: InStock
Author: loagma

Enforce deterministic Vitest testing practices with centralized /tests organization.

Updated Feb 7, 2026

Search Tags:#planning #vitest #testing #qa #unit-tests #integration-tests #e2e-tests

Ready to run

npx skills add https://github.com/loagma/LoagmaPMS --skill testing-guidelines-loagma

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-guidelines
Source: https://github.com/loagma/LoagmaPMS/tree/main/.claude/skills/testing-guidelines
Command: npx skills add https://github.com/loagma/LoagmaPMS --skill testing-guidelines-loagma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Testing Guidelines provide a definitive framework to ensure all tests are real, do not pass by manipulation, and remain deterministic, maintainable, and auditable across a project.

Core Features & Use Cases

Enforces the Golden Rule: tests validate actual behavior and catch regressions, not just run.
Defines planning requirements: explicit test types, execution rules, coverage targets, edge cases, and performance criteria.
Guides test organization and tooling (Vitest-based) with centralized /tests location and AAA pattern.

Quick Start

Write and apply these guidelines when planning every test for a Vitest-based project; begin by creating a /tests directory and writing unit tests that cover core logic with deterministic inputs.

Frequently Asked Questions about testing-guidelines

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

FAQPage Schema

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

To structure deterministic unit and integration tests with Vitest, organize all tests in a centralized `/tests` directory and follow the AAA pattern. This ensures tests validate actual behavior and remain maintainable.

What should be included in software test planning to prevent tests from passing by manipulation?▼

Test planning must include explicit test types, execution rules, coverage targets, edge cases, and performance criteria. Defining these requirements prevents tests from passing by manipulation and ensures they catch actual regressions.

Can I use these testing guidelines to plan end-to-end and performance tests for my project?▼

Yes, you can use these guidelines to plan end-to-end and performance tests. The framework applies to unit, integration, component, e2e, performance, and security testing, ensuring deterministic and auditable validation across all test types.

What is the best way to enforce real testing practices across a software engineering team?▼

The best way to enforce real testing practices is to apply a definitive framework dictating test location, tooling, and execution rules. This ensures tests validate actual behavior and remain deterministic across the project.

Why do my tests pass but still fail to catch regressions in my codebase?▼

Tests pass but fail to catch regressions when they do not validate actual behavior and lack deterministic inputs. Applying strict validation standards and defining edge cases in your test planning ensures tests catch real regressions.