Pest Testing Skill: Faster Laravel Test Workflows

Where this fits

A Laravel developer is mid-refactor, and the test suite is suddenly red. They need to update dozens of Pest tests, add new assertions, convert existing PHPUnit tests, and ensure browser smoke tests still pass. This skill activates exactly when the user writes, edits, or fixes Pest tests, providing context-aware guidance for syntax, datasets, mocking, and browser testing—so the agent doesn't guess.

Why agents benefit

• Triggers precisely on test-related tasks, not generic PHP code, so the agent uses Pest-specific patterns without mixing in controller or model logic.
• Provides up-to-date Pest 4 syntax and APIs (test()/it(), expect(), datasets, arch()) directly from docs, reducing hallucination.
• Covers advanced scenarios like Livewire component tests and browser automation (visit/click/fill) that are easy to get wrong.
• Enforces TDD workflows: the skill knows when to suggest dataset expansion, refresh database handling, and architecture tests.
• Converts PHPUnit to Pest with minimal friction, matching Laravel's default test framework.

Practical scenarios

Fixing broken tests after a model change

You changed a relationship name and your Feature tests now reference the old method. The skill guides the agent to update assertions, adjust factory usage, and apply RefreshDatabase correctly without touching non-test files.

Adding dataset-driven tests for form validation

You have a form with multiple validation rules. Instead of repeating test cases, the skill suggests using Pest datasets to loop over input variations, keeping the test suite lean and maintainable.

Smoke testing pages for JS errors

You need to verify that every public page loads without console errors. The skill shows how to use Pest's browser testing feature to visit multiple URLs, check for errors, and assert on the DOM—all within a single test file.

Add it to your agent workflow

Install the skill with:

npx skills add promovaweb/specsfy --skill pest-testing

Then, in your agent prompt, just mention that you're working on Pest tests—for example, "Refactor the PaymentTest to use datasets and add a browser test for the checkout page." The skill will automatically load the relevant documentation and best practices. For a broader view of available agent skills, see OpenAgentSkill.

Compare before adopting

Before integrating, compare the skill's freshness against Pest's release cycle—check how quickly it reflects new Pest versions. Look at the GitHub stars (currently 60) and commit history to gauge maintenance. Also, consider if your workflow already includes Pest-specific tooling or if the skill duplicates what your IDE already provides. Ensure it fits your existing agent setup (e.g., how it interacts with your test runner).

Why it is worth tracking

Pest is the default testing framework in Laravel 11+, and its feature set is expanding (browser testing, arch tests). This skill ensures your agent stays current with Pest 4 APIs, reducing blind spots in test generation and debugging. With active maintenance and a clear scope, it's a low-risk addition that can meaningfully speed up test-related tasks. Revisit it when Laravel or Pest releases major updates to confirm the skill keeps pace.