W3C home > Mailing lists > Public > public-svg-wg@w3.org > April to June 2012

Re: SVG at Test The Web Forward

From: Dirk Schulze <dschulze@adobe.com>
Date: Sat, 9 Jun 2012 20:11:40 -0700
To: Cameron McCormack <cam@mcc.id.au>
CC: Doug Schepers <schepers@w3.org>, SVG WG <public-svg-wg@w3.org>
Message-ID: <4B11986C-C77F-4F5E-8342-A77A447A5C4C@adobe.com>

On Jun 9, 2012, at 7:32 PM, Cameron McCormack wrote:

> Doug Schepers:
>> I just had a call with Peter Linss and Chris Lilley about the test
>> framework and what my presentation should feature.
> Did you discover what work needs to be done to get Shepherd working with 
> our repository?  I can spend some time this coming week to get that up 
> and running if I know what needs to be done.
Peter Linss asked for help of one of the admins of our mercurial testing repo. He would like to help setting it up. Can you talk with Peter Linss, Cameron?

>> We agreed that since most people aren't as familiar with SVG as with
>> CSS, the most likely tests we will get them to contribute are those that
>> are shared between SVG and CSS, such as the FX TF deliverables
>> (specifically Filters, Transforms, and Compositing, and maybe Animation
>> and Transitions), and CSS features as applied to SVG rather than HTML
>> (e.g. opacity and HSLA, and so on).
> That sounds fair enough.  I wonder which repository these tests should 
> live in?  If not the svg2-tests repo, then perhaps it is not as 
> important for us to have that up and running for the event.  (I don't 
> know if the FXTF has a dedicated test suite repo.)
It absolutely depends. At the end they will live as HTML tests in the CSS test suite and as SVG tests in the SVG test suite I guess.

>> We thought that the best outcome might be for us to provide 5-10 good
>> examples of tests we want, for use as templates, and ask them to help
>> iterate on those, along the lines of a set of features they could test.
>>  So, maybe we make 2-3 good Filters examples, and ask them to extend
>> those to other filter types,
A great idea!

>> or we make a scale transform test, and
>> suggest that they do similar ones for translate, rotate, skew, and so
>> on, or variations on different values.
I am not so sure if we should ask for tests for the SVG test suite. We definitely have Transforms as topic for this event. And Transforms for SVG is definitely part of this topic. But I would like to write the SVG tests with inline SVG in HTML and use Tav's script to convert all these tests to pure SVG tests afterwards. Actually most of the >600 tests for CSS3 Transforms are testing the behavior for SVG already.

> Great idea!
>> Do people like this approach? If so, what tests should I use as
>> templates, and what variations should I suggest?
> I guess the problem is that we have very few tests currently in the 
> svg2-tests repository to copy from, and that that is because we don't 
> have Shepherd running yet. :)
No, I assume it is the same problem like for editing the spec. The lack of time. Hopefully not a lack of interests, since testing is extremely important. That was/is one of the biggest issues of the current test suite. We don't have enough tests, we don't have enough detailed tests and we don't have tests that can easily be run automatically by any UA.

Received on Sunday, 10 June 2012 03:12:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:14 UTC