Skip to content
TrustedSkillsbeta
Back to all skills

Pest Testing

Checked
spatie·vlatest·testing·MIT

Automatically generate diverse, realistic user inputs to rigorously test application resilience against unexpected data and edge cases.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add spatie/freek.dev --skill pest-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

spatie

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned spatie/freek.dev at 91a2c48ac3.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
91a2c48ac3
Manifest
.claude/skills/pest-testing/SKILL.md
Scanned
1 file, 174 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, Pest Testing, automatically generates diverse and realistic user inputs to rigorously test application resilience against unexpected data and edge cases. It leverages the Pest testing framework for PHP applications, enabling you to create unit, feature, browser, smoke, visual regression, architecture, and other types of tests. The skill supports creating new tests, modifying existing ones, debugging failures, and enforcing code conventions.

When to use it

This skill is useful in these scenarios:

  • Creating new unit, feature, or browser tests.
  • Modifying existing tests within a PHP application using Pest.
  • Debugging test failures.
  • Performing smoke testing to quickly validate multiple pages.
  • Writing architecture tests to enforce code conventions.
  • Developing visual regression tests to compare screenshots for changes.

Key capabilities

  • Supports various test types: unit, feature, browser, smoke, visual regression, and architecture tests.
  • Integration with the Pest testing framework.
  • Browser testing in real browsers (Chrome, Firefox, Safari).
  • Support for device/viewport testing (e.g., iPhone 14 Pro, tablets).
  • Ability to switch between color schemes (light/dark mode) during tests.
  • Features like Event::fake() and assertions such as assertSuccessful(), assertNotFound().
  • Dataset support for repetitive tests (like validation rules).

Example prompts

Here are some examples of how you might instruct an agent with this skill:

  • "Create a new browser test for the user login flow."
  • "Modify the existing feature test for product search to include edge case scenarios."
  • "Debug the failing architecture test related to code style conventions."

Tips & gotchas

  • Tests must be written using Pest. Use php artisan make:test --pest {name} to create new tests.
  • Browser tests reside in the tests/Browser/ directory.
  • Refer to search-docs for detailed Pest 4 patterns and documentation.