testing-best-practices
Skill8 starsChanged 2 months agoMITView on GitHub
Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.
16 other projects use a version of this, 12 of them edited.
Adopted by
Most recently taken up by
- trypostit/trypostedited, first seen Nov 1, 2026
- rbaskam/PRismedited, first seen Nov 1, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- nasirkhan/laravel-starteredited, first seen Oct 8, 2026
- syofyanzuhad/uptime-kitaedited, first seen Oct 8, 2026
- WINBIGFOX/TimeScribeedited, first seen Oct 8, 2026
Used with
Projects with it also use inertia-vue-development, configuring-horizon and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
syofyanzuhadSkillinertia-vue-development
Develops Inertia.js v2 Vue client-side applications. Activates when creating Vue pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions Vue with Inertia, Vue pages, Vue forms, or Vue navigation.
Also in 6 projects that use this
datashamanSkillconfiguring-horizon
Use this skill whenever the user mentions Horizon by name in a Laravel context. Covers the full Horizon lifecycle: installing Horizon (horizon:install, Sail setup), configuring config/horizon.php (supervisor blocks, queue assignments, balancing strategies, minProcesses/maxProcesses), fixing the dashboard (authorization via Gate::define viewHorizon, blank metrics, horizon:snapshot scheduling), and troubleshooting production issues (worker crashes, timeout chain ordering, LongWaitDetected notifications, waits config). Also covers job tagging and silencing. Do not use for generic Laravel queues without Horizon, SQS or database drivers, standalone Redis setup, Linux supervisord, Telescope, or job batching.
Also in 7 projects that use this
m3ueSkillai-sdk-development
TRIGGER when working with ai-sdk which is Laravel official first-party AI SDK. Activate when building, editing AI agents, chatbots, text generation, image generation, audio/TTS, transcription/STT, embeddings, RAG, vector stores, reranking, structured output, streaming, conversation memory, tools, queueing, broadcasting, and provider failover across OpenAI, Anthropic, Gemini, Azure, Groq, xAI, DeepSeek, Mistral, Ollama, ElevenLabs, Cohere, Jina, and VoyageAI. Invoke when the user references ai-sdk, the `Laravel\Ai\` namespace, or this project's AI features — not for Prism PHP or other AI packages used directly.
Also in 6 projects that use this
- syofyanzuhadSkill
wayfinder-development
Use this skill for Laravel Wayfinder which auto-generates typed functions for Laravel controllers and routes. ALWAYS use this skill when frontend code needs to call backend routes or controller actions. Trigger when: connecting any React/Vue/Svelte/Inertia frontend to Laravel controllers, routes, building end-to-end features with both frontend and backend, wiring up forms or links to backend endpoints, fixing route-related TypeScript errors, importing from @/actions or @/routes, or running wayfinder:generate. Use Wayfinder route functions instead of hardcoded URLs. Covers: wayfinder() vite plugin, .url()/.get()/.post()/.form(), query params, route model binding, tree-shaking. Do not use for backend-only task
Also in 4 projects that use this
whisper-moneySkillcashier-stripe-development
Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling. Triggered when a user mentions Cashier, Billable, IncompletePayment, stripe_id, newSubscription, Stripe subscriptions, or billing. Also applies when setting up webhooks, handling SCA/3DS payment failures, testing with Stripe test cards, or troubleshooting incomplete subscriptions, CSRF webhook errors, or migration publish issues.
Also in 4 projects that use this
gdarkoSkillfortify-development
ACTIVATE when the user works on authentication in Laravel. This includes login, registration, password reset, email verification, two-factor authentication (2FA/TOTP/QR codes/recovery codes), profile updates, password confirmation, or any auth-related routes and controllers. Activate when the user mentions Fortify, auth, authentication, login, register, signup, forgot password, verify email, 2FA, or references app/Actions/Fortify/, CreateNewUser, UpdateUserProfileInformation, FortifyServiceProvider, config/fortify.php, or auth guards. Fortify is the frontend-agnostic authentication backend for Laravel that registers all auth routes and controllers. Also activate when building SPA or headless authentication, customizing login redirects, overriding response contracts like LoginResponse, or configuring login throttling. Do NOT activate for Laravel Passport (OAuth2 API tokens), Socialite (OAuth social login), or non-auth Laravel features.
Also in 5 projects that use this
- +1 more from syofyanzuhad
Other versions16 projects use a version of this.
Word for word · 1
- gazi04/code-forge★ 0100% same
Edited · 12
- coollabsio/coolify★ 66k96% same
- anonaddy/anonaddy★ 4.9k94% same
- yaojingang/GEOFlow★ 4k94% same
- Relaticle/relaticle★ 1.8k96% same
- relaticle/relaticle★ 1.8k96% same
- nasirkhan/laravel-starter★ 1.4k95% same
- WINBIGFOX/TimeScribe★ 93396% same
- trypostit/trypost★ 83296% same
- syofyanzuhad/uptime-kita★ 18678% same
- Dricle/eveil★ 10100% same
2 more not listed
Wrote their own version · 3
- siberiacancode/agent-skills★ 23same name
- Spardutti/claude-skills★ 3same name
- davidanthonyn/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- infer-conventionsSkill
- laravel-best-practicesSkill
- tailwindcss-developmentSkill
The file
We split this skill into the rules it gives an agent
11 rules. 9 are common, 0 are distinctive, and 2 are very specific to this project.
9
Common
Most of the 15 edited versions we read keep these.
0
Distinctive
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
- Common: line 16
Read nearby tests before you choose syntax and organization.
- Common: line 24
Read this section before you write a test.
- Common: line 26
Test observable behavior and application contracts.
- Common: line 29
Leave framework behavior to framework tests.
- Common: line 30
Keep every test that can detect a distinct defect.
- Common: line 31
Write a feature test first.
- Very specific: line 32
Write a feature test for every behavior reachable through a request.
- Common: line 34
Use the test tools that the project installs.
- Common: line 38
Read the code under test. Read the tests in the same directory.
- Common: line 41
Write the tests. Run the smallest set of tests that covers the change.
- Very specific: line 42
Check every applicable item in rules/review.md and every selected rule file.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Testing Best Practices
This skill provides rules for designing Laravel tests. Each rule file explains what to do and why. Use search-docs for Laravel and Pest API syntax.
This project uses Pest. Follow the corresponding guidance in each rule.
Consistency First
Read nearby tests before you choose syntax and organization.
A pattern repeated throughout the project is a convention, and project conventions take precedence over this skill. Follow them and give new tests the same structure.
These rules govern the tests you write now. An existing test that follows a project convention is not defective merely because it conflicts with this skill. Do not delete or rewrite it. If the convention has drawbacks, explain them and let the user decide.
What to Test
Read this section before you write a test.
- Test observable behavior and application contracts. A test must pass after an implementation change if the behavior stays the same.
- Cover every changed decision and each applicable high-value failure mode. A decision is a branch, a validation, a calculation, or an authorization.
- Exercise declarations through behavior instead of repeating their text.
- Leave framework behavior to framework tests. Testing project configuration is not testing the framework. A constrained relationship, cast, scope, or validation rule belongs to this project.
- Keep every test that can detect a distinct defect. When two tests detect the same defect, trim the higher-layer test to one case and report the duplication. Do not delete an existing test.
- Write a feature test first. Write a unit test only for logic that does not use the framework.
- Write a feature test for every behavior reachable through a request. Real-browser tests require
pestphp/pest-plugin-browserand a browser download, neither of which this project installs. Mention the package only if the user asks for a real-browser test. - Judge an architecture test by the convention it protects, not by the rules above. An
arch()test declares a rule for an entire directory, such as the parent class of every model, the classes that may use an enum, or the methods every factory declares. It intentionally checks declarations and fails when a new file breaks the convention. - Use the test tools that the project installs. Add a new test dependency, plugin, or browser only after the user asks for it.
How to Apply
- Read the code under test. Read the tests in the same directory. Identify every decision in the code.
- Select every applicable branch in the rule index. Read every selected rule file.
- Report each defect in the code before you write a test. Examples are a method with no body, a policy that no action calls, and a write action with no validation. Test the actual behavior. Report the defect to the user.
- Write the tests. Run the smallest set of tests that covers the change. The tests must pass.
- Check every applicable item in
rules/review.mdand every selected rule file. Resolve every mismatch before completion.
Rule Index
Most changes need more than one rule file.
| Subject | Rule File |
| Test framework features that may already do the work | rules/finding-features.md |
| File layout, test names, and groups | rules/naming.md |
| Arrange-act-assert and choosing the correct assertion | rules/assertions.md |
| Endpoint coverage, authentication, authorization, tenant isolation, validation, and browser tests | rules/endpoint-tests.md |
| Factories, test data ownership, and repeated input values | rules/test-data.md |
| Fakes, mocks, outbound HTTP, time, randomness, and databases | rules/isolation.md |
| Escaping, injection, cross-tenant access, and privilege checks | rules/security.md |
| Environment and CI settings for a slow suite | rules/performance.md |
| Reviewing a test or suite | rules/review.md |
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
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.