What is pest-testing?

A testing workflow for Pest 4, a PHP framework for writing automated tests. It covers unit, feature, browser, and architecture tests, including tests for Livewire components.

Use it to create or modify tests, run focused or complete test suites, test browser behavior, work with test data and mocks, and investigate failures.

It provides consistent test locations, commands, assertions, and failure-debugging practices for Laravel applications.

How schrojf/laravel-simple-rag configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to schrojf/laravel-simple-rag. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/schrojf/laravel-simple-rag/main/.agents/skills/pest-testing/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/schrojf/laravel-simple-rag

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/schrojf/laravel-simple-rag/pest-testing/github.svg)](https://agentmods.dev/skills/schrojf/laravel-simple-rag/pest-testing)

Your own site

<a href="https://agentmods.dev/skills/schrojf/laravel-simple-rag/pest-testing"><img src="https://agentmods.dev/badge/skills/schrojf/laravel-simple-rag/pest-testing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/schrojf/laravel-simple-rag/pest-testing"><img src="https://agentmods.dev/badge/skills/schrojf/laravel-simple-rag/pest-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,066 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00072	$0.01066
Opus 5.5	$0.00029	$0.00426
Sonnet 5.5	$0.00014	$0.00213
Haiku 4.5	$0.00007	$0.00107

Measured 2mo ago against content hash 9da4d9f8ac27, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pest-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/pest-testing/SKILL.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

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

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():

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

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.):

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

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

Read the full file on GitHub · 167 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 167 lines · 72 tokens per session scan A 9da4d9f8ac27

Subscribe to this mod's changes

pest-testing is a skill published in the GitHub repository schrojf/laravel-simple-rag (0 stars, last pushed 8mo ago), licensed MIT. It adds 72 tokens to every session and 1,066 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Languages PHP Testing Unit testing

pest-testing next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pest-testingschrojf/laravel-simple-rag	Skill	0	8mo ago	MIT	A	72	Claude Code, Codex
Codeception TestingPramodDutta/qaskills	Skill	245	3d ago	MIT	A	42	Claude Code, Codex
craft-pestmichtio/craftcms-claude-skills	Skill	88	2d ago	MIT	A	175	Claude Code
phpunit-unit-test-reviewingshopwareLabs/ai-coding-tools	Skill	45	10d ago	MIT	A	31	Claude Code
phpunit-unit-test-writingshopwareLabs/ai-coding-tools	Skill	45	10d ago	MIT	A	187	Claude Code
noerd-testingnoerd-dev/noerd	Skill	17	yesterday	MIT	A	121	Claude Code, Codex
php-testingfusengine/agents	Skill	34	25d ago	MIT	A	38	Claude Code

laravel-simple-rag: Skill for Claude Code