Yes, each plugin should be responsible for its own tests. This is something that we should practice with the core plugins and encourage with third-party plugins.
I'm still playing catch up, but this is something that must be added to the plugin spec IMO. Michael On Thu, Feb 7, 2013 at 12:48 PM, Filip Maj <f...@adobe.com> wrote: > This is definitely what I had envisioned as well.. > > On 2/7/13 11:13 AM, "Andrew Grieve" <agri...@chromium.org> wrote: > > >If someone wants to lead the charge on this angle of the plugin > >splitting-out, that would be awesome. On the priority list though, I think > >it's pretty low. Right now you have to set up the project file, add the > >JS, and then run the tests. This model will still work when plugins are > >separated out. > > > > > >On Thu, Feb 7, 2013 at 1:21 PM, Marcel Kinard <cmarc...@gmail.com> wrote: > > > >> I don't want to jump forward too far, but would it make sense to breakup > >> mobile-spec in a similar way so that the tests for a plugin are actually > >> located in the plugin's repo? Then the test and the function under test > >> would be synchronized. And it could potentially open the way for > >> third-parties to supply tests for their own plugins. > >> > >> -- Marcel Kinard > >> > >> On Feb 7, 2013, at 10:44 AM, Andrew Grieve <agri...@chromium.org> > wrote: > >> > >> > https://issues.apache.org/jira/browse/INFRA-5839 > >> > >> > >
