- From: Paul Adenot <padenot@mozilla.com>
- Date: Mon, 8 Jun 2015 18:44:22 +0200
- To: Chris Lowis <chris.lowis@gmail.com>
- Cc: Joe Berkovitz <joe@noteflight.com>, Raymond Toy <rtoy@google.com>, Audio Working Group <public-audio@w3.org>
- Message-ID: <CANWt0WpW3nu=rkqe_9qzNW7wxvWY6USbUEGr8_TNfy3V8ydFWA@mail.gmail.com>
Joe, Chris, I've got someone working on importing Blink's test suite into the Gecko test suite, we'll see how it goes. In the meantime, https://dxr.mozilla.org/mozilla-central/source/dom/media/webaudio/test are all the test we have. Running them outside Firefox should be quite simple, just a matter of putting the files SimpleTest.js, SimpleTest.css at the right location, with a standard web server. Some test make use of a "SpecialPowers" API. Most of the time, they can be ignored. I second most of Raymond's questions, and I'll be happy to help people get started on our test suite. Paul. On Mon, Jun 8, 2015 at 5:58 PM, Chris Lowis <chris.lowis@gmail.com> wrote: > Hi Joe, > > The W3C has a test suite which has some basic Web Audio tests in it: > https://github.com/w3c/web-platform-tests/tree/master/webaudio. > > A while ago I wrote a contribution guide, including how to import > tests from the various vendors' own test suites which your intern > might find helpful: > http://blog.chrislowis.co.uk/2014/04/30/testing-web-audio.html > > I am able to review/approve pull requests to the web platform tests > test suite, and off your intern some guidance as to format/style etc. > if helpful. > > Best, > > Chris > > > > > On 8 June 2015 at 16:34, Joe Berkovitz <joe@noteflight.com> wrote: > > Hello Paul, Raymond, > > > > I am following up on our decision at the F2F to try to create a unified > JS > > test suite for Web Audio that will bring together existing tests > contributed > > by the browser vendors, and also expand to include other tests > contributed > > by WG members and the developer community at large. > > > > Noteflight has an intern available that is able to assist with this task, > > starting now. I would very much like to start this person off on > coalescing > > the existing tests from implementations into a single suite that is > runnable > > independent of browser-specific tooling. This can then be checked into a > W3C > > repo alongside the spec. > > > > Of course, we're not seeking to preempt anyone else who wants to do this > > instead :-) I just want to get the ball rolling, and we're ready to help. > > > > What is the best way to get started on this? Can someone from your > > respective teams provide a few representative test samples from Chromium > and > > Mozilla to get going, and then a larger dump later? Or is there a better > way > > to proceed? > > > > Best, > > > > . . . . . ...Joe > > > > Joe Berkovitz > > President > > > > Noteflight LLC > > 49R Day Street / Somerville, MA 02144 / USA > > phone: +1 978 314 6271 > > www.noteflight.com > > "Your music, everywhere" >
Received on Monday, 8 June 2015 16:45:16 UTC