[heycam/webidl] Testing (#520)

So, I'd like to adopt a process where we mandate tests for normative changes to the spec.

The problem is that most of the things that we're able to test must be done through testing actual concrete interfaces found in other specs. Which thus most often already have their own test suites.

For example, I just added a bunch of tests for the "is an array index" abstract operation in https://github.com/w3c/web-platform-tests/pull/9446, only to be advised in duplicated the tests found in https://github.com/w3c/web-platform-tests/pull/9303.

I'm not too sure what the solution is for this.

Should we track test suites via annotation in the spec? Should we not care and allow for duplicates? should be give-up mandating tests for normative changes in WebIDL?

What are your suggestions here?

Tagging a bunch of folks which might have an opinion about this: @annevk, @foolip, @tabatkins, @domenic, @TimothyGu, @marcoscaceres.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/520