Open gsnedders opened 8 years ago
As SVG 2 CR is in the process of being published. I've started to take a look at what we need to do to build the svg 2 test suite. Unfortunately most of the knowledge on W3C testing left the working group so I'm starting mostly from scratch here.
I wouldn't bother importing these tests. We need to rework the existing SVG 1.1 tests that are still relevant, we can look at bringing the tests here that are useful in at the same time. I'll ask active contributors to take care of their own, and I'll look at the remaining (or we'll split them up depending on how many there are).
Feel free to assign this issue to me if you want to hold off on closing it until all tests are in web-platform-tests.
@nikosandronikos I presume they aren't simply duplicates of things in 1.1, therefore I'd assume the tests do have some value!
Unless you're going to actively work on it soon, I'd rather just leave it unassigned, then someone (possibly you!) can pick it up at some point in the future.
@gsnedders Sorry, I'm not saying never import them. I'm just proposing the working group take on the job of importing them while importing the SVG 1.1 tests - as likely both will need reworking into the correct format.
Happy to leave unassigned for now until we have a firm plan in place and have assigned people to pick up particular groups of tests.
The SVG WG has an old abandoned svg2-tests repo at https://svgwg.org/hg/svg2-tests/; given the WG seem to have no interest in maintaining a testsuite currently, we should import them into our
svg
directory for the sake of having a maintained SVG testsuite somewhere.Given the amount of folders that lead to
readme
or.emtpy
files, the files that may or may not be tests in the repo are:It certainly looks like some of those are not tests (being resources like the fonts which may or may not actually be used by any of the tests). Equally, some of them are CSS tests and should go into https://github.com/w3c/csswg-test.