History

Eric Anderson e085a0eca0 Bump to Gradle 4.7 The new jmh plugin fixes a warning for the newer version of Gradle. The new AppEngine plugin still produces a warning, but updating it anyway so people know that upgrading the plugin doesn't fix the problem. The new android-maven plugin fixes a build problem with the newer Gradle. The Visual Studio fixes were necessary starting ~4.4. https://github.com/gradle/gradle-native/issues/34#issuecomment-335222096 describes the change in behavior. There's nothing immediately being used as part of this update. It's just to keep us current and to get us over that Visual Studio change hump.		2018-05-17 15:46:21 -07:00
..
gae-jdk7	Bump to Gradle 4.7	2018-05-17 15:46:21 -07:00
gae-jdk8	Bump to Gradle 4.7	2018-05-17 15:46:21 -07:00
README.md	gae-interop-testing: add GAE interop tests (#3535 )	2017-10-06 10:44:58 -07:00

README.md

Google App Engine interop tests

This directory contains interop tests that runs in Google App Engine as gRPC clients.

Prerequisites

Install the Google Cloud SDK and ensure that gcloud is in the path
Set up an App Engine app with your choice of a PROJECT_ID.

Associate your gcloud environment with your app:

# Log into Google Cloud
$ gcloud auth login

# Associate this codebase with a GAE project
$ gcloud config set project PROJECT_ID

Running the tests in GAE

You can run the gradle task to execute the interop tests.

# cd into either gae-jdk7 or gae-jdk8
$ ./gradlew runInteropTestRemote

# Or run one of these from the root gRPC Java directory:
$ ./gradlew :grpc-gae-interop-testing-jdk7:runInteropTestRemote
$ ./gradlew :grpc-gae-interop-testing-jdk8:runInteropTestRemote

Optional:

You can also browse to http://${PROJECT_ID}.appspot.google.com to see the result of the interop test.

Debugging

You can find the server side logs by logging into http://appengine.google.com and scrolling down to the section titled Application Errors and Server Errors.

Click on the / URI to view the log entries for each test run.