Pest Testing

What it does

This skill, Pest Testing, automatically generates diverse and realistic user inputs to rigorously test application resilience against unexpected data and edge cases. It leverages the Pest testing framework for PHP applications, enabling you to create unit, feature, browser, smoke, visual regression, architecture, and other types of tests. The skill supports creating new tests, modifying existing ones, debugging failures, and enforcing code conventions.

When to use it

This skill is useful in these scenarios:

• Creating new unit, feature, or browser tests.
• Modifying existing tests within a PHP application using Pest.
• Debugging test failures.
• Performing smoke testing to quickly validate multiple pages.
• Writing architecture tests to enforce code conventions.
• Developing visual regression tests to compare screenshots for changes.

Key capabilities

• Supports various test types: unit, feature, browser, smoke, visual regression, and architecture tests.
• Integration with the Pest testing framework.
• Browser testing in real browsers (Chrome, Firefox, Safari).
• Support for device/viewport testing (e.g., iPhone 14 Pro, tablets).
• Ability to switch between color schemes (light/dark mode) during tests.
• Features like Event::fake() and assertions such as assertSuccessful(), assertNotFound().
• Dataset support for repetitive tests (like validation rules).

Example prompts

Here are some examples of how you might instruct an agent with this skill:

• "Create a new browser test for the user login flow."
• "Modify the existing feature test for product search to include edge case scenarios."
• "Debug the failing architecture test related to code style conventions."

Tips & gotchas

• Tests must be written using Pest. Use php artisan make:test --pest {name} to create new tests.
• Browser tests reside in the tests/Browser/ directory.
• Refer to search-docs for detailed Pest 4 patterns and documentation.