fd57909730
* chore: added execa dependency Co-authored-by: Raphael von der Grün <raphinesse@gmail.com> * chore: execa - drop superspawn in android_sdk Co-authored-by: Raphael von der Grün <raphinesse@gmail.com> * chore: execa - drop superspawn in build * chore: execa - drop superspawn in check_reqs Plus: Remove useless trimming of execa output Co-authored-by: Raphael von der Grün <raphinesse@gmail.com> * chore: execa - drop superspawn in emulator Co-authored-by: Raphael von der Grün <raphinesse@gmail.com> * chore: execa - drop superspawn in device Co-authored-by: Raphael von der Grün <raphinesse@gmail.com> * chore: execa - drop superspawn in run_java_unit_tests * chore: execa - drop superspawn in ProjectBuilder Co-authored-by: Raphael von der Grün <raphinesse@gmail.com> * chore: execa - drop superspawn in adb * chore: execa - drop superspawn in plugin.spec * chore: execa - replace child_process in log * chore: execa - replace child_process in check_reqs * chore: execa - replace child_process in emulator Co-authored-by: エリス <erisu@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| app | ||
| build.gradle | ||
| gradle.properties | ||
| README.md | ||
| run_java_unit_tests.js | ||
| settings.gradle | ||
| wrapper.gradle | ||
Cordova Android Test Project
The project in this directory is an Android Test project that enables those
interested in further developing cordova-android to validate their changes.
Requirements
The requirements in the top-level README still apply. In addition, ensure you have installed Gradle, and that it is (at the time of this writing) at least version 3.3 or newer.
Getting Started
You can run this test project from both the command line as well as from Android Studio:
Command Line
Ensure you have the gradle wrapper script, gradlew, in this directory. If
you do not, you can run the following to generate it:
$ cd cordova-android/test
$ gradle :wrapper -b build.gradle
You can then see a list of all tasks available to run with gradlew tasks.
The two different kinds of tests one typically wants to run are unit tests and end-to-end, or instrumented, tests. Unit tests do not require any particular environment to run in, but the instrumented tests, however, require a connected Android device or emulator to run in.
- To run the unit tests, run:
gradlew test. - To run the instrumented tests, run:
gradlew connectedAndroidTest.
To make sure all tests are run, add the --rerun-tasks parameter.
Android Studio
Import this test/ directory into Android Studio, and hit the Play button.