- From: Raymond Toy <rtoy@google.com>
- Date: Thu, 25 Jun 2015 08:49:20 -0700
- To: Joe Berkovitz <joe@noteflight.com>
- Cc: Audio Working Group <public-audio@w3.org>
- Message-ID: <CAE3TgXH2YZOOSDKNXwvxiq8i6UWD-b0iSC-g1gdJ6Mj5eeXnag@mail.gmail.com>
On Thu, Jun 25, 2015 at 6:18 AM, Joe Berkovitz <joe@noteflight.com> wrote: > Hi group, > > Noteflight's summer intern Daniel Shaar has been working on coalescing the > Chrome and Moz tests into the W3C suite. He's made excellent progress and > reports he is now able to run all the tests as part of a unified suite > which includes the original sparse set of W3C test cases. He was able to > set up the environment (with a bit of mocking for Mozilla) so that > everything runs without modification. Daniel will give us a quick update > on the next telcon. > Is it possible to get a snapshot of what he's done? I'd like to see it (but won't be able to do anything for several weeks.) > > But a couple of questions came up that perhaps folks (particularly > implementors) will have opinions on: > > - What would be the optimal directory organization for the test suite? A > natural breakdown would be by Web Audio interface name, but... > > - Pulling us in the opposite direction, however, is the convenience of > grouping the original Chrome/Mozilla tests together in their own trees > (since they currently require their own test framework libraries and > resources). Moving to a unified organization would probably involve > migrating the Chrome/Mozilla test cases to use a single standard framework. > Which is perhaps a Good Thing. > > What do people think? > I don't think Chrome has any constraints on the directory layout. The biggest constraint is that they continue to run with the infrastructure that is used by our commit bots and try bots. > > . . . . . ...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 Thursday, 25 June 2015 15:49:48 UTC