infrastructure/blender-id
0
4
Fork 0
Code Issues 11 Pull Requests Projects Releases Wiki Activity
20240826-085506
blender-id/integration_tests
History
Sybren A. Stüvel 710b0d4d51 Changed Cloud address in fixture and README to http://cloud.local:5001/
2018-07-11 12:41:30 +02:00
..
abstract_bid_test.py Adjusted integration test for 401/403 difference in old/new Blender ID 2017-11-14 11:06:20 +01:00
callbackhtml.py Nicer error msg in test HTTP server 2017-11-10 18:33:07 +01:00
callbackserver.py Nicer error msg in test HTTP server 2017-11-10 18:33:07 +01:00
README.md Changed Cloud address in fixture and README to http://cloud.local:5001/ 2018-07-11 12:41:30 +02:00
setup.cfg Integration tests: short tracebacks 2018-02-14 13:01:02 +01:00
test_addon_behaviour.py Require client ID in /u/validate_token 2018-02-21 11:18:43 +01:00
test_canary.py Added some integration tests. 2017-11-07 12:11:57 +01:00
test_oauth_flow.py Require client ID in /u/validate_token 2018-02-21 11:18:43 +01:00

README.md

Blender ID Integration Tests

These tests are made to run against a live server; this can be either production, test, or development server).

Setting up & running

The tests require the following environment variables:

  • BLENDER_ID_ENDPOINT: the URL of the Blender ID server under test. For example http://id.local:8000/ for a typical dev server.
  • BCLOUD_SERVER: the Blender Cloud server, used for sending subclient tokens. For example http://cloud.local:5001/ for a typical dev server.

The following environment variables are optional and provide extra convenience:

  • BLENDER_ID_UNAME: valid username for login/token creation/revocation etc. tests. If not given, the test will prompt for it.
  • BLENDER_ID_PASSWD: valid password for said tests. If not given, the test will prompt for it. Note that using this environment variable is convenient but may also be a security leak (since any process can inspect other processes' environment variables).

The tests can be run using py.test integration_tests, or cd integration_tests; py.test.

The -s option prevents capture of stdin/out and is required as some tests require user interaction; this option is passed automatically to Py.Test when it's run as described above, due to its inclusion in integration_tests/setup.cfg.