- From: alancutter <web-platform-tests-notifications@w3.org>
- Date: Tue, 09 Aug 2016 07:39:39 GMT
- To: public-web-platform-tests-notifications@w3.org
This test runs the cross product of animation states and method calls and records the resulting animation state. It makes sense from an implementation stand point to cover this as a way of tracking changes in behaviour, perhaps it makes less sense from a spec testing perspective. Does it sound reasonable to simply split these tests up according to the animation method being called? That way they are scoped to a section of the spec. Also you mentioned "no need to test the `playState`" after calling `cancel()`, I'm not sure I understand the motivation to not have test coverage for the effect of `cancel()` in that instance. View on GitHub: https://github.com/w3c/web-platform-tests/pull/3327#issuecomment-238477261
Received on Tuesday, 9 August 2016 07:39:47 UTC