Executors and test maximums Question about karma-parallel

[joeljeske]

Hmm there is no upper limit on the number of tests. It does depend on how expensive each test is in terms of CPU or memory.

It is true that karma parallel adds some tests in some circumstances, but that is only when it detects that there are either not enough specs for each browser, or you are focusing a test in browser and therefore it needs to create a fake focused test in another browser to prevent all tests from running.

Your question concerns me, though. Why were you having trouble running all tests with karma mocha? It shouldn’t care how many tests you have. Karma parallel should speed things up, but not support more tests. I suspect you have some other issue that prevents all tests from running properly, not sure what that might though.

I do not suspect any issue with the strategy pattern, but if you wanted to experiment you can use a custom strategy. Look at the readme for info.

[d1820]

Thanks for response. here is a sample output from the parallel runner. Its seems odd the highlighted one is not 143/143 meaning all ran like the rest. seems like its skipping tests all together.

HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 200 of 200�[32m SUCCESS�[39m (11.557 secs / 8.1 secs)
HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 273 of 273�[32m SUCCESS�[39m (19.781 secs / 14.645 secs)
HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 208 of 208�[32m SUCCESS�[39m (8.559 secs / 4.681 secs)
HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 201 of 201�[32m SUCCESS�[39m (16.337 secs / 11.789 secs)
**

HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 104 of 143�[32m SUCCESS�[39m (7.131 secs / 4.808 secs)

**
HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 187 of 187�[32m SUCCESS�[39m (6.432 secs / 3.435 secs)
HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 267 of 267�[32m SUCCESS�[39m (15.5 secs / 10.738 secs)
HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 147 of 147�[32m SUCCESS�[39m (3.489 secs / 1.382 secs)
HeadlessChrome 72.0.3626 (Windows 8.1.0.0): Executed 210 of 210�[32m SUCCESS�[39m (18.05 secs / 13.587 secs)
[32mTOTAL: 1797 SUCCESS�[39m]

[d1820]

it turns out vuex and inversify was causing the issues.. we had to refactor all of our tests and hijack resource resolutions with inversify middleware.. now all tests run and parallel def speeds it all up..