mirror of https://github.com/grpc/grpc-java.git
This moves our depedencies into a plain file that can be read and updated by tooling. While the current tooling is not particularly better than just using gradle-versions-plugin, it should put us on better footing. gradle-versions-plugin is actually pretty nice, but will be incompatible with Gradle 8, so we need to wait a bit to see what the future holds. Left libraries as an alias for libs to reduce the commit size and make it easier to revert if we don't end up liking this approach. We're using Gradle 7.3.3 where it was an incubating fetaure. But in Gradle 7.4 is became stable. |
||
|---|---|---|
| .. | ||
| src | ||
| README.md | ||
| build.gradle | ||
| proguard-rules.pro | ||
| start-emulator.sh | ||
| wait-for-emulator.sh | ||
README.md
gRPC Android test App
Implements gRPC integration tests in an Android App.
In order to build this app, you need a local.properties file under this directory which specifies the location of your android sdk:
sdk.dir=/somepath/somepath/sdk
Connect your Android device or start the emulator:
$ ./start-emulator.sh <AVD name> & ./wait-for-emulator.sh
Start test server
Start the test server by:
$ ../run-test-server.sh
Manually test
Install the App by:
$ ../gradlew installDebug
Then manually test it with the UI.
Instrumentation tests
Instrumentation tests must be run on a connected device or emulator. Run with the following gradle command:
$ ../gradlew connectedAndroidTest \
-Pandroid.testInstrumentationRunnerArguments.server_host=10.0.2.2 \
-Pandroid.testInstrumentationRunnerArguments.server_port=8080 \
-Pandroid.testInstrumentationRunnerArguments.use_tls=true \
-Pandroid.testInstrumentationRunnerArguments.server_host_override=foo.test.google.fr \
-Pandroid.testInstrumentationRunnerArguments.use_test_ca=true \
-Pandroid.testInstrumentationRunnerArguments.test_case=all