Skip to content

Commit 53373b1

Browse files
author
Jon Wayne Parrott
committed
Update TESTING.md
1 parent c697937 commit 53373b1

File tree

1 file changed

+3
-14
lines changed

1 file changed

+3
-14
lines changed

TESTING.md

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -38,16 +38,6 @@ From the Cloud Console, create a new Service Account and download its json key.
3838
* Run `source testing/resources/test-env.sh`.
3939
* Run `export GOOGLE_APPLICATION_CREDENTIALS=testing/resources/service-account.json`.
4040

41-
If you want to run the Google App Engine tests, you will need:
42-
43-
* The App Engine Python SDK. You can also download it programatically with `gcp-python-repo-tools`:
44-
45-
$ gcp-python-repo-tools download-appengine-sdk <dest>
46-
47-
* Set the `GAE_PYTHONPATH` variable:
48-
49-
$ export GAE_PYTHONPATH=<path your AppeEngine sdk>
50-
5141
### Test environments
5242

5343
We use [nox](https://nox.readthedocs.org/en/latest/) to configure
@@ -78,7 +68,6 @@ invoke nox like this:
7868
When adding a new top-level directory, be sure to edit ``.coveragerc`` to
7969
include it in coverage reporting.
8070

81-
To add new tests that require Google App Engine, please place them in
82-
the ``appengine`` directory if possible. If you place them elsewhere,
83-
you will need to modify ``nox.py`` to make the environments
84-
appropriately run or ignore your test.
71+
To add new tests that require Google App Engine, you must place them in
72+
the ``appengine`` directory so that the py.test fixtures needed for App
73+
Engine are available.

0 commit comments

Comments
 (0)