pest-testing

Writes and fixes Pest PHP tests for Laravel applications.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Nweremizu/ekklesia --skill pest-testing-nweremizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pest-testing
Source: https://github.com/Nweremizu/ekklesia/tree/main/.junie/skills/pest-testing
Command: npx skills add https://github.com/Nweremizu/ekklesia --skill pest-testing-nweremizu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create, fix, and refactor Laravel tests in Pest without drifting from the project's existing conventions, reducing brittle test changes and speeding up test-driven development.

Core Features & Use Cases

  • Pest Syntax Guidance: Use test() and it() consistently, follow the repo's local style, and convert PHPUnit tests to Pest when needed.
  • Laravel Test Coverage: Handle feature tests, unit tests, browser tests, smoke tests, mocking, datasets, and architecture checks in a Laravel 13 codebase.
  • Practical Workflow Support: Validate common behaviors like authentication, redirects, validation, JavaScript-free page loads, and other application flows with clear, minimal test changes.
  • Use Case: A developer updates member onboarding and needs a few focused Pest tests that match the existing suite, protect regressions, and confirm the UI still works in the browser.

Quick Start

Ask for a Pest test that matches the existing Laravel project style and covers the specific behavior or regression you want to verify.

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 tests for Laravel that match my existing project conventions?

Pest tests for Laravel are written using test() and it() syntax, following the repo's local style and structure. The Skill applies Pest 4 conventions, Laravel testing helpers, datasets, and mocking to ensure new unit, feature, browser, and smoke tests integrate cleanly without drifting from established test patterns.

What is the best way to convert PHPUnit tests to Pest in a Laravel application?

Converting PHPUnit tests to Pest involves applying Pest 4 conventions while preserving the existing test directory structure and Laravel testing helpers. The Skill handles this conversion by refactoring assertions into Pest's it() and test() syntax, maintaining project consistency throughout the test suite.

Can I use Pest datasets and mocking for Laravel feature and architecture tests?

Pest datasets and mocking are fully supported for Laravel feature and architecture tests. The Skill implements these alongside Laravel testing helpers to validate common behaviors like authentication, redirects, and validation, while also performing architecture checks to enforce structural rules within the application.

Does this approach support browser tests and smoke tests in a Laravel 13 codebase?

Browser tests and smoke tests are supported in a Laravel 13 codebase using Pest. The Skill covers these workflows by validating JavaScript-free page loads, application flows, and common UI regressions, ensuring minimal test changes while protecting existing functionality across unit, feature, and browser testing directories.

Why are my Pest test changes brittle when updating Laravel application flows?

Pest test changes become brittle when they drift from existing project conventions or use inconsistent test structure. The Skill fixes this by applying Pest 4 conventions, Laravel testing helpers, and project-consistent structure, reducing brittle modifications and accelerating test-driven development for application behaviors.