pest-testing

Automate Pest PHP testing workflows in Laravel projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/muddassarsaleemiqbal/haulix-core --skill pest-testing-muddassarsaleemiqbal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pest-testing
Source: https://github.com/muddassarsaleemiqbal/haulix-core/tree/main/.github/skills/pest-testing
Command: npx skills add https://github.com/muddassarsaleemiqbal/haulix-core --skill pest-testing-muddassarsaleemiqbal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pest testing in Laravel projects often involves writing, editing, and refactoring tests across multiple directories (tests/Unit, tests/Feature, tests/Browser). This skill provides a clear, repeatable guide to Pest 4 usage, activation triggers, and best practices to accelerate quality assurance.

Core Features & Use Cases

  • Guidance on Pest 4 features: Browser testing, datasets, mocks, and architecture tests.
  • Clear test organization and workflow recommendations for unit, feature, and browser tests in Laravel.
  • Real-world scenario: when migrating from PHPUnit to Pest or adding properties like datasets and Livewire component tests.

Quick Start

Use Pest in your Laravel project to scaffold tests and run php artisan test.

Frequently Asked Questions about pest-testing

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

FAQPage Schema
How do I set up Pest PHP testing in a Laravel project?

Pest PHP testing in Laravel projects is set up by organizing tests across unit, feature, and browser directories. You can scaffold tests and execute them using the php artisan test command to validate your application.

Can I migrate my existing PHPUnit tests to Pest in Laravel?

Yes, migrating from PHPUnit to Pest in Laravel is supported. The workflow provides guidance on refactoring tests, organizing them into unit, feature, and browser directories, and leveraging Pest 4 features like datasets and architecture checks.

Does this workflow support Laravel browser testing and datasets?

Yes, Laravel browser testing and datasets are fully supported. The workflow applies Pest 4 features across unit, feature, and browser tests, including guidance on mocks, architecture checks, and Livewire component testing scenarios.

What is the best way to organize Pest tests across different directories?

The best way to organize Pest tests is by separating them into tests/Unit, tests/Feature, and tests/Browser directories. This workflow provides clear test organization and workflow recommendations to accelerate quality assurance in Laravel.

When do I need to use architecture tests in Pest PHP?

Architecture tests in Pest PHP are needed to enforce structural rules and constraints within your Laravel codebase. This workflow includes guidance on applying architecture checks alongside unit, feature, and browser testing.