PHPackages                             jrmadsen67/laravel-feature-test-generator - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. jrmadsen67/laravel-feature-test-generator

ActiveLibrary[Utility & Helpers](/categories/utility)

jrmadsen67/laravel-feature-test-generator
=========================================

Cascading model updates for Laravel.

204.1k[2 issues](https://github.com/jrmadsen67/laravel-feature-test-generator/issues)PHP

Since Jan 20Pushed 7y ago1 watchersCompare

[ Source](https://github.com/jrmadsen67/laravel-feature-test-generator)[ Packagist](https://packagist.org/packages/jrmadsen67/laravel-feature-test-generator)[ RSS](/packages/jrmadsen67-laravel-feature-test-generator/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

Laravel Feature Test Generator
==============================

[](#laravel-feature-test-generator)

Generator to create simple feature tests for Resource Controller in Laravel

Description
===========

[](#description)

The purpose of this generator to provide very quick, basic scaffolding for minimal feature test coverage against resource controllers. These can be run before you have built out any code, in a TDD fashion of sorts, or to add coverage to existing routes.

The goal is to get people past the "takes too much time" or "I'm not sure where to get started" phase of testing, and give them a direction to go in.

Usage
=====

[](#usage)

Start with a composer pull:

`composer require jrmadsen67/laravel-feature-test-generator --dev`

to bring the generator into your application. You may then create a set of feature tests with:

`artisan feature-test:generate Post`

where `Post` is the name of your resource (typically the same as the Model you are building around).

The `SampleFile` will show you what the default for that comand will produce.

That's it! Or can be - you have an additional option.

The above will run what I consider to be very simple but complete resource tests that cover index, show, create, store, edit, update and destroy. If you have some additional tests that you always like to run you may publish that stub and extend:

`artisan vendor:publish --tag=stubs`

This will copy the stub file to `config/feature-test-generator/stubs/resource_feature_tests.stub` where you can make your own changes.

VERY IMPORTANT NOTE YOU PROBABLY WON'T READ
===========================================

[](#very-important-note-you-probably-wont-read)

This does NOT write your routes or actual code for you! When you first run these tests, they will fail (unless you are adding them afterwards to test your existing code). You will be able to go through route by route and build out your code, adding to the test file itslef to handle failing tests and whatever else you want.

This is not a substitute for proper testing, just an "onboarding" into basic test coverage.

Additional Notes
================

[](#additional-notes)

This is very early and simple at the moment, in part because it needs to be simple enough that it will work as a starting point for everyone.

If you have tests you like to run all the time, I'd suggest using the publish feature. If you have tests or other functionality you think a majority of users would benefit from, I would be happy to accept any PRs.

Happy Testing!

---

I prefer you use the Issues section for problems, but if you do need to reach me you can do so at:

###  Health Score

25

—

LowBetter than 35% of packages

Maintenance18

Infrequent updates — may be unmaintained

Popularity26

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity39

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/68a4d9bb38657f2c9360f5e953323185bde37c17a22e38848215a876e399e9bd?d=identicon)[jrmadsen67](/maintainers/jrmadsen67)

---

Top Contributors

[![jrmadsen67](https://avatars.githubusercontent.com/u/821958?v=4)](https://github.com/jrmadsen67 "jrmadsen67 (13 commits)")

### Embed Badge

![Health badge](/badges/jrmadsen67-laravel-feature-test-generator/health.svg)

```
[![Health](https://phpackages.com/badges/jrmadsen67-laravel-feature-test-generator/health.svg)](https://phpackages.com/packages/jrmadsen67-laravel-feature-test-generator)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)