Cleanup after actions in UI

[r-erema]

Hello. I run my acceptance test via selenium and webdriver, it creates a user order(row in db) by UI.
I have cleanup: true in config, then I expect that the dump will cleanup database with created order(according codeception documentation).

Either I do something wrong or the plugin(or codeception) does not cleanup.
My test:

public function testCreateOrder(AcceptanceTester $I, Example $example): void {
 $config =\Codeception\Configuration::config();
 $I->loginIfNotAuthorized(
 $config['users']['admin_full']['login'],
 $config['users']['admin_full']['password'],
 $config['users']['admin_full']['auth_cookie_value'] ?? null
 );
 $I->amOnPage('/services/new/');
 $I->selectOption('select#installment_payment_type', $example['installment_payment_type_friendly']);
 $I->selectOption('select#installment_term_type', $example['installment_term_type_friendly']);
 $I->click('Create order');
}

And config:

...
modules:
 enabled:
 - Codeception\Extension\MultiDb
 config:
 Codeception\Extension\MultiDb:
 connectors:
 connector_1:
 dsn: "mysql:host=localhost;port=3306;dbname=db;charset=utf8"
 user: 'sites_db_access'
 password: '****'
 dump: 'tests/_data/dump.sql'
 populate: true
 cleanup: true
...

[codemedic]

Which version of Codeception are you using?
I haven't looked into maintaining MultiDb, in line with later developments in Codeception framework.
Codeception v2.0 and v2.1 are the last I tinkered with.

Also, if you are not using any of the "steps" based usage of MultiDb, you are probably better off using the Db module that comes with Codeception.

[r-erema]

Which version of Codeception are you using?

I'm using Codeception 2.3.4.

Also, if you are not using any of the "steps" based usage of MultiDb, you are probably better off using the Db module that comes with Codeception.

I'm using them, and I need MultiDb features:)

Codeception v2.0 and v2.1 are the last I tinkered with.

Apparently, the only solution now is downgrade my codeception to this versions?

[r-erema]

Сome up with a solution more like a hack: add method AcceptanceTester::setupCleanupTruncateDb() which cleanups affected tables in test, and call it on end of test or in _after(), but I do not really like this decision.

class AcceptanceTester extends \Codeception\Actor {
...
public function setupCleanupTruncateDb(): void { 
 $this->setupCleanup(\Codeception\Extension\MultiDb\Utils\CleanupAction::runSql('
 SET FOREIGN_KEY_CHECKS = 0;
 TRUNCATE TABLE table_1;
 ...
 TRUNCATE TABLE table_n;
 SET FOREIGN_KEY_CHECKS = 1;
 '));
}
}

[codemedic]

Sorry @gutsout !

only solution now is downgrade my codeception to this versions?

It is more of a testing and adapting the code to changes if-any. Unfortunately, I am not in a position right now to spend some time on it.
If you could figure out what is breaking in newer version of Codeception, that would be very valuable.

[tuannguyen201]

I'm using MultiDb feature in codeception 2.3.7 and also cannot clear the record after each scenario test. I hope it will be supported in future.