How to tell if a spec is sufficiently clear: implementations based on the spec, not reverse engineering, interoperate. Most specs aren't.
-
-
Replying to @sleevi_
@sleevi_@rmhrisk@YuryStrozhevsky Mmmm, spec bugs. Filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=26311 … and https://bugzilla.mozilla.org/show_bug.cgi?id=1037501 …2 replies 0 retweets 0 likes -
Replying to @really_bz
@sleevi_@rmhrisk@YuryStrozhevsky Also, webcrypto needs a conformance test suite. If one can be written, given lack of MTI bits. :(1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@sleevi_@YuryStrozhevsky totally agree. We still need mocha tests for PKIjs too.1 reply 0 retweets 0 likes -
Replying to @rmhrisk
@bz_moz@sleevi_@YuryStrozhevsky one of my god was that PKIjs used enough of WebCrypto that it would be useful interop target for the API.2 replies 0 retweets 0 likes -
Replying to @rmhrisk
@rmhrisk@sleevi_@YuryStrozhevsky A conformance test would test all sorts of invalid input, full range of valid input, etc.1 reply 0 retweets 0 likes -
-
Replying to @rmhrisk
@bz_moz@sleevi_@YuryStrozhevsky interop target != conformance test.1 reply 0 retweets 0 likes -
Replying to @rmhrisk
@rmhrisk@sleevi_@YuryStrozhevsky Yes, but I'm interested in conformance tests, not interop targets, for things like the case issue.2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@rmhrisk@sleevi_ Such conformance test will be running just about 5 times - for each browser :)2 replies 0 retweets 1 like
@YuryStrozhevsky @rmhrisk @sleevi_ They would be updated on every spec update and running in browser continuous integration testing.
-
-
Replying to @really_bz
@bz_moz@rmhrisk@sleevi_ In fact I agree that spec dev should be a TDD - test first, spec after. This must be addressed to@sleevi_0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.