testing-standards

Define software testing standards mandating Test-Driven Development and test writing best practices.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/george-popescu/bee-dev --skill testing-standards-george-popescu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-standards
Source: https://github.com/george-popescu/bee-dev/tree/main/plugins/bee/skills/standards/testing
Command: npx skills add https://github.com/george-popescu/bee-dev --skill testing-standards-george-popescu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes and enforces rigorous testing standards to ensure code quality, reliability, and maintainability across all development phases.

Core Features & Use Cases

  • Mandatory TDD: Enforces the Red-Green-Refactor cycle for all implementation tasks.
  • Test Writing Guidelines: Provides clear rules for test quantity, focus, structure (AAA), and adherence to acceptance criteria.
  • Naming Conventions: Defines best practices for naming tests in PHP (Pest) and JavaScript/TypeScript (Vitest).
  • Mocking Strategy: Guides developers on what to mock, what not to mock, and the preference for fakes over mocks.
  • Test Data Management: Recommends using factories for consistent and maintainable test data.
  • Gap Analysis: Outlines a process for identifying and addressing test coverage gaps after initial TDD.
  • Organization: Suggests clear directory structures for tests in both PHP and JavaScript projects.

Quick Start

Ensure all new code adheres to the mandatory TDD cycle and test writing standards.

Frequently Asked Questions about testing-standards

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

FAQPage Schema
How do I enforce Test-Driven Development standards across my software engineering team?

Test-Driven Development standards are enforced by mandating the Red-Green-Refactor cycle for all implementation tasks, ensuring code quality and maintainability. This approach requires structured testing methodologies and adherence to acceptance criteria.

What are the best practices for structuring test data and mocking in automated tests?

Best practices for test data and mocking involve using factories for consistent data management and preferring fakes over mocks. This strategy guides developers on what to mock and what to avoid, promoting reliable and maintainable tests.

How do I define naming conventions for tests in PHP and JavaScript projects?

Naming conventions for tests in PHP and JavaScript are defined by following specific best practices for Pest and Vitest frameworks. These standards ensure test clarity and maintainability across different technology stacks.

What is the process for identifying test coverage gaps after initial TDD?

Identifying test coverage gaps after initial TDD involves a structured gap analysis process to address missing test scenarios. This methodology ensures comprehensive coverage and adherence to acceptance criteria after the Red-Green-Refactor cycle.

Does this testing methodology work for both PHP and JavaScript environments?

This testing methodology works for both PHP and JavaScript environments by providing clear directory structures and test writing guidelines tailored for Pest and Vitest. It ensures maintainable code across different platforms.

When should I use AAA structure and acceptance criteria in test writing?

The AAA structure and acceptance criteria should be used in all test writing to ensure proper focus, quantity, and structure. This guarantees that tests are reliable and adhere to defined software testing standards.