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

Re: SVG at Test The Web Forward

From: <tavmjong@free.fr>
Date: Sun, 10 Jun 2012 04:10:05 +0200 (CEST)
To: Doug Schepers <schepers@w3.org>
Cc: SVG WG <public-svg-wg@w3.org>
Message-ID: <1250875700.130742397.1339294205960.JavaMail.root@zimbra44-e7.priv.proxad.net>

Hi Doug and WG,

I have some tests in my area of the HG repository that might serve as examples. They compare CSS styling vs. using attributes for CSS3 Transforms. I think these tests are good examples as they will work in automated testing yet when viewed manually indicate what is being tested and show the expected results. The tests can be seen at:

http://tavmjong.free.fr/SVG/svg2-tests/contributors/tavmjong/incoming/

The first three tests are ones that I wrote, The fourth is one of the CSS tests from Adobe that I converted from an SVG in HTML test to a standalone SVG test. I prefer my tests to the Adobe tests as it is not clear from just looking at the Adobe test what it is testing. (BTW, I have a script that converts the hundreds of Adobe SVG in HTML tests to stand-alone SVG tests. I will try get them uploaded in the next few days.)

Tav

----- Mail original -----
De: "Doug Schepers" <schepers@w3.org>
À: "SVG WG" <public-svg-wg@w3.org>
Envoyé: Vendredi 8 Juin 2012 22:30:04
Objet: SVG at Test The Web Forward

Hi, SVG WG-

As you know, I'm presenting at Adobe's Test the Web Forward event next 
Friday.

There are over 120 people attending this event, who will be there to 
help make tests for W3C specs.  It's a great idea.

I just had a call with Peter Linss and Chris Lilley about the test 
framework and what my presentation should feature.

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).

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, 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.

Do people like this approach? If so, what tests should I use as 
templates, and what variations should I suggest?


Thanks-
-Doug
Received on Sunday, 10 June 2012 02:10:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 10 June 2012 02:10:38 GMT