My factory is not applied to my test cases

Where is your UserFactory file located? In database/factories?

@ftiersch yes under database/factories

Is the filename userFactory.php or UserFactory.php?

If it's the first rename it to the second.

@tray2 its UserFactory.php

And your User class has a "verified" column? Is the verified column filled in the database when you execute the factory?

@ftiersch this my migration

public function up()
    {
        Schema::create('users', function (Blueprint $table) {
            $table->increments('id');
            $table->string('name');
            $table->string('email');
            $table->string('password');
            $table->boolean('verified')->default(false);
            $table->rememberToken();
            $table->timestamps();
        });
    }

It appears that you might have modified the $hidden or $visible property, or implemented toArray() on the model because I would not expect to see the password hash and remember token in the result. Did you also give the verified field the same treatment?

@tykus this my attributes in mode user

 protected $table = 'users';

    /**
     * The attributes that are mass assignable.
     *
     *
     * @var array
     */
    protected $fillable = ['name', 'email', 'password'];

    /**
     * The attributes that should be hidden for arrays.
     *
     * @var array
     */
    protected $hidden = [
        'password', 'remember_token',
    ];

@ftiersch @tray2 @tykus hi guys, I remember I am using use DatabaseTransactions will this affect something ?

That depends, I would not use transactions unless it is critical that more than one database action needs to complete successfully.

Let's say you have a bank and you want to transfer funds from one account to another.

1. Deduct the amount from the source account.
2. Add the amount to the destination account.
3. If both actions finish ok commit it else rollback.

So if you have that kind of need use transactions otherwise I would suggest that you don't use it.

Somethings to be aware of is that transactions can cause deadlocks in your database. This is normal behaviour but you need to handle it.

https://laravel.com/docs/6.x/database#database-transactions

@omda

Try updating the default value on your verified column in the migration to 0 (as opposed to false, since it's a boolean field), see below:

public function up()
    {
        Schema::create('users', function (Blueprint $table) {
            $table->increments('id');
            $table->string('name');
            $table->string('email');
            $table->string('password');
            $table->boolean('verified')->default(0);
            $table->rememberToken();
            $table->timestamps();
        });
    }

my issue is solved, the problems i found there are two UserFactory.php one in root directory database and another in Module, cause i use Module package.