Yes. Though I also wish implementers read the spec instead of just making all the existing tests pass. And wish more tests linked to specific assertions.
-
-
-
Oh, for sure. In my ideal world, a spec writer writes tests, then implementors write an implementation based on the spec. Any tests they fail, that's probably a spec issue in the sense of the spec being unclear or wrong, if the implementor is competent.
- 1 more reply
New conversation -
-
-
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.
-
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.
- 4 more replies
New conversation -
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.