Laravel TDD
Test-driven Laravel for Muse: PHPUnit and Pest, model factories, HTTP and API tests, Sanctum auth testing, fakes and mocks, and coverage goals, in red-green-refactor loops.
- What
- Test-driven Laravel for Muse: PHPUnit and Pest, model factories, HTTP and API tests, Sanctum auth testing, fakes and mocks, and coverage goals, in red-green-refactor loops.
- Cost
- Free
- Needs
- Use "Laravel TDD" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: test-driven development for Laravel applications, so Muse writes tests first and features second. Covers the full red-green-refactor cycle: PHPUnit configuration for testing (in-memory SQLite, array cache, mail and queue fakes), base TestCase helpers (actingAsUser, actingAsAdmin), model factories with states and sequences (UserFactory with admin and unverified states, relationships, make versus create), model tests (hidden attributes, scopes, relationships), feature and HTTP tests (guest redirects, validation errors, authorization boundaries like users-can-only-modify-their-own), JSON API tests (paginated lists, assertJsonStructure, 401 for unauthenticated), Sanctum token auth testing (register, login, wrong password, bearer token), mocking with Laravel fakes (Http::fake with sequences, Mail::fake, Notification::fake, Queue::fake, Storage::fake, Event::fake), Artisan command tests, authorization tests (policies, gates, super-admin), Pest-style feature tests, and coverage setup with goals per component (models 95%+, services 90%+, overall 80%+). Includes a quick-reference table of every assertion helper and DO/DON'T testing best practices (factories over manual create, one logical assertion per test, never test framework internals, never couple tests). Use when writing Laravel tests with PHPUnit or Pest, or driving a Laravel feature test-first. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: needs a Laravel project with PHPUnit or Pest wired up; coverage targets are goals, not guarantees; examples assume recent Laravel versions, check yours. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Laravel TDD" with your Muse. Prerequisites: none to install. Pure guidance; a Laravel project with PHPUnit or Pest set up helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/laravel-tdd/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Drive this Laravel feature test-first (red-green-refactor): [describe the feature]." 3. Ask it to write the failing test first, then the minimal implementation, then refactor, using factories and fakes for boundaries. Tip: ask "write the feature test for this endpoint, including auth and authorization cases" and let the tests lead. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated code before merging.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.