How to properly populate DB in Laravel 4 with Codeception by migrations, not by using dump

Question

I want to test my Laravel 4 applications. But I can't do it without creating database. The problem is, that I want to approach these things:

Separate DB for tests and for development (in memory also will be good)
Doing migrations and seeds before testing
Clearing database after testing

How to approach that?

tliokos · Accepted Answer · 2014-03-14 14:43:59Z

6

I think this will help you get started

1. Override Database settings for testing only

Inside app/config/testing create a new file named database.php and inside it place:

return array(

  'default' => 'mysql',

  'connections' => array(

    'mysql' => array(

      'driver' => 'mysql',

      'host' => 'localhost',

      'database' => 'TEST_DB_NAME', // Create also the Database

      'username' => 'USERNAME',

      'password' => 'PASSWORD',

      'charset' => 'utf8',

      'collation' => 'utf8_unicode_ci',

      'prefix' => '',

    )
  )
);

This database will bee used only for testing purposes.

2. Add this info to codeception.yml also

modules:

  config:

    Db:

      dsn: 'mysql:host=localhost;dbname=TEST_DB_NAME'

      user: 'USERNAME'

      password: 'PASSWORD'

      dump: app/tests/_data/dump.sql

3. Migrate and seed the testing database

php artisan migrate --seed --env="testing"

4. To clean up the database

php artisan migrate:reset --env="testing"

answered Mar 14, 2014 at 14:43

tliokos

3,6363 gold badges30 silver badges28 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Cysioland Over a year ago

I needed to skip migrate:reset, because Codeception automatically resets database

Collectives™ on Stack Overflow

How to properly populate DB in Laravel 4 with Codeception by migrations, not by using dump

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related