grpc-java/gae-interop-testing
Eric Anderson b06942d63b Use Gradle's version catalog
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.
2022-06-14 14:04:10 -07:00
..
gae-jdk8 Use Gradle's version catalog 2022-06-14 14:04:10 -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.