Archana, you can take a look at the script, its pretty easy to read. The TLDR; is that it: - sets up environment (plugin search paths, platform paths in config.json) - creates a new cordova app linking to mobile-spec/www/ and copies over a config.xml (actually, this step could be simplified now that config.xml import works) - adds platforms - add a "dependency" plugin. This is optional, you can just install all cordova plugins yourself. - The new bit: looks for the existence of all `plugins/*/tests/plugin.xml` and installs all those. Those are plugin tests. - Updates cordova.js (pretty sure this is optional much of the time, since changes there are few)
Its probably in your best interests to just get the script to work for your platform/environment, though! If you do use the script, cordova-plugin-test-framework is automatically installed as part of the "dependency" plugin, so you shouldn't need to clone it explicitly (its part of the coho plugin set). Regarding buttons on mobile-spec, yeah they should be removed if the tests have been ported. I didn't even notice the tests land (was waiting for CI to be fixed for new-style tests, which you can now find at http://ci.cordova.io/). -Michal On Tue, Aug 12, 2014 at 6:23 PM, Archana Naik <[email protected]> wrote: > Hi, Martin > > Another problem i have is using createmobilespec module. I am testing > mobilespec on amazon-fireos platform and script doesn't work for me. So i > create mobilespec manually. Hence, its quite broken and most tests are not > working. Are you familiar with createmobilespec.js? > > Archana > > > On Tue, Aug 12, 2014 at 2:55 PM, Archana Naik <[email protected]> > wrote: > > > Cool. Thank you Martin. I will clone plugin-test-framework and try it > out. > > > > One question: I see mobilespec's main page still has other buttons for > > some the tests that were removed. Dont we want to remove those from > > index.html? > > > > Archana > > > > > > On Tue, Aug 12, 2014 at 2:43 PM, Martin Gonzalez < > > [email protected]> wrote: > > > >> Hi Archana, > >> The recent changes in mobile spec are aimed to use cordova > >> plugin-test-framework. > >> plugin-test-framework brings a new style, usage of jasmine 2.0, and > >> several > >> other features (https://github.com/apache/cordova-plugin-test-framework > ). > >> > >> All tests were moved to its respective plugin, and ported to Jasmine > 2.0. > >> Some features: > >> -No spies. > >> -timeouts(minimum). > >> -Process error callback or unexpected success callbacks instead of > called > >> spies. > >> -Jasmine report with more information about the failed operation, which > >> contains the operation and a description about it. > >> -Jasmine reports include error callback object. > >> > >> Old tests were removed. > >> > >> createmobilespec module, it contains the changes to use this new style > and > >> process the plugin-test-framework workflow, to access to "New-Style > >> Tests", > >> use the first button on the mobilespec project created using the module. > >> createmobilespec usage remains the same ( > >> https://github.com/apache/cordova-mobile-spec). > >> > >> > >> > >> > >> 2014-08-12 16:01 GMT-05:00 Archana Naik <[email protected]>: > >> > >> > Hi, Devs > >> > > >> > Recently, I noticed mobilespec has gone through changes and want to > know > >> > whats the new workflow to test all the plugins? Can someone please > >> > summarize? > >> > > >> > Thanks > >> > Archana > >> > > >> > >> > >> > >> -- > >> Regards, > >> Martin Gonzalez > >> > > > > >
