Disconnect timeouts occurring for multiple executors - OK for single executor about karma-parallel

[jamesopti]

I believe I'm onto the root cause here.

Sharding tests out across many executors means that any side effects that one test may be relying on from another (such as lazy loading a module) may not be guaranteed to have happened.

This re-enforces the correct practice of ensuring your test can run in isolation and dont rely on other imports.

Will confirm once I've fully investigated.

[joeljeske]

Interesting. Yes each test must setup its own dependencies.

I have had difficulty in migrating some of our projects to use this sharding mechanism because it reveals how some of our tests were initially written incorrectly. There is not much to do about it but try to enforce good habits on your team of always setting up your environment before each test and cleaning it up after.

[joeljeske]

@jamesopti Did you confirm that test independence was the root issue here?

[joeljeske]

Closing due to inactivity