-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dictionary 1.18 merge to master #411
Conversation
…o account when lymph_nodes_examined_status has exception value 'unknown'
… values ("unknown" and "not applicable") on tumour_grading_system
…nits' field for exception value of 'not applicable' and then check that the prescribed and actual drug dose fields are not submitted
…n value of 'not applicable' and prescribed/actual drug dose field values
…hanges Exceptions validation script changes
409 chemo dose exception
Testing in QA: Tested Test case 1: Missing dose when Sample submission files: Result: Validation fails as expected Test case 2: Dose field(s) are submitted when there is a clinical exception for Sample submission files: Result: Validation fails as expected Test case 3: Validation should pass if Sample submission files: Result: Validation passes as expected (row 3) |
Testing in QA: Tested validation script changes related to Test case 1: Validation should fail when Sample submission files: Submission in primary_diagnosis.tsv file: Error message in clinical submission system: Result: Validation failed as expected. Both Test case 2: Validation should fail if Sample submission files: Submission in primary_diagnosis.tsv file: Error message in clinical submission system: Result: Validation fails as expected. Rows 1 and 2 of the submission fail as expected, while Rows 3 and 4 pass validation as expected. Test case 3: Validation should pass if Sample submission files: |
Testing in QA: Tested validation script changes for Test case 1: If Sample submission files: Result: Validation fails as expected. Both the Updated error message in clinical submission system indicates to the data submitter that the Test case 2: If both Sample submission files: Result: Validation passes as expected. |
Deployed Dictionary version 1.18 to Staging Tested the same test cases that were done in QA (documented in above comments) in Staging as well. Used the same sample submission files (included in comments above). |
Dictionary version 1.18 deployed to prod August 25, 2023. Tested same test cases (documented above) in prod. All test cases passed/failed validation in prod as expected (same results as Staging). |
Test in QA/Staging