On Fri, Sep 5, 2014 at 8:23 PM, James Graham <ja...@hoppipolla.co.uk> wrote: > I think Ms2ger has a better answer here, but I believe it obsoletes most > of them, except a few that never got submitted to web-platform-tests > (the editing tests are in that class, because the spec effort sort of died).
FWIW, the editing tests are still very useful for regression-testing. They often catch unintended behavior changes when changing editor code, just because they test quite a lot of code paths. I think it would be very valuable for web-platform-tests to have a section for "tests we don't know are even vaguely correct, so don't try to use them to improve your conformance, but they're useful for regression testing anyway." That might not help interop, but it will help QoI, and it makes sense for browsers to share in that department as well. (This is leaving aside the fact that the editing tests are pathologically large and should be chopped up into a lot of smaller files. I have a vague idea to do this someday. They would also benefit from only being run by the Mozilla testing framework on commits that actually touch editor/, because it's very unlikely that they would be affected by code changes elsewhere that don't fail other tests as well. I think.) _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
