Bug #59436
closed
tearDown don't clean up database
0%
Description
Hi,
The functional testing is not cleaning up the databases when running the functional testing from cli. I'm using the FunctionalTestsBootstrap.
- ./typo3conf/ext/phpunit/Composer/vendor/bin/phpunit --process-isolation --colors --bootstrap typo3/sysext/core/Build/FunctionalTestsBootstrap.php typo3/sysext/core/Tests/Functional/DataHandling/IRRE
After this command I have 2 temporary databases still existing. I have the same issue with my own functional tests, but to "prove" that it was not a local issue i tried with the Core-Functional testing.
Any know issues on this topic?
Updated by Tomas Norre Mikkelsen about 10 years ago
This Commit explains the behavior.. It's not my wanted behavior, but i'm not the one to decide :)
https://git.typo3.org/Packages/TYPO3.CMS.git/commitdiff/8fbe410750e1348bfc5e4dc9691773c890b50502
Updated by Anja Leichsenring almost 10 years ago
- Sprint Focus set to On Location Sprint
Updated by Steffen Müller almost 10 years ago
afaik keeping the DB is a tradeoff between test isolation and test performance. Can you live with that and delete the DB in tearDown() in your own (extension) tests?
Updated by Steffen Müller almost 10 years ago
- Status changed from New to Needs Feedback
Updated by Christian Kuhn almost 10 years ago
- Status changed from Needs Feedback to Rejected
This will not be fixed. Databases are re-used for further runs improving performance then.
Updated by Anja Leichsenring almost 9 years ago
- Sprint Focus deleted (
On Location Sprint)