- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Jun 2018 10:51:23 +0000
- To: public-webauthn@w3.org
There are already a bunch of tests in https://github.com/web-platform-tests/wpt/commits/master/webauthn, and when changing the spec the risk is that the tests end up being wrong, contradicting the spec. In the worst case, implementers won't even notice, and will match the tests instead of the spec. The objective here is not testing as such, but reaching interoperability on spec changes faster. I don't know if there are special testing challenges for webauthn, but experience from other groups suggests that progress is faster even though there is more up-front work. I think a reasonable minimum bar is that when normative spec changes are made that *aren't* reflected in tests, then an issue is filed to keep track of that. Or some other mechanism that helps ensure that changes aren't just silently forgotten, which tends to happen when the spec changes arent't closely followed by all implementers and there's nothing else to serve as a reminder of the required implementation change. But, it's ultimately up to the people doing the work, I am merely suggesting a workflow that I think would work. -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/webauthn/pull/653#issuecomment-398707785 using your GitHub account
Received on Wednesday, 20 June 2018 10:51:27 UTC