Re: When it is appropriate to use wpt...

And this, my friends, is why I ask the questions.  Okay - so extra "server"
code goes into wpt-tools.  And tests go into wpt itself.

One thing we are considering is a declarative grammar for some of the
requirements that would be parsed and generate/model some of the tests.
That parsing could be "client-side" or "server-side".  I don't think we
care which.  Historically this has been done either place.  Is there a
preference in this community?  Is there a precedent?  (I HATE breaking new
ground.)

On Thu, Apr 21, 2016 at 5:56 PM, Geoffrey Sneddon <me@gsnedders.com> wrote:

> On Thu, Apr 21, 2016 at 11:50 PM, Shane McCarron <shane@spec-ops.io>
> wrote:
> >
> >
> > On Thu, Apr 21, 2016 at 5:14 PM, Geoffrey Sneddon <me@gsnedders.com>
> wrote:
> >>
> >> From the browser testing side: I was imagining a dummy payment service
> >> (given there's no way we can test against live payment services!) in
> >> wpt-tools.
> >
> >
> > Me too.  Although it might not be in wpt-tools.  I mean, it could be.
> But
> > it could just be in the "test suite" couldn't it?  Or are there
> sandboxing
> > restrictions that mean plugins / extensions to the server.py script
> (pipes)
> > need to be outside of the test suite folder?
>
> The only reason (and IMO good reason) is to be consistent with how we
> deal with everything else which has extra server code, like
> WebSockets.
>
> /Geoffrey
>



-- 
Shane McCarron
Projects Manager, Spec-Ops