On 11/20/2012 6:11 AM, Randell Jesup wrote:
This does mean almost all tests should be mochitests. That's not a bad thing, it's a good thing! But the bigger takeaway is that tests should start with functionality (as the feature is useless without that), then add general stressors (create/destroy fast, create a lot, evil arrangements, obvious edge cases, etc), then (especially as code matures and stabilizes) add very specific tests.
One addendum: another high-priority test type (perhaps right after broad functionality tests) are broad touch-all-the-API-points tests, which again protect us from regressions of the API and serve to help verify what we've implemented.
-- Randell Jesup _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
