Twitter | Pretraživanje | |
Boris
I wish spec editors would stop making spec changes without updating the spec's web platform tests in the process...
Reply Retweet Označi sa "sviđa mi se" More
Chris Lilley 3. pro
Odgovor korisniku/ci @bz_moz @zcorpan
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.
Reply Retweet Označi sa "sviđa mi se"
Boris 3. pro
Odgovor korisniku/ci @svgeesus @zcorpan
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.
Reply Retweet Označi sa "sviđa mi se"
Marcos Càceres 3. pro
Odgovor korisniku/ci @bz_moz @zcorpan
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.
Reply Retweet Označi sa "sviđa mi se"
Boris 3. pro
Odgovor korisniku/ci @marcosc @zcorpan
It was a W3C spec, yes. Rookie editor, which is part of what's going on. I'll message you the details offline.
Reply Retweet Označi sa "sviđa mi se"