grpc-java/gae-interop-testing
Eric Anderson 0ff9f37b9e Use Gradle's task configuration avoidance APIs
This can avoid creating an additional 736 tasks (previously 502 out of
1591 were not created). That's not all that important as the build time
is essentially the same, but this lets us see the poor behavior of the
protobuf plugin in our own project and increase our understanding of how
to avoid task creation when developing the plugin. Of the tasks still
being created, protobuf is the highest contributor with 165 tasks,
followed by maven-publish with 76 and appengine with 53. The remaining
59 are from our own build, but indirectly caused by maven-publish.
2022-07-08 12:16:40 -07:00
..
gae-jdk8 Use Gradle's task configuration avoidance APIs 2022-07-08 12:16:40 -07:00
README.md doc: Change http to https for security links 2019-02-27 17:25:42 -08: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 gae-jdk8
$ ../../gradlew runInteropTestRemote

# Or run one of these from the root gRPC Java directory:
$ ./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.