Use Laravel database fill to accelerate development requires four steps: first, define dynamic data generation rules through the factory, then organize the fill class according to the functional module, and then customize the Faker again to obtain data that is closer to the actual situation, and finally run the fill command efficiently. For example, create a UserFactory to define the user data structure and generate test data by calling the factory method; separate UsersTableSeeder, PostsTableSeeder, etc. by modules and call them uniformly by DatabaseSeeder; use fake()->randomElement or custom premium() methods in the factory to enhance data authenticity; use the php artisan migrate:fresh --seed or db:seed commands to flexibly reset or update data, thereby improving testing efficiency and reducing manual input.

When you're working on a Laravel project, setting up database seeing for development is one of the best things you can do to speed up testing and avoid manual data entry. It gives you consistent, realistic data to work with—without having to click through forms every time you reset your database.

Here's how to set it up in a way that actually works for real-world projects.

Use Factory for Dynamic Data Generation

Factoryes are the backbone of Laravel's seeing system. Instead of hardcoding values into seed files, factories let you define reusable blueprints for your models.

For example, if you have a User model, you'd create a factory like this:

 // database/factories/UserFactory.php
use Illuminate\Database\Eloquent\Factory\Factory;

class UserFactory extends Factory
{
    public function definition()
    {
        Return [
            'name' => fake()->name(),
            'email' => fake()->unique()->safeEmail(),
            'password' => bcrypt('password'),
        ];
    }
}

Now, whenever you need test users, you can generate them with traits or states to customize behavior:

• Create 10 regular users:

   \App\Models\User::factory(10)->create();

• Create one admin user:

   \App\Models\User::factory()->create(['is_admin' => true]);

This makes it easy to simulate different scenarios without writing repetitive seed classes.

Organize Seeders by Feature or Module

Don't just throw everything into DatabaseSeeder . If your app has multiple modules (like users, posts, comments), create separate seeder files for each.

For example:

 database/seeders/UsersTableSeeder.php
database/seeders/PostsTableSeeder.php
database/seeders/CommentsTableSeeder.php

Then call them from the main DatabaseSeeder class:

 public function run()
{
    $this->call([
        UsersTableSeeder::class,
        PostsTableSeeder::class,
        CommentsTableSeeder::class,
    ]);
}

This keeps your seeing logic modular and easier to debug or disable when needed.

Also, don't forget to use artisan make:seeder to generate these files—it saves time and avoids typos.

Don't Skip Faker Customization

Faker comes with tons of built-in data types, but sometimes you need more control. For example, if you're generating product names, you might want something semi-realistic instead of random words.

You can tweak faker calls directly in your factories:

 'product_name' => fake()->randomElement(['Premium Widget', 'Deluxe Gadget', 'Pro Model']),
'price' => fake()->numberBetween(10, 500),

Or even better, create helper methods in your factories for complex logic:

 public function premium()
{
    return $this->state(fn (array $attributes) => [
        'type' => 'premium',
        'price' => 99.99,
    ]);
}

This lets you write cleaner factory calls like:

 Product::factory()->premium()->create();

Run Seeding Efficiently During Development

To refresh your database and re-seed, use:

 php artisan migrate:fresh --seed

That command drops all tables, reruns migrations, and then runs your seeders. Perfect when you're still designing your schema.

If you only need to re-run the seeders without resetting the database structure:

 php artisan db:seed

But be careful—this won't clear existing data. So if you're adding new seeders, consider truncating relevant tables first using the --class option:

 php artisan db:seed --class=UsersTableSeeder

This will re-run just the specified seeder, which is handy when iterating quickly.

Setting up database seeing properly takes a bit of time upfront, but it pays off every time you reset your dev DB or onboard a new team member. Keep your factories clean, organize your seeders, and take advantage of faker customization—it'll save you hours down the line.

Basically that's it.

The above is the detailed content of Setting up Database Seeding for Development in Laravel?. For more information, please follow other related articles on the PHP Chinese website!