Currently, the automated test system that we have running (derived from Medic) uses only the mobilespec tests. It does not yet use tests collected from the plugins. Its been talked about, but not gone anywhere.
David Kemp On Wed, Sep 25, 2013 at 7:58 PM, Jesse <purplecabb...@gmail.com> wrote: > Yeah, I have pushed some changes to mobile-spec, and when I did I also > copied the tests into the plugin involved. > Until we get the magic test runner happening, I think we just keep > duplicating. > > @purplecabbage > risingj.com > > > On Wed, Sep 25, 2013 at 4:38 PM, Steven Gill <stevengil...@gmail.com> > wrote: > > > We copied over tests into plugins when we first broke them out, but I > don't > > believe they have been updated. > > > > I would say for now to just add the tests to mobile spec, and possibly in > > the future we go all voltron to build mobile spec and keep tests with > their > > corresponding plugins. > > > > > > On Wed, Sep 25, 2013 at 4:22 PM, Joe Bowser <bows...@gmail.com> wrote: > > > > > Hey > > > > > > Right now, I'm working on a weird file issue that requires me to > > > update mobile-spec, but I'm wondering where the tests should live. > > > Should it all keep living in mobile-spec, or is it with the plugins. > > > And if it's with the plugins, will there be scripts to assemble > > > mobile-spec all Voltron style? > > > > > > This came up earlier, but I haven't found any fix that needed a > > > mobile-spec test. (Many that need native testing, like recursive file > > > copy, etc). Any thoughts? > > > > > > Joe > > > > > >
