Generate PHPUnit feature tests for Laravel API CRUD endpoints.
npx skills add https://github.com/milosptr/pos-system --skill feature-test
Please help me install this Agent Skill. Skill: feature-test Source: https://github.com/milosptr/pos-system/tree/main/.claude/skills/feature-test Command: npx skills add https://github.com/milosptr/pos-system --skill feature-test
Create PHPUnit feature tests for API endpoints following Laravel testing conventions to ensure controllers, responses, and database interactions behave as expected.
Create a new Feature test file under tests/Feature for your API endpoints following the standard Laravel testing conventions.
High-intent search queries and answers about installing and using this skill.
To scaffold PHPUnit feature tests for Laravel API endpoints, this tool automates the creation of test files in tests/Feature. It generates standard CRUD test patterns covering listing, showing, creating, updating, and deleting resources using model factories and RefreshDatabase.
Yes, model factories are required to generate Laravel API feature tests. The scaffolding relies on factory-based data setups to populate the database for testing controllers, API responses, and database interactions across standard CRUD scenarios.
You can use this to test Laravel controllers and database interactions. It applies PHPUnit feature tests to API endpoints, ensuring controllers, responses, and database interactions behave as expected following Laravel testing conventions.
The best way to generate CRUD test patterns for a Laravel API is using an automated scaffolding tool. It creates a feature test file in tests/Feature with standard patterns for list, show, create, update, and delete operations.
This Laravel testing scaffolder requires a testing environment with Laravel, PHPUnit, and a phpunit.xml file configured. These prerequisites ensure the generated feature tests run correctly within the standard Laravel testing utilities.
Generated Laravel feature tests use RefreshDatabase to reset the database state after each test. This ensures factory-based data setups and database interactions remain isolated and predictable across CRUD test patterns.
elmochilyasSet up Pest 4 unit and feature testing for Laravel 13 applications.
DarkMonkDevRun unit, integration, and end-to-end tests in isolated containers.
noartemRefactor Laravel route closures into controller-backed routes with middleware.
ensi-platformCreate Pest PHP tests for Ensi Laravel API endpoints and database models.
