cr-connect-workflow/tests
Carlos Lopez 4727d87adb Hooking up emails into process - start 2020-06-04 20:37:28 -06:00
..
data Run the validation twice, once completing all of the data, and a second time, completing only the required fields. 2020-05-30 17:26:27 -04:00
__init__.py Lots and lots of random stuff as I organize code and get things to make sense. 2019-12-18 14:02:17 -05:00
base_test.py Hooking up emails into process - start 2020-06-04 20:37:28 -06:00
test_approvals_api.py Doing everything I can imagine to get a CSV dump out tomorrow. 2020-06-02 22:01:49 -04:00
test_approvals_service.py Hooking up emails into process - start 2020-06-04 20:37:28 -06:00
test_authentication.py Merge branch 'feature/support_ui_dashboard' into dev 2020-05-25 21:31:16 -04:00
test_complete_template_script.py Assure that new lines entered in text-fields are correctly added to the final word document. 2020-05-18 11:55:10 -04:00
test_file_service.py Ludicrously stupid launch in a refactor of the way all files work in the system at a time where I crave sleep and peace above all other things. 2020-05-28 20:03:50 -04:00
test_files_api.py Ludicrously stupid launch in a refactor of the way all files work in the system at a time where I crave sleep and peace above all other things. 2020-05-28 20:03:50 -04:00
test_ldap_service.py For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". 2020-06-02 18:17:00 -04:00
test_lookup_service.py Committed a stupid. 2020-05-29 15:20:22 -04:00
test_mails.py Hooking up emails into process - start 2020-06-04 20:37:28 -06:00
test_protocol_builder.py Protocol Builder isn't disabled on the dcos servers, trying to figure out why, and assure it isn't some sort of weird race condition. 2020-05-26 22:42:49 -04:00
test_request_approval_script.py Don't add an empty approval record. 2020-06-02 08:35:19 -04:00
test_study_api.py Fixing broken test by using proper FileSchema 2020-05-31 22:00:52 -06:00
test_study_details_documents.py As we now have an approval_service.py, I moved all the business logic into this service and out of the request_approval.py script. And moved all tests for these features into a test file for the service. Will make it easier to cross reference what is happening, as everything all happens in one file. 2020-05-24 16:13:15 -04:00
test_study_service.py Ludicrously stupid launch in a refactor of the way all files work in the system at a time where I crave sleep and peace above all other things. 2020-05-28 20:03:50 -04:00
test_tasks_api.py Tweaks to approvals 2020-06-01 21:49:30 -04:00
test_tools_api.py On the tools/render_docx api, allow sending the json data in the body, rather than as a ludicrous long get parameter. Silly Dan. 2020-05-22 15:30:22 -04:00
test_update_study_script.py Adding an "UpdateStudy" task that is able to update the data on the study model, useful for setting core data points on the model, such as setting the Primary Investigator, or altering the Study Title. 2020-05-25 15:30:06 -04:00
test_workflow_processor.py Run the validation twice, once completing all of the data, and a second time, completing only the required fields. 2020-05-30 17:26:27 -04:00
test_workflow_processor_multi_instance.py the heck with camel case, what the heck TypeScript? Get a grip. This is a python API. 2020-05-15 16:38:37 -04:00
test_workflow_service.py Run the validation twice, once completing all of the data, and a second time, completing only the required fields. 2020-05-30 17:26:27 -04:00
test_workflow_spec_api.py I absolutely must fix our cascade deletes, but I sort of like the horror such chunks of code cause, we really need to protect these endpoints, and assure they never get called under normal circumstances, and raise some thoughtful errors. 2020-05-26 21:18:09 -04:00
test_workflow_spec_validation_api.py Run the validation process twice, each time it is requested, first populating everything, and then a second time 2020-05-30 18:43:20 -04:00