agentleFS
MrPunyapalMrPunyapal/laravel-auditor/.agents/skills/package-testing/SKILL.md

package-testing

Skill78 starsChanged 3 months agoMITView on GitHub

Use this skill when writing, editing, fixing, or reviewing package tests with Pest 4/5 and Orchestra Testbench, including TDD, feature tests, unit tests, type coverage, arch tests, workbench behavior, commands, routes, config, migrations, and publishable resources.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with TDD: write the smallest failing package test for the requested behavior, then implement the smallest change that makes it pass.

    line 17
  2. Distinctive:

    Prefer focused feature tests for package integration behavior and arch tests for broad constraints.

    line 19
  3. Very specific:

    Use composer test:unit -- --filter ...

    line 20
  4. Distinctive:

    Keep real package tests in the suite and remove only throwaway tests that were explicitly created for local scaffolding experiments.

    line 21
  5. Distinctive:

    Test config merge and config override by asserting default package config, then overriding the host config value in the Testbench app.

    line 34
  6. Distinctive:

    Test publishable assets, migrations, views, lang files, or config by invoking vendor publish behavior and asserting the target path exists.

    line 35
  7. Very specific:

    Test routes with Testbench HTTP requests, commands with Artisan assertions, migrations with a SQLite test database, and workbench behavior …

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Package Testing

Primary Goal

Prove package behavior with Pest 4/5, Orchestra Testbench, and the local tests/TestCase.php setup before or alongside implementation.

Workflow

  1. Start with TDD: write the smallest failing package test for the requested behavior, then implement the smallest change that makes it pass.
  2. Cover happy-path, unhappy-path, and edge-case behavior when the feature has meaningful failure modes.
  3. Prefer focused feature tests for package integration behavior and arch tests for broad constraints.
  4. Use composer test:unit -- --filter ... while iterating, composer test:types when type-sensitive tests or code changed, and composer test before finishing.
  5. Keep real package tests in the suite and remove only throwaway tests that were explicitly created for local scaffolding experiments.

References

  • tests/TestCase.php
  • tests/Pest.php
  • tests/Feature/
  • tests/Unit/
  • tests/ArchTest.php
  • composer.json scripts

Examples

  • Test config merge and config override by asserting default package config, then overriding the host config value in the Testbench app.
  • Test publishable assets, migrations, views, lang files, or config by invoking vendor publish behavior and asserting the target path exists.
  • Test routes with Testbench HTTP requests, commands with Artisan assertions, migrations with a SQLite test database, and workbench behavior after composer build when needed.

Anti-Patterns

  • Deleting real package tests because they are inconvenient.
  • Relying only on smoke tests when behavior needs assertions.
  • Testing implementation details when observable package behavior is available.
  • Keeping throwaway scaffolding experiment tests in the package test suite.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.