3 ms·

Here is Mozilla's list of common causes for flaky Firefox tests (aka "intermittent oranges"): https://developer.mozilla.org/en-US/docs/Mozilla/QA/Avoiding_inte

• raverbashing 8y ago
  Those are interesting but very JS centric (though some principles apply regardless) Of the tests I've seen, one usual source of flakyness is ignored side-effects between tests (DB is not emptied, some source of persistence is not reset - could be a 'global' variable or a mock library not mocking things correctly), sometimes import conflicts (some module clashes with a builtin library, but if you do this in a certain order it works) Other sources include people using the equivalent of "now()" but then you're on those small time periods where your assumptions break (for example, now() is the last day of the year and you're assuming tomorrow is still in the same year, things like that)