I wish spec editors would stop making spec changes without updating the spec's web platform tests in the process...
-
-
Why we should enforce a “no test? no merge!” rule across all specs via policy. If it was a W3C spec, let me know and I’ll add the template to prevent that in whatever WG is culpable.
2 replies 0 retweets 5 likes -
Even if you add a test if you do not also have an implementation you might not realize other tests are impacted. And even if you suspect they are it can be rather hard to find them all.
3 replies 0 retweets 10 likes -
True. Suggestions? My feeling is that having at least a test and at least one reviewer can help with that problem... so long as the other reviewer knows the tests and spec well. Plus don't merge things without also having one implementation and the promise of a second one.
1 reply 0 retweets 1 like -
For plenty of specs it's not really the case that anyone knows quite what is in the testsuite, especially given plenty of the tests were written and imported from different vendors at different times.
1 reply 0 retweets 1 like
Sure. I'm not asking for "fix all the existing tests"; I'm asking for "add a test that will fail in implementations that have not aligned with this change".
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.