- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Sep 2016 17:24:39 +0000
- To: public-svg-issues@w3.org
I'm really hopeful that we can port any and all existing testing suites to get things up and running for a start. However, we'll also need a specific process of reviewing all these to make sure they match up with specific SVG 2 text (some of which has changed re edge cases), and that all edge cases are covered. This was a big problem with the SVG 1.1 test suite: it wasn't very well connected to the spec. Given that reviews are going to be required, I don't see requiring a template as too big an obstacle. There are a number of SVG-specific metadata we'll need, particularly re which processing modes the results are for (static, animated, scripted, with external files allowed or not), and whether it works for SVG standalone, SVG as inline in XML, and/or SVG inline in HTML. @gsnedders What's your concerns about organizing tests by chapter? We're going to be looking at 1000s of tests, it would be nice to have some sort of structure to them. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/269#issuecomment-247394077 using your GitHub account
Received on Thursday, 15 September 2016 17:24:45 UTC