On 1/17/2014, 8:27 AM, Ed Morley wrote:
Hi!
If you've recently fixed an intermittent test failure - please can you
see if the cause was something that should be documented on the best
practices guide:
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Avoiding_intermittent_oranges
The page was last added to in 2011 - I'm keen to see us revive it - once
up to date the sheriffs will be advocating making it recommended reading
for engineer new-hires and reviewers.
That page should be ready to be used for this purpose right now. There
might be things missing on that page, but all of the content on that
page still applies.
> Rather than playing constant
whac-a-mole with intermittent failures, we should prioritise preventing
their introduction in the first place.
Amen to that!
I'm also optimistic that we can use that page as the basis for some
one-off static analysis of our existing tests to find some quick wins
for reducing our orange factor [1].
I once started a project to detect bad usages of timeouts in mochitests
(see bug 649012.) That work was never finished unfortunately because I
ran out of time and steam, but it would be great if someone can revive
that work and shepherd it into the tree.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
