- From: Cameron McCormack <cam@mcc.id.au>
- Date: Thu, 20 Dec 2012 11:54:32 +1100
- To: Dirk Schulze <dschulze@adobe.com>
- CC: Erik Dahlstrom <ed@opera.com>, "public-svg-wg@w3.org" <public-svg-wg@w3.org>
On 20/12/12 11:50 AM, Dirk Schulze wrote: >> Would we be able to talk briefly about the test suite? I would like to >> form a plan of attack for, at least, migrating the SVG 1.1 test suite to >> the new repository, because it's probably not going to happen by itself. > > Not sure if we should do that. The SVG 1.1 test suite is not compatible with the requirements of the new test suite (ref tests or js tests) Maybe instead of "migrate" I should have said "port". Unless you think we need to write completely new tests because there is something about how the current ones are formulated that isn't compatible (aside from the metadata/structure)? >> :) Also, I was asked recently if we have a place to put testharness.js >> tests as somebody was going to contribute a couple. We don't think we >> have any yet -- where in the svg2-tests repo should we put them? >> > > There should not be any need for a special hierarchy. Just do the same as for the ref tests. Shepherd or the created test suite should add the required libraries on there own. Does testharness.js run under Shepherd? I had the impression that it was a separate thing.
Received on Thursday, 20 December 2012 00:55:07 UTC