skills.rest
epologee
epologeeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

testing-philosophy

Enforce test-driven development with failing specs before implementation.

3|1|Updated Apr 4, 2026
Search Tags:#testing#tdd#rspec#cucumber#ci#flaky-tests#test-strategy
One-click install
npx skills add https://github.com/epologee/leclause-skills --skill testing-philosophy-epologee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-philosophy
Source: https://github.com/epologee/leclause-skills/tree/main/packages/testing-philosophy/skills/testing-philosophy
Command: npx skills add https://github.com/epologee/leclause-skills --skill testing-philosophy-epologee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, enforceable testing discipline to prevent ambiguous "works-for-me" outcomes, reduce flaky tests, and ensure the main branch remains reliably green by specifying desired behavior before implementation.

Core Features & Use Cases

  • TDD Workflow Enforcement: Mandates red→green→refactor, writing failing specs first for features, bug fixes, and interface changes.
  • Cucumber/Gherkin Guidance: Prescribes domain-focused feature files for UI/UX bugs and keeps step definitions responsible for UI mechanics.
  • Flaky Test Triage & Suite Health: Defines how to investigate flaky specs, gather context (command, failure output, failure rate), and prioritize remediation to restore trust in the suite.
  • Use Case: When a CI job fails intermittently, follow the flaky-test procedure to collect failure context, propose a dedicated investigation, and prevent masking with retries.

Quick Start

Write a failing spec that reproduces the desired behavior or bug, implement the minimal change to make it pass, then refactor while keeping the entire suite green.

Frequently Asked Questions about testing-philosophy

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

FAQPage Schema
How do I enforce TDD discipline in my RSpec workflow?▼

To enforce TDD discipline with RSpec, mandate a red-green-refactor cycle by writing failing specs first to define desired behavior, then implementing the minimal change to pass, and finally refactoring while keeping the suite green.

What's the best way to triage flaky tests in a CI pipeline?▼

Triage flaky tests in CI by gathering context including the failure command, output, and failure rate, then proposing a dedicated investigation to remediate the root cause and prevent masking the issue with retries.

When do I need Cucumber and Gherkin feature files for testing?▼

Use Cucumber and Gherkin feature files for user-facing scenarios like UI/UX bugs, keeping domain-focused behavior specifications separate from step definitions that handle UI mechanics.

Does this test strategy work for full-stack backend applications?▼

This test strategy applies to backend and full-stack applications, enforcing explicit behavior specifications across unit and integration testing workflows to keep the main branch reliably green.

Why does writing failing specs before implementation matter?▼

Writing failing specs before implementation matters because it specifies desired behavior upfront, preventing ambiguous outcomes and ensuring the implementation directly addresses the defined requirements.

Related Skills

Explore More Software Engineering Skills→
reckerswartzreckerswartz

rspec

Assess Rails RSpec coverage gaps and generate strengthened specs.

Community
Advanced
Chachamaru127Chachamaru127
3.0k

verify

Verify builds, recover from errors, and apply review fixes across CI pipelines.

Community
Intermediate
CaptainCrouton89CaptainCrouton89
497

Testing Code

Automate software tests to verify functionality against acceptance criteria.

Community
Basic
luanrodriguesluanrodrigues
2

bee:dev-fuzz-testing

Execute mutation testing on PHP implementation files with Infection.

Community
Advanced