GitHub user filmaj opened a pull request:
https://github.com/apache/cordova-android/pull/392
WIP: Run native android unit tests in CI
Still a work in progress, let's see how appveyor and travis react to this.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/filmaj/cordova-android ci-native-tests
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-android/pull/392.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #392
----
commit 90053eb9dfc03c6cdab31aab665324556c3358be
Author: filmaj <[email protected]>
Date: 2017-06-27T17:02:38Z
CB-12950: lots of tweaks for end-to-end test runs, especially on CI:
- rename npm tasks to reflect what they do (npm run unit-tests, npm run
e2e-tests). main `npm test` runs linter, unit tests and e2e tests now.
- locked jasmine down to ~2.6.0.
- consolidate gitignores.
- updated travis to run `npm test`. add android sdk installation to
appveyor ci run.align android dpendencies across travis and appveyor. have
appveyor install gradle. force gradle to version 3.4.1 in appveyor, as that
seems to be the only version choco has. explicitly invoke sdkmanager to move
license accepting process along.
commit 8ec72bee4af733ca049d59d18913ddb58913c770
Author: filmaj <[email protected]>
Date: 2017-06-27T22:37:07Z
try to run native unit tests in both travis and appveyor.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]