Dirty table collector is per default permanent for performance reasons

v2.1.4

Update README.md

Configuration file test_suite_light is not supported anymore

Next release on main (#13)

* #7 Removes the CakePHP fixture init (#8)

Co-authored-by: Juan Pablo Ramirez <>

* #7 Removes the loadConfig (#12)

Co-authored-by: Juan Pablo Ramirez <>

Co-authored-by: Juan Pablo Ramirez <>

Dirty table collector is per default permanent for performance reasons

#14 cake3 make perm mode default (#15) (#17)

* #7 Removes the CakePHP fixture init (#9) (#11)

Co-authored-by: Juan Pablo Ramirez <>

* #14 Makes the dirty table collector permanent per default

* #14 Test fix

Co-authored-by: Juan Pablo Ramirez <>

Configuration file test_suite_light is not supported anymore

Merge branch 'cake3-next' into cake3

# Conflicts:
#	src/FixtureManager.php

Fix connection issue with CakePHP Fixtures

#7 Removes the CakePHP fixture init (#8) (#10)

Co-authored-by: Juan Pablo Ramirez <>

Fix connection issue with CakePHP Fixtures

#7 Removes the CakePHP fixture init (#9) (#11)

Co-authored-by: Juan Pablo Ramirez <>

Statistic tool

The suite now comes with a statistic tool. This will store the execution time, the test name, the number and the list of the dirty tables for each test.

The statistics will be store after each suite in tmp/test_suite_light/test_suite_statistics.csv.

With the help of your IDE, you can easily order the results and track the slow tests, and improve their respective performance.

Not the that the statistic tool does not perform any query in the database. It uses information that is being gathered regardless of its actvation. It has no significant impact on the overall speed of your tests.

Statistic tool

The suite now comes with a statistic tool. This will store the execution time, the test name, the number and the list of the dirty tables for each test.

The statistics will be store after each suite in tmp/test_suite_light/test_suite_statistics.csv.

With the help of your IDE, you can easily order the results and track the slow tests, and improve their respective performance.

Not the that the statistic tool does not perform any query in the database. It uses information that is being gathered regardless of its actvation. It has no significant impact on the overall speed of your tests.