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 -
We have cases in service worker where the tests didn't quite match the spec. Implementations followed the tests, and now we're having to update the spec to match the tests. Not sure what the solution is other than more review.
4 replies 1 retweet 5 likes -
Replying to @jaffathecake @annevk and
I wanted to have this problem when I was talking about testing years ago. Despite the headache that this is creating, I can't refrain from being happy to have it.
1 reply 0 retweets 0 likes
Oh, this is definitely a better problem to have than not having test infrastructure!
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.