public/cordova-android
public/cordova-android
9
0
Fork 0
forked from github/cordova-android
Code Pull Requests Activity

improve test readme (#582)

Browse Source 
<!--
Please make sure the checklist boxes are all checked before submitting the PR. The checklist
is intended as a quick reference, for complete details please see our Contributor Guidelines:

http://cordova.apache.org/contribute/contribute_guidelines.html

Thanks!
-->

### Platforms affected


### What does this PR do?


### What testing has been done on this change?


### Checklist
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html) in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
- [ ] Added automated test coverage as appropriate for this change.
This commit is contained in:
Jan Piotrowski 2018-12-04 20:38:31 +01:00 committed by GitHub
parent 8a4ae311ce
commit 5f44af3757
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
test/README.md
View File

@ -22,7 +22,7 @@
# Cordova Android Test Project # Cordova Android Test Project
The project in this directory is an Android Test project that enables those The project in this directory is an Android Test project that enables those
interested in further developing cordova-android to validate their changes. interested in further developing `cordova-android` to validate their changes.
## Requirements ## Requirements
@ -33,7 +33,7 @@ writing) at least version 3.3 or newer.
## Getting Started ## Getting Started
You can run this test project from both the command line as well as from You can run this test project from both the command line as well as from
Android Studio. Android Studio:
### Command Line ### Command Line
@ -50,8 +50,10 @@ 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 environment to run in, but the instrumented tests, however, require a connected
Android device or emulator to run in. Android device or emulator to run in.
To run the unit tests, run: `gradlew test`. - To run the unit tests, run: `gradlew test`.
To run the instrumented tests, run: `gradlew connectedAndroidTest`. - To run the instrumented tests, run: `gradlew connectedAndroidTest`.
To make sure all tests are run, add the `--rerun-tasks` parameter.
### Android Studio ### Android Studio