cr-connect-workflow/config
Dan Funk 503c1c8f18 Allow disabling the Protocol Builder
PB_ENABLED can be set to false in the configuration (either in a file called instance/config.py, or as an environment variable)

Added a check in the base_test, to assure that we are always running tests with the test configuration, and bail out otherwise.  Setting TESTING=true as an environment variable will get this, but so well the correct ordering of imports. Just be dead certain the first file every test file imports is base_test.py.

Aaron was right, and we call the Protocol Builder in all kinds of awful places.  But we don't do this now.  So Carlos, you should have the ability to reuse a lot of the logic in the study_service now.

I dropped the poorly named "study-update" endpoint completely.  We weren't using it. POST and PUT to Study still work just fine for doing exactly that.

All the tests now run and pass with the Protocol builder disabled. Tests that specifically check PB behavior turn it back on for the test, or mock it out.
2020-05-22 14:37:49 -04:00
..
default.py Allow disabling the Protocol Builder 2020-05-22 14:37:49 -04:00
logging_example.py Refactor the stats models, and assure they are very correct across all tests with the workflow api. 2020-05-04 10:57:09 -04:00
testing.py Allow disabling the Protocol Builder 2020-05-22 14:37:49 -04:00
travis-testing.py Allows CORS connections from frontend 2020-05-12 10:43:52 -04:00