Well, for one thing, it's not self-documenting. For the other, unless I'm missing something, we won't notice if an assertion is fixed and replaced with another one.
And yes, catching when an assertion is fixed would clearly be useful, too. Cheers, David On 20/11/14 18:14, L. David Baron wrote: > It's not all that fragile, since most tests don't have known > assertions, so in that vast majority of tests, we have test coverage > of regressions of assertion counts. > > This covers reftests, crashtests, and all mochitests except for > mochitest-browser-chrome (bug 847275 covers doing it there). > > (We should probably make an attempt to go through the tests that > have assertion count ranges including 0, since nothing catches when > those assertions are fixed, and we're missing the test coverage > there.) > > -David > -- David Rajchenbach-Teller, PhD Performance Team, Mozilla
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
