| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [View Raw Code] [Original HTTPS Page] |
The tests in this repository are system tests and run against live services, therefore, it takes a bit of configuration to run all of the tests locally.
Before you can run tests locally you must have:
The latest nox, pip, and gcp-python-repo-tools installed.
$ sudo pip install --upgrade nox-automation
The Google Cloud SDK installed. You can do so with the following command:
$ curl https://sdk.cloud.google.com | bash
Running the complete suite may require system dependencies. Most of these should be installable via typical package managers like apt-get and brew.
For example, to install portaudio:
brew install portaudio
If you have trouble installing a necessary system library, try filing an issue.
See speech/api/README.md.
Most tests require you to have an active, billing-enabled project on the Google Cloud Console.
Some resources need to be created in a project ahead of time before testing. We have a script that can create everything needed:
gcloud config set project <your-project-id> scripts/prepare-testing-project.sh
The script will also instruct you to follow a URL to enable APIs. You will need to do that.
From the Cloud Console, create a new Service Account and download its json key. Place this file in testing/resources/service-account.json.
Create a new OAuth client ID. Create a file testing/resources/client-secrets.json and write the client_id and client_secret to the file in the Client Secrets JSON format.
We use nox to configure multiple python sessions:
To see a list of the available sessions:
nox -l
To run tests for a particular session, with a particular parameter, invoke nox with the -s flag:
nox -s "tests(interpreter='python2.7')"
To run one particular session or provide additional parameters to py.test, invoke nox like this:
nox -s tests -- storage/api
When adding a new top-level directory, be sure to edit .coveragerc to include it in coverage reporting.
To add new tests that require Google App Engine, you must place them in the appengine directory so that the py.test fixtures needed for App Engine are available.
| Back | FazBrowse Home | New Git URL |