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 -
Sure, but in this case the spec change was accompanied by absolutely no tests... Solving this problem perfectly is hard, I agree. Doing at least something so people will notice the spec change and have some idea of whether they have changed their code to match is not that hard.
1 reply 0 retweets 1 like -
I see, if W3C I believe
@plhw3org is gradually making progress on that front, but not sure where it’s at organization-wide. Maybe this is also something@davidbaron should push on during charter review.2 replies 0 retweets 1 like -
We also need to do something on the Mozilla side where we notice new/changed tests that fail, in areas where we would expect tests to pass.
3 replies 0 retweets 1 like
Yes, we do.... It keeps getting deferred....
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.