skills.rest
Bottelet
BotteletCOMMUNITY
Explore all skills by this author →
𝕏@cbotteletGitHub

pest-control

Detect and remove Pest references from codebases to enforce PHPUnit-only testing.

2.3k|769|Updated Jan 14, 2016
Search Tags:#migration#Pest#PHPUnit#code cleanup#test enforcement
One-click install
npx skills add https://github.com/Bottelet/DaybydayCRM --skill pest-control
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pest-control
Source: https://github.com/Bottelet/DaybydayCRM/tree/main/.claude/skills/pest-control
Command: npx skills add https://github.com/Bottelet/DaybydayCRM --skill pest-control

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that a project adheres to PHPUnit-only testing, eliminating the use of Pest and enforcing best practices for test structure and assertion style.

Core Features & Use Cases

  • PHPUnit Enforcement: Automatically scans and eliminates Pest references from code, config, and documentation.
  • Rule Compliance: Provides guidelines for test class patterns, attribute syntax, assertion style, and file placement.
  • Conversion Reference: Offers a comprehensive mapping from Pest to PHPUnit syntax for easy conversion.
  • Use Case: When migrating a project from Pest to PHPUnit, this Skill automates the cleanup process and enforces the new testing standards.

Quick Start

Use the pest-control skill to scan the current project directory for Pest references and remove them.

Frequently Asked Questions about pest-control

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

FAQPage Schema
How do I remove Pest references and enforce PHPUnit-only testing in my codebase?▼

Migrating from Pest to PHPUnit involves scanning your project for Pest-specific syntax and replacing it with PHPUnit equivalents. A conversion reference mapping helps automate this cleanup process while enforcing new testing standards for file placement and attributes.

What is the process for migrating a project from Pest to PHPUnit?▼

Migrating from Pest to PHPUnit involves scanning your project for Pest-specific syntax and replacing it with PHPUnit equivalents. A conversion reference mapping helps automate this cleanup process while enforcing new testing standards for file placement and attributes.

Does PHPUnit enforcement scan configuration files and documentation for Pest syntax?▼

When converting Pest tests to PHPUnit, you need guidelines for test class patterns, attribute syntax, assertion style, and file placement. A comprehensive syntax mapping from Pest to PHPUnit provides the necessary reference for accurate and standard-compliant conversion.

What conversion rules apply when replacing Pest test syntax with PHPUnit standards?▼

When converting Pest tests to PHPUnit, you need guidelines for test class patterns, attribute syntax, assertion style, and file placement. A comprehensive syntax mapping from Pest to PHPUnit provides the necessary reference for accurate and standard-compliant conversion.

Why should I use automated elimination for Pest references instead of manual code cleanup?▼

Automated Pest elimination ensures comprehensive detection across source code and configurations that manual cleanup might miss. It enforces strict adherence to PHPUnit testing standards consistently, reducing human error during migration and guaranteeing best practices for test structure.

Related Skills

Explore More Software Engineering Skills→
y-l-gy-l-g
3

pest-testing

Convert PHPUnit tests to Pest syntax for Laravel projects.

Community
Advanced
nashgaonashgao
3

test unit

Execute unit tests across Jest, pytest, Go, PHPUnit, and RSpec.

Community
Advanced
MatthieuszMatthieusz

coding-standards

Validate TypeScript code against predefined coding standards using static analysis tools.

Community
Advanced
DevanBDevanB

Testing Test Writing

Fill gaps in Pest test coverage for Laravel user workflows.

Community
Basic