Well it *is* a cordova plugin, in the sense that it has a plugin.xml and is managed using cordova plugin add/rm. It also exports js apis: a list of tests, which you can enable/disable, a way to define auto/manual tests, and a way to bootstrap the whole process. It does also ship a full test-harness application which you can optionally set as your start page, but thats just for convenience.
Anyway, I think its pretty plugin-y, more plugin-y than say cordova-plugin-console, I think. However, if we want to reserve "cordova-plugin-*" for device api type things going forward, I'm okay with changing the name -- its just a repo name, totally not a big deal. The package id users use to install from registry wouldn't change. -Michal On Mon, May 12, 2014 at 10:39 AM, Ian Clelland <[email protected]>wrote: > Agreed -- it's nice to be able to filter directory operations on > "cordova-plugin-*" > > > On Mon, May 12, 2014 at 10:38 AM, Josh Soref <[email protected]> > wrote: > > > Michal Mocny wrote: > > >s/cordova-plugin-test-harness/cordova-plugin-test-framework/ -- and I'm > > >totally open to naming suggestions before we get stuck with this. > > > > I'd rather cordova-test-framework-plugins or something > > > > > > Specifically, I do not want *anything* named cordova-plugin-* which is > not > > an actual cordova _plugin_. > > > > >
