Re: [w3c/clipboard-apis] Make all clipboard events composed by default. (#62)

Hi all,

This quarter @rakuco and I have been looking into a [normative spec change without tests](https://docs.google.com/document/d/1kFYTqUMEbo9p87i6wAzORoicMWgHsuYwL2CgtvdhDaE/edit#heading=h.gn90gr74sg9s) to help us understand how [testing in standards](https://github.com/foolip/testing-in-standards) is working out in practice, and where there's more infrastructure work needed to make it practical.

This week I ended up here, and I think https://github.com/w3c/clipboard-apis/pull/58 and https://github.com/w3c/clipboard-apis/commit/11619a7 (no PR?) might also be testable, but less obviously so.

It looks like there weren't any tests for any events at all in https://github.com/w3c/web-platform-tests/tree/master/clipboard-apis, presumably because they'd have to be manual. To convince myself it's possible, I wrote a manual test that exercises this change:
https://github.com/w3c/web-platform-tests/pull/9626 (review appreciated)

Question for everyone here: what automation bits would you need in https://w3c.github.io/webdriver/webdriver-spec.html and exposed in http://web-platform-tests.org/writing-tests/testdriver.html to be able to reliably test changes to this spec? If you could file an issue on the web-platform-tests repo and add the type:untestable label, that'd be much appreciated.

In the meantime, do you think that writing manual tests is worthwhile? Is there any useful advice that should go in https://github.com/w3c/clipboard-apis/blob/master/CONTRIBUTING.md#tests?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/pull/62#issuecomment-367589357