Hi Petr, On Tue, Jun 30, 2015 at 11:02 AM, Petr Shypila <[email protected]> wrote: > ...I think the best way to solve this problem is > to subscribe for BundleEvent.UNINSTALLED event of these bundles....
That might not be sufficient, as I suppose the content loader acts asynchronously, potentially after that event is emitted. To verify that you might add some sleep(...) calls in the content loader, and see if that causes your tests to fail. Another strategy would be just to add some retry loops in your tests, to wait for what you expect to happen (a property being overwritten etc.), with a timeout - that might solve most of those cases. -Bertrand
