- bug report? no
- feature request? yes
- version: df5e87f
Tester\Runner\Runner::findTests has always been very slow when using test cases, mostly because of initiateTestCase. With the recent improvement which makes Tester run failed tests first, this has become even bigger issue than before.
Our application has about ~300 test cases and the findTests phase takes about 20 seconds (~15 second is pure Tester code, about 5 second is our bootstrap).
Tester\Runner\Runner::findTestshas always been very slow when using test cases, mostly because of initiateTestCase. With the recent improvement which makes Tester run failed tests first, this has become even bigger issue than before.Our application has about ~300 test cases and the findTests phase takes about 20 seconds (~15 second is pure Tester code, about 5 second is our bootstrap).