On Thursday 2012-08-16 12:31 +0300, Aryeh Gregor wrote: > I think that the above won't make anything much harder for our coders, > but will be a big step forward for web testing -- especially if our > example motivates other browsers to do the same. It needs a little
I agree that this is worth doing. I think the key to making it work is figuring out how to distribute the knowledge effectively in the Mozilla community. This requires educating Mozilla module owners and code reviewers about the testing guidelines for W3C tests. Some of this can be done by written documentation, but some of it, I think, can only be taught through review and feedback cycles. In some cases, this means getting reasonably rapid feedback (from other browser vendors or others involved in W3C testing efforts) on submitted tests so that people at Mozilla who are writing tests can learn, through rapid feedback, what's required of tests submitted to W3C groups. That said, some test reviews in the W3C space tend to be unnecessarily nitpicky. I think we need to be careful to filter the review feedback appropriately for the change requests that are actually motivated by real testing needs, and to push back on the others so that the amount of information that we need to distribute through the Mozilla community is not too large. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla http://www.mozilla.org/ 𝄂 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
