AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomsrequest-factories
Request Factories is a Laravel testing utility that eliminates boilerplate when writing HTTP request tests by auto-populating form request fields with sensible defaults. Developers specify test data once in a factory class, then reuse it across tests, focusing assertions on the specific behavior being tested rather than satisfying validation rules.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | worksome/request-factories |
| Owner | worksome |
| Primary language | PHP |
| License | MIT — OSI-approved |
| Stars | 623 |
| Forks | 17 |
| Open issues | 5 |
| Latest release | v3.5.1 (2026-04-09) |
| Last updated | 2026-06-22 |
| Source | https://github.com/worksome/request-factories |
What request-factories is
A PHP package (MIT license) extending Laravel's model factory pattern to FormRequest objects. It provides a `RequestFactory` base class with `definition()` and `files()` methods, integrates via macros into FormRequest classes, and supports multiple invocation styles: `factory()->create()`, `fake()`, and Pest's `fakeRequest()` higher-order method. Compatible with PHPUnit and Pest.
Get the request-factories source
Clone the repository and explore it locally.
git clone https://github.com/worksome/request-factories.gitcd request-factories# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Factory placement convention: store in `tests/RequestFactories/` with `Factory` suffix matching FormRequest name for automatic Artisan command support.
- Factory `definition()` method should include all required FormRequest fields with valid defaults; `files()` method handles UploadedFile instances separately.
- Data precedence is strict: request() payload > state() > definition() > files(). Plan field overrides carefully to avoid subtle test failures.
- Extend existing factories via inheritance or use `state()` method to create variants; avoid duplicating definition logic across factory subclasses.
- For tests without a corresponding FormRequest (raw requests), factories still work but require manual class instantiation and do not gain macros on Request class.
When to avoid it — and what to weigh
- Non-Laravel PHP projects or other frameworks — This package is tightly coupled to Laravel's testing infrastructure, FormRequest class, and Artisan command structure. It does not work outside Laravel.
- Testing logic outside HTTP request scope — If your tests focus on business logic, domain models, or services independent of HTTP layers, request factories add no value and introduce an unnecessary abstraction layer.
- Minimal validation rule complexity — For endpoints with only one or two required fields, defining a factory may add more overhead than simply passing field values directly in each test.
- Projects requiring strict audit trails of all test data — Faker-generated default data and factory state chains can obscure the exact payload being tested; projects with rigorous compliance requirements may need explicit, inline test data instead.
License & commercial use
MIT License. Permissive OSI-approved license permitting commercial use, modification, and distribution with minimal restrictions (retain license notice and liability disclaimer).
MIT License explicitly permits commercial use in closed-source applications and commercial products. No licensing fees, no proprietary restrictions. Include original license text in source distribution if applicable.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
No explicit security vulnerabilities mentioned or disclosed in available data. Standard Laravel testing best practices apply: do not use real credentials or production data in factories; use Faker for synthetic data. Since this runs only in test environment (`--dev` dependency), production exposure is minimal. Review generated UploadedFile mocks to ensure they do not cause unintended file operations during tests.
Alternatives to consider
Manual inline test data
Simplest approach for small projects or endpoints with few fields; avoids factory abstraction but requires repeating payloads per test and is harder to maintain at scale.
Laravel Model Factories + seeding
Addresses database state but does not reduce HTTP request payload boilerplate; often used alongside request factories, not as a replacement.
API testing tools (Postman, Insomnia) with collections
External UI-based alternatives for manual API testing; do not integrate into automated test suites and add operational overhead versus in-code factories.
Build on request-factories with DEV.co software developers
Use request factories to eliminate repetitive FormRequest validation payloads. See how Worksome's testing utility can accelerate your test suite.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
request-factories FAQ
Does Request Factories work with PHPUnit, or only Pest?
Can I use request factories without a FormRequest?
What if a test needs different data than the factory default?
Is there built-in support for validating factory definitions match FormRequest rules?
Custom software development, end to end
Standing up request-factories properly takes more than a deploy. As a software development agency, DEV.co handles the open-source testing architecture, the web development on top, and the operational work underneath.
Streamline Your Laravel Tests
Use request factories to eliminate repetitive FormRequest validation payloads. See how Worksome's testing utility can accelerate your test suite.