These are the webapp2 utilities for the im_futuretest library. If your project uses webapp2, this is the package you want.
[](https://travis-ci.org/emlynoregan/im_futuretest_webapp2)
## Install
Use the python package for this library. You can find the package online [here](https://pypi.org/project/im-futuretest-webapp2/).
Change to your Python App Engine project's root folder and do the following:
> pip install im_futuretest_webapp2 --target lib
Or add it to your requirements.txt. You'll also need to set up vendoring, see [app engine vendoring instructions here](https://cloud.google.com/appengine/docs/python/tools/using-libraries-python-27).
## Configuring im_futuretest_webapp2
This package provides functions that set up webapp2 routes for im_futuretest, both for its api and its ui.
To get your tests running properly, you should add these routes in your main app (wherever your main webapp2 app is constructed). Doing this
ensures that your tests have exactly the same code loaded as the code they're testing would have when being used normally, ie: no dependency hell.
### app.yaml
The futuretest handlers all have routes of the form:
/futuretest/XXX
(where XXX may include more levels of pathing)
Say you already have an app.yaml rule which pushes all routes to your main app, say main.py, as follows:
handlers:
- url: *
script: main.app
Then this will work for futuretest without any modification.
If things are a little messy, you can just add this somewhere early in app.yaml:
- url: /futuretest/*
script: main.app
login: admin
This will direct all futuretest routes to the "app" webapp2 application constructed in main.py. Obviously modify this as needed.
Also note the requirement for the user to be an admin of your project. Futuretest is designed to run potentially long running and expensive
tests; it's best not to open that up to all comers!
### main.py
Now traffic is going to the app constructed in main.py.
Next we need to add futuretest routes to app.
Do it like this:
import webapp2
... other imports ...
routes = [
...
]
...
addroutes_futuretest_webapp2(routes) # this is the important bit, adds required routes
...
app = webapp2.WSGIApplication(routes)
ie: just call addroutes_futuretest_webapp2(app) somewhere in main.py
### Accessing the UI
Go to the url
http(s)://<yourdomain>/futuretest/ui
and you'll see the UI:

Metadata
Release files for im-futuretest-webapp2 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| im_futuretest_webapp2-0.1.1.tar.gz | 3.9 kB | Without provenance | Details for im_futuretest_webapp2-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| im_futuretest_webapp2-0.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for im_futuretest_webapp2-0.1.1-py2.py3-none-any.whl |
Total release size: 10.5 kB
Release files / im_futuretest_webapp2-0.1.1.tar.gz
| Download URL | im_futuretest_webapp2-0.1.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5504465a47582b3cb96948b57ae6aece9fa83fefae14487a49cdb0b5d9f9af54
|
|
BLAKE2b-256 checksum How to use checksums |
32d9ad3646c267797d8fba3b80d1cdcd8d33e721e4ba8f11625b8570de1b17b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / im_futuretest_webapp2-0.1.1-py2.py3-none-any.whl
| Download URL | im_futuretest_webapp2-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7228fb92331cb151385b2453130bbc3adfd4717de882f51f8405c0c6349f7e2b
|
|
BLAKE2b-256 checksum How to use checksums |
f06eb17d4253fe5cd28e142cc130b561e1a23ecbf462b5ca90d635e55839b19c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for im-futuretest-webapp2 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.