- From: Kristijan Burnik <web-platform-tests-notifications@w3.org>
- Date: Fri, 09 Sep 2016 16:30:47 GMT
- To: public-web-platform-tests-notifications@w3.org
One does not necessarily need to add a lot of tests. Even a single test can be generated by a single spec.json rule. The generating framework allows for suppressing (excluded_tests) or specifying explicit scenario values (i.e. other than * expansion). It's up to you if you choose to be more general/specific or prefer whitelisting to blacklisting. :-) This is all documented here: https://github.com/w3c/web-platform-tests/blob/master/referrer-policy/README.md On Sep 9, 2016 3:20 PM, "Mike West" <notifications@github.com> wrote: > I apologize; I didn't get back to this right away, and then it fell off my > radar completely. > > I think the approach is reasonable in the short term, but, as you note, > adds a lot of tests. Since we should probably be doing srcdoc tests (and > iframe@sandbox tests, etc) for resource types other than images, perhaps > it makes sense to extend the general test framework to coalesce these new > tests into the existing subresource tests without adding a few hundred new > tests. > > I don't think it's fair to ask you to do that refactoring after ~4 months, > though, so I've uploaded a pass at it to https://github.com/w3c/web- > platform-tests/tree/referrer-policy. WDYT? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/web-platform-tests/pull/2851#issuecomment-245910439>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AHmrGawHtd6UwUCLrVw9N3xwCwWzoDm5ks5qoV0HgaJpZM4ILVdx> > . > View on GitHub: https://github.com/w3c/web-platform-tests/pull/2851#issuecomment-245965852
Received on Friday, 9 September 2016 16:30:55 UTC