Codeception Db Module deleting my DATABASE!

[gusdecool]

I user Codeception version 1.6.7

Following with this tutorial here http://codeception.com/docs/modules/Db
I tried this Db config:

paths:
    tests: tests
    log: tests/_log
    data: tests/_data
    helpers: tests/_helpers
settings:
    bootstrap: _bootstrap.php
    suite_class: \PHPUnit_Framework_TestSuite
    colors: true
    memory_limit: 1024M
    log: true
modules:
    enabled: [Db]
    config:
      Db:
        dsn: 'mysql:host=localhost;dbname=test_codeception'
        user: 'gusdecool'
        password: 'gusdecool'
        dump: 'tests/_data/dump.sql'
        populate: true
        cleanup: false

And this is the code for my AcceptanceTesting

<?php
$user = 'gusdecool';
$pass = 'gusdecool';

/** @var $scenario \Codeception\Scenario */
$I = new WebGuy($scenario);
$I->wantTo('Do successful login');
$I->amOnPage('/index.php');
$I->fillField('user', $user);
$I->fillField('pass', $pass);
$I->click('input[type="submit"]');
$I->see('Hello, '.$user);
$I->amGoingTo('Testing check database');
$I->seeInDatabase('user', array('name'=>'gusdecool', 'pass'=>'123456'));

And then everytime i use run command, my actual database table is deleted!!!
and no database is dumped in tests/_data/dump.sql

Why this happening?

[DavertMik]

Sorry, but I think you misread documentation.

populate: true means - to use dump you provided to load data before the test.
cleanup: false means to not cleanup database between tests.

You should create a test dump yourself (via mysqldump or phpmyadmin) and put it into tests/_data/dump.sql. It will be used by Db module to create database for tests.

Just to be clear: Db module does not create dumps itself. It uses the dump you created to load data before tests.

[gusdecool]

Okay, that's mean in the step should be: dump the live database, put it into dump.sql then use the configuration as setting for creating new table?

If I'm right, i think you should change config name from dumpto source. It feel misleading for me.

[gustavovaldezsan]

I have the same feelings, and i'm here because i was mislead the same way DB Dump, sounds like a place where the DB will be dumped. +1 On the rename request.

[mipon]

I had to spend a few hours trying to find why the database is not restored in my acceptance tests because I expected the database data are automatically dumped when codecept run is performed. It would be useful if there was an option to allow it.

[DavertMik]

@mipon there are much better tools to create database dumps. Codeception is a testing framework not a database dumper. So we recommend to dump data on your own. You can use mysqldump command, as well as mysql runner or whatever you like. It is pretty hard to implement some universal tool for database dumping.

[mipon]

@DavertMik I see. Thanks for the advice.

[Antnee]

We've just come across a similar problem. We have some tests that are running on a new table. We put the CREATE TABLE query in our dump and it is created as expected. However, when the process is finished the only table that exists is the one that was created in the tests. Everything else is gone, including the ones created previously. I'd have expected that it only cleans up what it created, not everything but what it created. It seems backwards to me and has broken other tests that didn't create tables because they were already in place. We're using populate: true and cleanup: true. I don't understand the benefits of dropping every single table except the one that was being tested

[GustavoDarriens]

@gustavovaldezsan And here I came to see why cleanup didn't restore the database from dump after the last test was run.

[0xK3rn3lP4n1c]

Same here, I'm also running some tests and using dump: 'tests/_data/dump.sql', populate: true, and cleanup: false. However, even though I'm using mock objects and not directly writing to the database, my tables seem to be truncated every time I run the tests."