I've noticed some strange behaviours when testing:

1. Sometimes when one test fails, a lot of unrelated and unmodified tests starts to fail,
2. Changes to one test makes another one fail.

Has anyone else noticed this kind of behaviour?
is this a gulp issue or something related to webqml?
should we consider tests that suddenly fail without any direct changes a failed test, i mean there must be some conditions that trigger it that we havent accounted for?
most recent example is the propertyNamedSignal test. Had to sneak in a fix: 1ae6a8e