20. Draft Mode

[MintooXavier]

Brief description: This feature is used to track changes to a project in Production; and commit or reject the changes accordingly.

User spec: https://github.com/CCTC-team/redcap_cypress/blob/redcap_val/user_requirement_specification/core/20_draft_mode.spec

Feature link: https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/B/Draft%20Mode_20/B.4.20.100%20-%20REDUNDANT.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/B/Draft%20Mode_20/B.4.20.300%20-%20Instrument%20Behavior.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/B/Draft%20Mode_20/B.4.20.400%20-%20Draft%20Mode%20Summary.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/B/Draft%20Mode_20/B.4.20.500%20-%20REDUNDANT.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/B/Draft%20Mode_20/B.4.20.600%20-%20REDUNDANT.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/B/Draft%20Mode_20/B.4.20.700%20-%20REDUNDANT.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/B/Draft%20Mode_20/B.4.20.800%20-%20Draft%20warning.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/B/Draft%20Mode_20/B.4.20.900%20-%20Draft%20version%20control.feature

Pre review:

• [x] Script(s) targets the correct feature sufficiently
• [x] The user requirements are met

Post review:

• [x] Script(s) targets the correct feature sufficiently
• [x] Script(s) appropriately tests the feature
• [x] Scripts are run on CCTC_REDCap_Docker
• [x] Scripts are run on the REDCap version being validated

[MintooXavier]

Emailed REDCap Team - Theresa Baker and Adam De Fouw regarding the below script:

1. B.4.20.300 – Instrument Behavior.
   • After submitting the changes in draft mode, we are checking if it is successful based on messages e.g. “Changes Were Made Automatically”. Do we need to check the instrument to see if the changes have been applied to it? Because only then we can be sure that the changes have been successfully applied.
   • Verify instrument before and after draft mode submission
   • Modified the script and pushed to MX_v13.1.37

Not verified explicitly but included in other options (No need to email)

2. B.4.20.100 - REDUNDANT The below options are not verified explicitly but included in the other options in A.6.4.400: • Yes, if project has no records OR if has records and no existing fields were modified • Yes, if no critical issues exist

[MintooXavier]

Scripts Pre-reviewed:

1. B.4.20.100 - REDUNDANT
2. No user requirement or script for .200
3. B.4.20.300 – Instrument Behavior.
4. B.4.20.400 - Draft Mode Summary
5. B.4.20.500 - REDUNDANT
6. B.4.20.600 - REDUNDANT
7. B.4.20.700 - REDUNDANT
8. B.4.20.800 - Draft warning
9. B.4.20.900 - Draft version control

All Tests pass

[phillidgithub]

Scripts Post-reviewed: B.4.20.300 – Instrument Behavior Test passes

Note that log record on line 65 is Approve production project modifications (automatic) rather than Approve production project modifications

[MintooXavier]

1. Added (automatic) to script
2. ATS team accepted the script