pest-testing

Create and refactor Pest PHP 4 tests for Laravel applications.

Updated May 28, 2026
One-click install
npx skills add https://github.com/EyesLight6/sopitas --skill pest-testing-eyeslight6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pest-testing
Source: https://github.com/EyesLight6/sopitas/tree/main/sopitas/.agents/skills/pest-testing
Command: npx skills add https://github.com/EyesLight6/sopitas --skill pest-testing-eyeslight6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Laravel developers create, maintain, and improve Pest PHP tests without relying on outdated PHPUnit patterns or inconsistent testing practices.

Core Features & Use Cases

  • Pest Test Authoring: Guides creation and refactoring of Laravel tests using Pest syntax, expectations, datasets, and mocking patterns.
  • Advanced Testing Workflows: Supports browser testing, smoke testing, visual regression, architecture tests, and Livewire component testing scenarios.
  • Use Case: A developer changing a Laravel feature can use this Skill to update affected tests, add assertions, and verify behavior through Pest 4 testing workflows.

Quick Start

Ask the Pest testing skill to help write or fix Laravel Pest tests for a feature change.

Frequently Asked Questions about pest-testing

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

FAQPage Schema
How do I write Pest PHP tests for a Laravel feature change?

To write Pest PHP tests for a Laravel feature change, use this Skill to generate and refactor tests using Pest 4 syntax, expectations, datasets, and mocking patterns. It guides you in creating feature, unit, browser, and architecture tests to verify your application behavior.

Does this Skill support Livewire component testing and browser interactions in Laravel?

Yes, this Skill supports Livewire component testing and browser interactions in Laravel. It provides advanced testing workflows for browser testing, smoke testing, visual regression, and architecture tests using Pest 4 syntax.

How do I refactor PHPUnit tests to Pest 4 syntax in Laravel?

You can refactor PHPUnit tests to Pest 4 syntax by applying this Skill to update assertions, test organization practices, and expectations. It helps transition Laravel projects away from outdated PHPUnit patterns toward reliable Pest PHP workflows.

What is the best way to organize Pest datasets and mocking patterns in Laravel?

The best way to organize Pest datasets and mocking patterns is by following this Skill's test organization practices. It applies Pest 4 requirements to structure datasets, assertions, and mocking workflows for reliable Laravel application testing.

Can I use architecture testing to verify Laravel application structure with Pest?

Yes, you can use architecture testing to verify Laravel application structure with Pest. This Skill guides creating architecture tests alongside feature, unit, and browser tests to enforce structural constraints and verify behavior through Pest 4 workflows.

Why are my Pest tests failing after updating a Laravel feature?

Pest tests may fail after a Laravel feature update due to outdated assertions or incompatible PHPUnit patterns. Use this Skill to fix affected tests, add correct Pest 4 assertions, and verify behavior through updated testing workflows.