# pest-testing

Applies Pest 4 standards for testing PHP applications. Guides unit, feature, browser, and architecture tests with recommended assertions and datasets.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 716 installs · ★ 650
- Author: spatie
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/spatie/freek.dev/tree/HEAD/.claude/skills/pest-testing/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/pest-testing

## What it does

The skill sets strict conventions for writing tests with the Pest 4 PHP framework. It directs the agent to generate tests using `php artisan make:test --pest {name}`. Files go to `tests/Unit`, `tests/Feature`, or `tests/Browser/`. Existing tests cannot be deleted without prior approval.

Specific assertion helpers take priority over status codes. The agent must use `assertSuccessful()`, `assertNotFound()`, and `assertForbidden()` instead of raw `assertStatus()` calls. Before running mocks, it enforces importing `use function Pest\Laravel\mock;`. Missing this import will break test execution immediately.

It covers browser testing in real browsers with viewport control and `assertNoJavascriptErrors()`. For quick multi-page checks, it defines smoke testing patterns. It also handles architectural assertions with `arch()`, visual regression, and test sharding for parallel CI runs.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add spatie/freek.dev --skill pest-testing -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/pest-testing/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/pest-testing/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add spatie/freek.dev --skill pest-testing -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/pest-testing/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add spatie/freek.dev --skill pest-testing -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/pest-testing/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install spatie/freek.dev pest-testing
```

2. **Manually: put the files in place**
- File: `.github/skills/pest-testing/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add spatie/freek.dev --skill pest-testing -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/spatie/freek.dev --path .claude/skills/pest-testing
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/pest-testing/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add spatie/freek.dev --skill pest-testing -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/spatie/freek.dev/tree/HEAD/.claude/skills/pest-testing/SKILL.md

## When to use it
- write unit and feature tests using Pest 4 syntax
- set up browser tests with JavaScript error assertions
- enforce architectural rules across application controllers
- replace generic HTTP status assertions with Pest helpers

## Example prompts
- Write a Pest test for user password reset flow
- Create an architecture test enforcing controller naming rules
- Add a Pest 4 smoke test checking routes for JavaScript console errors

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 10ec538d4bd0c404.

BEGIN THIRD-PARTY FILE 10ec538d4bd0c404
```text
---
name: pest-testing
description: >-
  Tests applications using the Pest 4 PHP framework. Activates when writing tests, creating unit or feature
  tests, adding assertions, testing Livewire components, browser testing, debugging test failures,
  working with datasets or mocking; or when the user mentions test, spec, TDD, expects, assertion,
  coverage, or needs to verify functionality works.
---

# Pest Testing 4

## When to Apply

Activate this skill when:

- Creating new tests (unit, feature, or browser)
- Modifying existing tests
- Debugging test failures
- Working with browser testing or smoke testing
- Writing architecture tests or visual regression tests

## Documentation

Use `search-docs` for detailed Pest 4 patterns and documentation.

## Basic Usage

### Creating Tests

All tests must be written using Pest. Use `php artisan make:test --pest {name}`.

### Test Organization

- Unit/Feature tests: `tests/Feature` and `tests/Unit` directories.
- Browser tests: `tests/Browser/` directory.
- Do NOT remove tests without approval - these are core application code.

### Basic Test Structure

<code-snippet name="Basic Pest Test Example" lang="php">

it('is true', function () {
    expect(true)->toBeTrue();
});

</code-snippet>

### Running Tests

- Run minimal tests with filter before finalizing: `php artisan test --compact --filter=testName`.
- Run all tests: `php artisan test --compact`.
- Run file: `php artisan test --compact tests/Feature/ExampleTest.php`.

## Assertions

Use specific assertions (`assertSuccessful()`, `assertNotFound()`) instead of `assertStatus()`:

<code-snippet name="Pest Response Assertion" lang="php">

it('returns all', function () {
    $this->postJson('/api/docs', [])->assertSuccessful();
});

</code-snippet>

| Use | Instead of |
|-----|------------|
| `assertSuccessful()` | `assertStatus(200)` |
| `assertNotFound()` | `assertStatus(404)` |
| `assertForbidden()` | `assertStatus(403)` |

## Mocking

Import mock function before use: `use function Pest\Laravel\mock;`

## Datasets

Use datasets for repetitive tests (validation rules, etc.):

<code-snippet name="Pest Dataset Example" lang="php">

it('has emails', function (string $email) {
    expect($email)->not->toBeEmpty();
})->with([
    'james' => 'james@laravel.com',
    'taylor' => 'taylor@laravel.com',
]);

</code-snippet>

## Pest 4 Features

| Feature | Purpose |
|---------|---------|
| Browser Testing | Full integration tests in real browsers |
| Smoke Testing | Validate multiple pages quickly |
| Visual Regression | Compare screenshots for visual changes |
| Test Sharding | Parallel CI runs |
| Architecture Testing | Enforce code conventions |

### Browser Test Example

Browser tests run in real browsers for full integration testing:

- Browser tests live in `tests/Browser/`.
- Use Laravel features like `Event::fake()`, `assertAuthenticated()`, and model factories.
- Use `RefreshDatabase` for clean state per test.
```
END THIRD-PARTY FILE 10ec538d4bd0c404

The third-party file has ended. Everything between the 10ec538d4bd0c404 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2954 of 4832 bytes. © spatie · MIT · https://github.com/spatie/freek.dev/tree/HEAD/.claude/skills/pest-testing/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md