agentleFS
wachterjohanneswachterjohannes/symfony-skills/skills/make-test/SKILL.md

make-test

Skill4 starsChanged 2 months agoMITView on GitHub

Use when writing a test, or choosing which base class a test should extend.

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run them with symfony php bin/phpunit, falling back to vendor/bin/phpunit.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Tests

symfony console make:test TestCase InvoiceCalculatorTest
symfony console make:test KernelTestCase InvoiceRepositoryTest
symfony console make:test WebTestCase CheckoutControllerTest

Both the type and the name are arguments, so nothing is asked. symfony composer require --dev symfony/test-pack if the project has no test setup yet.

Picking the base class

The choice is about how much of the framework the test needs, and each step up costs time.

Base classFor
TestCaseplain PHPUnit — a class with no framework dependency
KernelTestCaseanything that needs a service from the container
WebTestCasean HTTP request and its response, without JavaScript
ApiTestCaseAPI-oriented scenarios, with API Platform
PantherTestCasea real browser and a real server, for JavaScript

Reaching for KernelTestCase where TestCase would do boots the kernel for every test and buys nothing.

What a test is for

A feature is not done until something exercises it the way a caller would — an HTTP request for a controller, a service call for a service. A test asserting that nothing threw is not that.

Run them with symfony php bin/phpunit, falling back to vendor/bin/phpunit.

For anything touching the database, run the migrations against the test database rather than recreating the schema, so the tests exercise what production will run.

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.