Re: SVG at Test The Web Forward

There are a few draft  tests that I made using the old svg template:

     https://dvcs.w3.org/hg/FXTF/file/tip/filters/test/svg

A good start for people at the event would be to create reftests that  
create the equivalent shorthand and longhand filter effect inside an svg  
file, that should be quite possible since most browsers support svg 1.1  
filters. One problem is that that only tests that aspect (that the effect  
is exactly the same), not that the filters actually do what they're  
supposed to, so it's not enough by itself. A possibility might be to do a  
filter reference implementation in canvas by manipulating pixel values, or  
the same with a custom shader. There are problems with both of those ways  
too.

We could also do negative reftests, to say that *something* has to be  
rendered, e.g a rect with a filter has to look different to just the same  
rect without a filter.

Even if we import or reuse the filter tests from SVG 1.1 I don't think the  
coverage there is that great, and the tests there test a bunch of things  
at once.

We have no coverage of filters used on HTML content, so that's another  
thing that would be good to get. It might be possible to use svg files as  
references for simple HTML+filter testcases. It should also be possible to  
do pixelperfect tests for certain filter operations, e.g colormatrix: take  
a photo, draw it with a colormatrix filter to e.g get grayscale or  
something, that should be possible to actually use a PNG reference image  
for.

I would recommend people to constrain the testing to the simple things  
first, filters that don't extend outside the bbox of the shape it's  
applied to, e.g <filter x=0 y=0 width=1 height=1><feColorMatrix  
.../></filter>.
/ed

On Wed, 13 Jun 2012 07:26:16 +0200, Doug Schepers <schepers@w3.org> wrote:

> Hi folks-
>
> Tav, thanks for those tests.  I'm sure I can adapt them to my purposes.
>
> How about filter tests? Ed, do we have some nice simple filter tests  
> they can play with?  And maybe a set of parameters to mess around with?  
> What tests are we missing in coverage for the filters spec?
>
> Thanks-
> -Doug
>
>
> On 6/9/12 10:10 PM, tavmjong@free.fr wrote:
>>
>> 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
>>
>>


-- 
Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed

Received on Wednesday, 13 June 2012 09:08:06 UTC