Re: Testing

On Wed, Jul 3, 2013 at 8:25 AM, Chris Lowis <chris.lowis@bbc.co.uk> wrote:

>
> Robert O'Callahan writes:
>
> > On Wed, Jul 3, 2013 at 11:25 PM, Chris Lowis <chris.lowis@bbc.co.uk>
> wrote:
> >
> >     I'd like us to reuse as many of the tests as possible from Blink and
> >     Gecko, so am planning to copy as many in to the appropriate places
> as I
> >     can. There's going to be some duplication here, I'm sure - and I
> guess
> >     the W3C test suite will tend to cover the happy path rather than any
> >     edge cases or platform-specific issues, but hope fully we can get to
> the
> >     stage where, as discussed at the f2f earlier in the year, the W3C
> test
> >     suite becomes a part of the implementors CI systems.
> >
> >     Any thoughts on that?
> >
> > We probably should start with the W3C testharness.js --- though I'm not
> a huge
> > fan of it myself, we have support for integrating it into our tests at
> Mozilla
> > and I think Blink does too.
>
> Sounds good - the tests I've already written use testharness.js, so I'm
> keen to keep using that. I'm also not a huge fan, but it will help us to
> integrate with the rest of the web platform tests.
>
> > You might want to look at
> http://mxr.mozilla.org/mozilla-central/source/content
> > /media/webaudio/test/webaudio.js to see how Ehsan created a little
> framework
> > for simplifying Web Audio tests, and see if we can build something like
> that on
> > top of testharness.js.
>
> Thanks, I'll take a look!
>

Please let me know if you need help.  Once you port this miniframework
over, we have 20-30 tests right now which you should be able to import
almost verbatim.

Also, are you planning to work on the API tests as well?  It would be very
helpful for us to make sure that we're complying to the Web IDL exposed API.

Thanks!
--
Ehsan
<http://ehsanakhgari.org/>