I'd like to contribute with integration tests (for Android part) we have and add
them to the release process script (we use gradle/maven/java, so it should be
easy to combine).
Here is the itest workflow
1/ create a cordova app via cli (using to-be-release-version plugin)
2/ build app
3/ start android emulator/connect to real device
4/ deploy ups (or use openshift instance)
5/ install app
6/ execute test
a/ check app is registered
b/ send message
c/ check message is received - various variants (foreground,
7/ cleanup (uninstall, stop, etc)
All but step 1/ are currently automated for Cordova/Android. For iOS is it more
complicated, given the fact you can't test APNs in simulator.
On Tue, 1 Apr 2014 09:54:32 +0200
Erik Jan de Wit <edewit(a)redhat.com> wrote:
Because the release process for cordova plugins has a lot of steps and
because it’s a source distribution I would like to suggest an automated
process for releasing and testing the plugins.
What I would like to suggest is that we create a gradle script (for instance
can be something else) that will execute the tests, merge the development
branch create a tag and publish to plugins.cordova.io. I’ve already
experimented with it a bit and it seems very doable.
So what do you think?
aerogear-dev mailing list