From 6d906fcf54d1bdf0080152d0fcf475d098a84296 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 13:48:53 -0500 Subject: [PATCH 01/96] Create .gitignore --- .gitignore | 1 + 1 file changed, 1 insertion(+) create mode 100644 .gitignore diff --git a/.gitignore b/.gitignore new file mode 100644 index 00000000..ffd2a4a2 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +*.idea From a0cc27ea7af9bd90b3c0cb982f856db638b58792 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 13:49:14 -0500 Subject: [PATCH 02/96] Update gitignore --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index ffd2a4a2..1df651a2 100644 --- a/.gitignore +++ b/.gitignore @@ -1 +1,2 @@ *.idea +.DS_Store \ No newline at end of file From 9941d5f8b28f1c533430aa03b1965173fe40fdf9 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:04:39 -0500 Subject: [PATCH 03/96] Begin rename process --- .../A.2.2.100 - Create Users.feature} | 0 .../A.2.2.200 - Suspend - Unsuspend.feature} | 0 .../A.2.2.300 - Search by Criteria.feature} | 0 .../A.2.2.400 - Delete.feature} | 0 .../A.2.2.500 - Tabular View.feature} | 0 .../A.2.2.600 - Account Lockout.feature} | 0 .../A.2.2.700 - Account Lockout Time Change.feature} | 0 .../A.2.2.800 - Auto-Logout Inactivity Time.feature} | 0 .../A.2.3.100 - Administrators Table.feature} | 0 .../A.2.3.200 - Add Remove Admins.feature} | 0 .../A.2.3.300 - Super Users and Account Managers.feature} | 0 ... Projects.feature => A.6.4.100 - User Create Projects.feature} | 0 ... Production.feature => A.6.4.200 - Move to Production.feature} | 0 ...esponses.feature => A.6.4.300 - Edit Survey Responses.feature} | 0 ...ttings - Draft Mode.feature => A.6.4.400 - Draft Mode.feature} | 0 ...ruments.feature => A.6.4.500 - Repeatable Instruments.feature} | 0 ....feature => A.6.4.600 - Events and Arms in Production.feature} | 0 ... Projects.feature => A.6.4.700 - Blank Slate Projects.feature} | 0 ...- System Status.feature => A.2.12.100 - System Status.feature} | 0 .../B.2.6.100 - Basic Privileges.feature} | 0 .../B.2.6.200 - Data Entry Form Access.feature} | 0 .../B.2.6.300 - Data Export Rights.feature} | 0 .../B.2.6.400 - Creating Copying Deleting Roles.feature} | 0 .../B.2.6.500 - Adding and Removing Users from Roles.feature} | 0 ...it Delete.feature => B.2.10.100 - Create Edit Delete.feature} | 0 ...Remove Users.feature => B.2.10.200 - Add Remove Users.feature} | 0 ...- Multiple DAGs.feature => B.2.10.300 - Multiple DAGs.feature} | 0 ....feature => B.2.10.400 - User and Record Restrictions.feature} | 0 ... to DAG.feature => B.2.10.500 - Assign Records to DAG.feature} | 0 ...oup - Unique DAGs.feature => B.2.10.600 - Unique DAGs.feature} | 0 .../B/Data import/{B.3.16.300 => B.3.16.300 - REDUNDANT.feature} | 0 .../B.3.14.100 - create record.feature | 0 .../B.3.14.1000 - Delete Form Data.feature | 0 .../B.3.14.1100 -Delete Record Data.feature | 0 .../B.3.14.1200 - Delete Record.feature | 0 .../B.3.14.200 - Field Type Data Entry.feature | 0 .../B.3.14.300 - Multiple choice-radio button.feature | 0 .../B.3.14.400 - Date time fields.feature | 0 .../B.3.14.500 - Leave without save.feature | 0 .../B.3.14.600 - Save options.feature | 0 .../B.3.14.700 - Form status option.feature | 0 .../B.3.14.800 - Display record status dashboard.feature | 0 .../B.3.14.900 - Rename record.feature | 0 .../B.3.15.100 - Enable Form into Survey.feature | 0 .../B.3.15.1000 - Survey participant list.feature | 0 .../B.3.15.1100 - Survey track response.feature | 0 .../B.3.15.1200 - Disabled survey removes survey metadata.feature | 0 .../B.3.15.1300 - Public survey link.feature | 0 .../B.3.15.200 - Survey status.feature | 0 .../B.3.15.300 - Survey distribution participant list.feature | 0 .../B.3.15.400 - Survey open from form.feature | 0 .../B.3.15.500 - Survey mode alerts form mode.feature | 0 .../B.3.15.800 - Survey edit.feature | 0 .../B.3.15.900 - Survey status.feature | 0 ...Record Changes.feature => B.2.23.100 - Record Changes.feature} | 0 ...udit Trail.feature => B.2.23.200 - Export Audit Trail.feature} | 0 ...ing Ability.feature => B.2.23.300 - Filtering Ability.feature} | 0 ...dule Security.feature => B.2.23.400 - Module Security.feature} | 0 .../C.2.19.100 - Lock status.feature | 0 .../C.2.19.200 - Lock form display.feature | 0 .../C.2.19.300 - Locking record filter.feature | 0 .../C.2.19.400 - Lock status display.feature | 0 .../C.2.19.500 - esign display.feature | 0 .../C.2.19.600 - Locking module navigation.feature | 0 .../C.2.19.700 - esign customization.feature | 0 .../C.2.19.800 - Esign and Lock.feature | 0 .../C.2.19.900 - Esign and Lock access.feature | 0 ... management.feature => C.5.22.200 - Report Management.feature} | 0 68 files changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/A/{Add manage users/A.2.2.100 - Add Manage Users - Create Users.feature => Add Manage Users/A.2.2.100 - Create Users.feature} (100%) rename Feature Tests/A/{Add manage users/ A.2.2.200 - Add Manage Users - Suspend - Unsuspend.feature => Add Manage Users/A.2.2.200 - Suspend - Unsuspend.feature} (100%) rename Feature Tests/A/{Add manage users/A.2.2.300 - Add Manage Users - Search by Criteria.feature => Add Manage Users/A.2.2.300 - Search by Criteria.feature} (100%) rename Feature Tests/A/{Add manage users/A.2.2.400 - Add Manage Users - Delete.feature => Add Manage Users/A.2.2.400 - Delete.feature} (100%) rename Feature Tests/A/{Add manage users/A.2.2.500 - Add Manage Users - Tabular View.feature => Add Manage Users/A.2.2.500 - Tabular View.feature} (100%) rename Feature Tests/A/{Add manage users/A.2.2.600 - Add Manage Users - Account Lockout.feature => Add Manage Users/A.2.2.600 - Account Lockout.feature} (100%) rename Feature Tests/A/{Add manage users/A.2.2.700 - Add Manage Users - Account Lockout Time Change.feature => Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature} (100%) rename Feature Tests/A/{Add manage users/A.2.2.800 - Add Manage Users - Auto-Logout Inactivity Time.feature => Add Manage Users/A.2.2.800 - Auto-Logout Inactivity Time.feature} (100%) rename Feature Tests/A/{Assign administrators/A.2.3.100 - Assign Administrators and Account Managers - Administrators Table.feature => Assign Administrators/A.2.3.100 - Administrators Table.feature} (100%) rename Feature Tests/A/{Assign administrators/A.2.3.200 - Assign Administrators and Account Managers - Add Remove Admins.feature => Assign Administrators/A.2.3.200 - Add Remove Admins.feature} (100%) rename Feature Tests/A/{Assign administrators/A.2.3.300 - Assign Administrators and Account Managers - Super Users and Account Managers.feature => Assign Administrators/A.2.3.300 - Super Users and Account Managers.feature} (100%) rename Feature Tests/A/Project Setup/{A.6.4.100 - Manage project creation deletion and settings - User Create Projects.feature => A.6.4.100 - User Create Projects.feature} (100%) rename Feature Tests/A/Project Setup/{A.6.4.200 - Manage project creation deletion and settings - Move to Production.feature => A.6.4.200 - Move to Production.feature} (100%) rename Feature Tests/A/Project Setup/{A.6.4.300 - Manage project creation deletion and settings - Edit Survey Responses.feature => A.6.4.300 - Edit Survey Responses.feature} (100%) rename Feature Tests/A/Project Setup/{A.6.4.400 - Manage project creation deletion and settings - Draft Mode.feature => A.6.4.400 - Draft Mode.feature} (100%) rename Feature Tests/A/Project Setup/{A.6.4.500 - Manage project creation deletion and settings - Repeatable Instruments.feature => A.6.4.500 - Repeatable Instruments.feature} (100%) rename Feature Tests/A/Project Setup/{A.6.4.600 - Manage project creation deletion and settings - Events and Arms in Production.feature => A.6.4.600 - Events and Arms in Production.feature} (100%) rename Feature Tests/A/Project Setup/{A.6.4.700 - Manage project creation deletion and settings - Blank Slate Projects.feature => A.6.4.700 - Blank Slate Projects.feature} (100%) rename Feature Tests/A/Security settings/{A.2.12.100 - Security Settings - System Status.feature => A.2.12.100 - System Status.feature} (100%) rename Feature Tests/B/{Assign user rights/B.2.6.100 - Assign User Rights - Basic Privileges.feature => Assign User Rights/B.2.6.100 - Basic Privileges.feature} (100%) rename Feature Tests/B/{Assign user rights/B.2.6.200 - Assign User Rights - Data Entry Form Access.feature => Assign User Rights/B.2.6.200 - Data Entry Form Access.feature} (100%) rename Feature Tests/B/{Assign user rights/B.2.6.300 - Assign User Rights - Data Export Rights.feature => Assign User Rights/B.2.6.300 - Data Export Rights.feature} (100%) rename Feature Tests/B/{Assign user rights/B.2.6.400 - Assign User Rights - Creating Copying Deleting Roles.feature => Assign User Rights/B.2.6.400 - Creating Copying Deleting Roles.feature} (100%) rename Feature Tests/B/{Assign user rights/B.2.6.500 - Assign User Rights - Adding and Removing Users from Roles.feature => Assign User Rights/B.2.6.500 - Adding and Removing Users from Roles.feature} (100%) rename Feature Tests/B/Data Access Groups/{B.2.10.100 - Data Access Group - Create Edit Delete.feature => B.2.10.100 - Create Edit Delete.feature} (100%) rename Feature Tests/B/Data Access Groups/{B.2.10.200 - Data Access Group - Add Remove Users.feature => B.2.10.200 - Add Remove Users.feature} (100%) rename Feature Tests/B/Data Access Groups/{B.2.10.300 - Data Access Group - Multiple DAGs.feature => B.2.10.300 - Multiple DAGs.feature} (100%) rename Feature Tests/B/Data Access Groups/{B.2.10.400 - Data Access Group - User and Record Restrictions.feature => B.2.10.400 - User and Record Restrictions.feature} (100%) rename Feature Tests/B/Data Access Groups/{B.2.10.500 - Data Access Group - Assign Records to DAG.feature => B.2.10.500 - Assign Records to DAG.feature} (100%) rename Feature Tests/B/Data Access Groups/{B.2.10.600 - Data Access Group - Unique DAGs.feature => B.2.10.600 - Unique DAGs.feature} (100%) rename Feature Tests/B/Data import/{B.3.16.300 => B.3.16.300 - REDUNDANT.feature} (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.100 - create record.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.1000 - Delete Form Data.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.1100 -Delete Record Data.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.1200 - Delete Record.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.200 - Field Type Data Entry.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.300 - Multiple choice-radio button.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.400 - Date time fields.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.500 - Leave without save.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.600 - Save options.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.700 - Form status option.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.800 - Display record status dashboard.feature (100%) rename Feature Tests/B/{Direct data entry with data collection instrument => Direct Data Entry - Data Collection Instrument}/B.3.14.900 - Rename record.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.100 - Enable Form into Survey.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.1000 - Survey participant list.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.1100 - Survey track response.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.1200 - Disabled survey removes survey metadata.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.1300 - Public survey link.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.200 - Survey status.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.300 - Survey distribution participant list.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.400 - Survey open from form.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.500 - Survey mode alerts form mode.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.800 - Survey edit.feature (100%) rename Feature Tests/B/{Direct data entry through the survey feature => Direct Data Entry - Survey}/B.3.15.900 - Survey status.feature (100%) rename Feature Tests/B/Logging Module/{B.2.23.100 - Logging - Record Changes.feature => B.2.23.100 - Record Changes.feature} (100%) rename Feature Tests/B/Logging Module/{B.2.23.200 - Logging - Export Audit Trail.feature => B.2.23.200 - Export Audit Trail.feature} (100%) rename Feature Tests/B/Logging Module/{B.2.23.300 - Logging - Filtering Ability.feature => B.2.23.300 - Filtering Ability.feature} (100%) rename Feature Tests/B/Logging Module/{B.2.23.400 - Logging - Module Security.feature => B.2.23.400 - Module Security.feature} (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.100 - Lock status.feature (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.200 - Lock form display.feature (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.300 - Locking record filter.feature (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.400 - Lock status display.feature (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.500 - esign display.feature (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.600 - Locking module navigation.feature (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.700 - esign customization.feature (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.800 - Esign and Lock.feature (100%) rename Feature Tests/C/{Record locking and E-signatures => Record Locking & E-Signatures}/C.2.19.900 - Esign and Lock access.feature (100%) rename Feature Tests/C/Reporting/{C.5.22.200 - Report management.feature => C.5.22.200 - Report Management.feature} (100%) diff --git a/Feature Tests/A/Add manage users/A.2.2.100 - Add Manage Users - Create Users.feature b/Feature Tests/A/Add Manage Users/A.2.2.100 - Create Users.feature similarity index 100% rename from Feature Tests/A/Add manage users/A.2.2.100 - Add Manage Users - Create Users.feature rename to Feature Tests/A/Add Manage Users/A.2.2.100 - Create Users.feature diff --git a/Feature Tests/A/Add manage users/ A.2.2.200 - Add Manage Users - Suspend - Unsuspend.feature b/Feature Tests/A/Add Manage Users/A.2.2.200 - Suspend - Unsuspend.feature similarity index 100% rename from Feature Tests/A/Add manage users/ A.2.2.200 - Add Manage Users - Suspend - Unsuspend.feature rename to Feature Tests/A/Add Manage Users/A.2.2.200 - Suspend - Unsuspend.feature diff --git a/Feature Tests/A/Add manage users/A.2.2.300 - Add Manage Users - Search by Criteria.feature b/Feature Tests/A/Add Manage Users/A.2.2.300 - Search by Criteria.feature similarity index 100% rename from Feature Tests/A/Add manage users/A.2.2.300 - Add Manage Users - Search by Criteria.feature rename to Feature Tests/A/Add Manage Users/A.2.2.300 - Search by Criteria.feature diff --git a/Feature Tests/A/Add manage users/A.2.2.400 - Add Manage Users - Delete.feature b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature similarity index 100% rename from Feature Tests/A/Add manage users/A.2.2.400 - Add Manage Users - Delete.feature rename to Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature diff --git a/Feature Tests/A/Add manage users/A.2.2.500 - Add Manage Users - Tabular View.feature b/Feature Tests/A/Add Manage Users/A.2.2.500 - Tabular View.feature similarity index 100% rename from Feature Tests/A/Add manage users/A.2.2.500 - Add Manage Users - Tabular View.feature rename to Feature Tests/A/Add Manage Users/A.2.2.500 - Tabular View.feature diff --git a/Feature Tests/A/Add manage users/A.2.2.600 - Add Manage Users - Account Lockout.feature b/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature similarity index 100% rename from Feature Tests/A/Add manage users/A.2.2.600 - Add Manage Users - Account Lockout.feature rename to Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature diff --git a/Feature Tests/A/Add manage users/A.2.2.700 - Add Manage Users - Account Lockout Time Change.feature b/Feature Tests/A/Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature similarity index 100% rename from Feature Tests/A/Add manage users/A.2.2.700 - Add Manage Users - Account Lockout Time Change.feature rename to Feature Tests/A/Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature diff --git a/Feature Tests/A/Add manage users/A.2.2.800 - Add Manage Users - Auto-Logout Inactivity Time.feature b/Feature Tests/A/Add Manage Users/A.2.2.800 - Auto-Logout Inactivity Time.feature similarity index 100% rename from Feature Tests/A/Add manage users/A.2.2.800 - Add Manage Users - Auto-Logout Inactivity Time.feature rename to Feature Tests/A/Add Manage Users/A.2.2.800 - Auto-Logout Inactivity Time.feature diff --git a/Feature Tests/A/Assign administrators/A.2.3.100 - Assign Administrators and Account Managers - Administrators Table.feature b/Feature Tests/A/Assign Administrators/A.2.3.100 - Administrators Table.feature similarity index 100% rename from Feature Tests/A/Assign administrators/A.2.3.100 - Assign Administrators and Account Managers - Administrators Table.feature rename to Feature Tests/A/Assign Administrators/A.2.3.100 - Administrators Table.feature diff --git a/Feature Tests/A/Assign administrators/A.2.3.200 - Assign Administrators and Account Managers - Add Remove Admins.feature b/Feature Tests/A/Assign Administrators/A.2.3.200 - Add Remove Admins.feature similarity index 100% rename from Feature Tests/A/Assign administrators/A.2.3.200 - Assign Administrators and Account Managers - Add Remove Admins.feature rename to Feature Tests/A/Assign Administrators/A.2.3.200 - Add Remove Admins.feature diff --git a/Feature Tests/A/Assign administrators/A.2.3.300 - Assign Administrators and Account Managers - Super Users and Account Managers.feature b/Feature Tests/A/Assign Administrators/A.2.3.300 - Super Users and Account Managers.feature similarity index 100% rename from Feature Tests/A/Assign administrators/A.2.3.300 - Assign Administrators and Account Managers - Super Users and Account Managers.feature rename to Feature Tests/A/Assign Administrators/A.2.3.300 - Super Users and Account Managers.feature diff --git a/Feature Tests/A/Project Setup/A.6.4.100 - Manage project creation deletion and settings - User Create Projects.feature b/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.100 - Manage project creation deletion and settings - User Create Projects.feature rename to Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature diff --git a/Feature Tests/A/Project Setup/A.6.4.200 - Manage project creation deletion and settings - Move to Production.feature b/Feature Tests/A/Project Setup/A.6.4.200 - Move to Production.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.200 - Manage project creation deletion and settings - Move to Production.feature rename to Feature Tests/A/Project Setup/A.6.4.200 - Move to Production.feature diff --git a/Feature Tests/A/Project Setup/A.6.4.300 - Manage project creation deletion and settings - Edit Survey Responses.feature b/Feature Tests/A/Project Setup/A.6.4.300 - Edit Survey Responses.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.300 - Manage project creation deletion and settings - Edit Survey Responses.feature rename to Feature Tests/A/Project Setup/A.6.4.300 - Edit Survey Responses.feature diff --git a/Feature Tests/A/Project Setup/A.6.4.400 - Manage project creation deletion and settings - Draft Mode.feature b/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.400 - Manage project creation deletion and settings - Draft Mode.feature rename to Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature diff --git a/Feature Tests/A/Project Setup/A.6.4.500 - Manage project creation deletion and settings - Repeatable Instruments.feature b/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.500 - Manage project creation deletion and settings - Repeatable Instruments.feature rename to Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature diff --git a/Feature Tests/A/Project Setup/A.6.4.600 - Manage project creation deletion and settings - Events and Arms in Production.feature b/Feature Tests/A/Project Setup/A.6.4.600 - Events and Arms in Production.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.600 - Manage project creation deletion and settings - Events and Arms in Production.feature rename to Feature Tests/A/Project Setup/A.6.4.600 - Events and Arms in Production.feature diff --git a/Feature Tests/A/Project Setup/A.6.4.700 - Manage project creation deletion and settings - Blank Slate Projects.feature b/Feature Tests/A/Project Setup/A.6.4.700 - Blank Slate Projects.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.700 - Manage project creation deletion and settings - Blank Slate Projects.feature rename to Feature Tests/A/Project Setup/A.6.4.700 - Blank Slate Projects.feature diff --git a/Feature Tests/A/Security settings/A.2.12.100 - Security Settings - System Status.feature b/Feature Tests/A/Security settings/A.2.12.100 - System Status.feature similarity index 100% rename from Feature Tests/A/Security settings/A.2.12.100 - Security Settings - System Status.feature rename to Feature Tests/A/Security settings/A.2.12.100 - System Status.feature diff --git a/Feature Tests/B/Assign user rights/B.2.6.100 - Assign User Rights - Basic Privileges.feature b/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature similarity index 100% rename from Feature Tests/B/Assign user rights/B.2.6.100 - Assign User Rights - Basic Privileges.feature rename to Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature diff --git a/Feature Tests/B/Assign user rights/B.2.6.200 - Assign User Rights - Data Entry Form Access.feature b/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature similarity index 100% rename from Feature Tests/B/Assign user rights/B.2.6.200 - Assign User Rights - Data Entry Form Access.feature rename to Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature diff --git a/Feature Tests/B/Assign user rights/B.2.6.300 - Assign User Rights - Data Export Rights.feature b/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature similarity index 100% rename from Feature Tests/B/Assign user rights/B.2.6.300 - Assign User Rights - Data Export Rights.feature rename to Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature diff --git a/Feature Tests/B/Assign user rights/B.2.6.400 - Assign User Rights - Creating Copying Deleting Roles.feature b/Feature Tests/B/Assign User Rights/B.2.6.400 - Creating Copying Deleting Roles.feature similarity index 100% rename from Feature Tests/B/Assign user rights/B.2.6.400 - Assign User Rights - Creating Copying Deleting Roles.feature rename to Feature Tests/B/Assign User Rights/B.2.6.400 - Creating Copying Deleting Roles.feature diff --git a/Feature Tests/B/Assign user rights/B.2.6.500 - Assign User Rights - Adding and Removing Users from Roles.feature b/Feature Tests/B/Assign User Rights/B.2.6.500 - Adding and Removing Users from Roles.feature similarity index 100% rename from Feature Tests/B/Assign user rights/B.2.6.500 - Assign User Rights - Adding and Removing Users from Roles.feature rename to Feature Tests/B/Assign User Rights/B.2.6.500 - Adding and Removing Users from Roles.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.100 - Data Access Group - Create Edit Delete.feature b/Feature Tests/B/Data Access Groups/B.2.10.100 - Create Edit Delete.feature similarity index 100% rename from Feature Tests/B/Data Access Groups/B.2.10.100 - Data Access Group - Create Edit Delete.feature rename to Feature Tests/B/Data Access Groups/B.2.10.100 - Create Edit Delete.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.200 - Data Access Group - Add Remove Users.feature b/Feature Tests/B/Data Access Groups/B.2.10.200 - Add Remove Users.feature similarity index 100% rename from Feature Tests/B/Data Access Groups/B.2.10.200 - Data Access Group - Add Remove Users.feature rename to Feature Tests/B/Data Access Groups/B.2.10.200 - Add Remove Users.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.300 - Data Access Group - Multiple DAGs.feature b/Feature Tests/B/Data Access Groups/B.2.10.300 - Multiple DAGs.feature similarity index 100% rename from Feature Tests/B/Data Access Groups/B.2.10.300 - Data Access Group - Multiple DAGs.feature rename to Feature Tests/B/Data Access Groups/B.2.10.300 - Multiple DAGs.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.400 - Data Access Group - User and Record Restrictions.feature b/Feature Tests/B/Data Access Groups/B.2.10.400 - User and Record Restrictions.feature similarity index 100% rename from Feature Tests/B/Data Access Groups/B.2.10.400 - Data Access Group - User and Record Restrictions.feature rename to Feature Tests/B/Data Access Groups/B.2.10.400 - User and Record Restrictions.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.500 - Data Access Group - Assign Records to DAG.feature b/Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature similarity index 100% rename from Feature Tests/B/Data Access Groups/B.2.10.500 - Data Access Group - Assign Records to DAG.feature rename to Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.600 - Data Access Group - Unique DAGs.feature b/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature similarity index 100% rename from Feature Tests/B/Data Access Groups/B.2.10.600 - Data Access Group - Unique DAGs.feature rename to Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature diff --git a/Feature Tests/B/Data import/B.3.16.300 b/Feature Tests/B/Data import/B.3.16.300 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.300 rename to Feature Tests/B/Data import/B.3.16.300 - REDUNDANT.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.100 - create record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - create record.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.100 - create record.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - create record.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.1000 - Delete Form Data.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1000 - Delete Form Data.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.1000 - Delete Form Data.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1000 - Delete Form Data.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.1100 -Delete Record Data.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.1100 -Delete Record Data.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.1200 - Delete Record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.1200 - Delete Record.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.200 - Field Type Data Entry.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.200 - Field Type Data Entry.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.200 - Field Type Data Entry.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.200 - Field Type Data Entry.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.300 - Multiple choice-radio button.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.300 - Multiple choice-radio button.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.400 - Date time fields.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Date time fields.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.400 - Date time fields.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Date time fields.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.500 - Leave without save.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without save.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.500 - Leave without save.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without save.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.600 - Save options.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save options.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.600 - Save options.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save options.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.700 - Form status option.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status option.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.700 - Form status option.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status option.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.800 - Display record status dashboard.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.800 - Display record status dashboard.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.800 - Display record status dashboard.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.800 - Display record status dashboard.feature diff --git a/Feature Tests/B/Direct data entry with data collection instrument/B.3.14.900 - Rename record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename record.feature similarity index 100% rename from Feature Tests/B/Direct data entry with data collection instrument/B.3.14.900 - Rename record.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename record.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.100 - Enable Form into Survey.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.100 - Enable Form into Survey.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.1000 - Survey participant list.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey participant list.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.1000 - Survey participant list.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey participant list.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.1100 - Survey track response.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey track response.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.1100 - Survey track response.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey track response.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.1200 - Disabled survey removes survey metadata.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled survey removes survey metadata.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.1200 - Disabled survey removes survey metadata.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled survey removes survey metadata.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.1300 - Public survey link.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public survey link.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.1300 - Public survey link.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public survey link.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.200 - Survey status.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.200 - Survey status.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.300 - Survey distribution participant list.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey distribution participant list.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.300 - Survey distribution participant list.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey distribution participant list.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.400 - Survey open from form.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Survey open from form.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.400 - Survey open from form.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Survey open from form.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.500 - Survey mode alerts form mode.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey mode alerts form mode.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.500 - Survey mode alerts form mode.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey mode alerts form mode.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.800 - Survey edit.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Survey edit.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.800 - Survey edit.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Survey edit.feature diff --git a/Feature Tests/B/Direct data entry through the survey feature/B.3.15.900 - Survey status.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey status.feature similarity index 100% rename from Feature Tests/B/Direct data entry through the survey feature/B.3.15.900 - Survey status.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey status.feature diff --git a/Feature Tests/B/Logging Module/B.2.23.100 - Logging - Record Changes.feature b/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature similarity index 100% rename from Feature Tests/B/Logging Module/B.2.23.100 - Logging - Record Changes.feature rename to Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature diff --git a/Feature Tests/B/Logging Module/B.2.23.200 - Logging - Export Audit Trail.feature b/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature similarity index 100% rename from Feature Tests/B/Logging Module/B.2.23.200 - Logging - Export Audit Trail.feature rename to Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature diff --git a/Feature Tests/B/Logging Module/B.2.23.300 - Logging - Filtering Ability.feature b/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature similarity index 100% rename from Feature Tests/B/Logging Module/B.2.23.300 - Logging - Filtering Ability.feature rename to Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature diff --git a/Feature Tests/B/Logging Module/B.2.23.400 - Logging - Module Security.feature b/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature similarity index 100% rename from Feature Tests/B/Logging Module/B.2.23.400 - Logging - Module Security.feature rename to Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.100 - Lock status.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.100 - Lock status.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.200 - Lock form display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.200 - Lock form display.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.300 - Locking record filter.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.300 - Locking record filter.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.400 - Lock status display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.400 - Lock status display.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.500 - esign display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.500 - esign display.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.600 - Locking module navigation.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.600 - Locking module navigation.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.700 - esign customization.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.700 - esign customization.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.800 - Esign and Lock.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.800 - Esign and Lock.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.800 - Esign and Lock.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.800 - Esign and Lock.feature diff --git a/Feature Tests/C/Record locking and E-signatures/C.2.19.900 - Esign and Lock access.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature similarity index 100% rename from Feature Tests/C/Record locking and E-signatures/C.2.19.900 - Esign and Lock access.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature diff --git a/Feature Tests/C/Reporting/C.5.22.200 - Report management.feature b/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature similarity index 100% rename from Feature Tests/C/Reporting/C.5.22.200 - Report management.feature rename to Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature From 59979a27c5ba6559e2bca6c94f51a94a4989828a Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:05:45 -0500 Subject: [PATCH 04/96] Needs to be .feature (no s) --- ...0 - Field Ranges.features => B.4.8.300 - Field Ranges.feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/B/Field validation/{B.4.8.300 - Field Ranges.features => B.4.8.300 - Field Ranges.feature} (100%) diff --git a/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.features b/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature similarity index 100% rename from Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.features rename to Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature From bc85c01934a7d89f0bc104147948de07cb276cf1 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:08:19 -0500 Subject: [PATCH 05/96] Fix syntax error on this project creation step for ALL features --- .../A/Add Manage Users/A.2.2.100 - Create Users.feature | 4 ++-- .../A.6.4.1600 - survey edit enable control center.feature | 2 +- .../Project status/A.6.11.100 - limit project status.feature | 2 +- .../Assign User Rights/B.2.6.300 - Data Export Rights.feature | 2 +- .../B.2.6.400 - Creating Copying Deleting Roles.feature | 2 +- .../B.2.6.500 - Adding and Removing Users from Roles.feature | 2 +- .../B.2.10.100 - Create Edit Delete.feature | 2 +- .../Data Access Groups/B.2.10.200 - Add Remove Users.feature | 2 +- .../B/Data Access Groups/B.2.10.300 - Multiple DAGs.feature | 2 +- .../B.2.10.500 - Assign Records to DAG.feature | 2 +- .../B/Data Access Groups/B.2.10.600 - Unique DAGs.feature | 2 +- .../B.3.15.100 - Enable Form into Survey.feature | 2 +- .../B.3.15.1300 - Public survey link.feature | 2 +- .../B.3.15.200 - Survey status.feature | 2 +- .../B/Export data/B.5.21.200 - Export format.feature | 2 +- .../B/Export data/B.5.21.400 - Export select forms.feature | 2 +- .../B/Logging Module/B.2.23.100 - Record Changes.feature | 2 +- .../B/Logging Module/B.2.23.200 - Export Audit Trail.feature | 2 +- .../B/Logging Module/B.2.23.300 - Filtering Ability.feature | 2 +- .../B/Logging Module/B.2.23.400 - Module Security.feature | 2 +- .../B.4.27.300 - Longitudinal.feature | 2 +- .../B.4.27.400 - Longitudinal Events.feature | 2 +- .../B.4.27.700 - Longitudinal Admin Required.feature | 2 +- .../B.6.13.200 - My project dashboard archive hide.feature | 2 +- .../B/Online Designer/B.6.7.1800 - Field required.feature | 2 +- .../B.6.7.400 - Forms - Copy Instruments.feature | 2 +- .../B/Project Setup/B.6.4.1100 - Erase data in dev.feature | 4 ++-- .../B/Project Setup/B.6.4.1200 - Delete project.feature | 2 +- .../B/Project Setup/B.6.4.1400 - Repeat survey.feature | 2 +- .../B/Project Setup/B.6.4.800 - Project setup title.feature | 2 +- .../B/Project Setup/B.6.4.900 - Project setup purpose.feature | 2 +- .../B/Project status/B.6.11.200 - Move project status.feature | 2 +- ...300 - Data management during project status change.feature | 4 ++-- .../C.2.19.100 - Lock status.feature | 2 +- .../C.2.19.200 - Lock form display.feature | 2 +- .../C.2.19.300 - Locking record filter.feature | 2 +- .../C.2.19.400 - Lock status display.feature | 2 +- .../C.2.19.500 - esign display.feature | 2 +- .../C.2.19.600 - Locking module navigation.feature | 2 +- .../C.2.19.700 - esign customization.feature | 2 +- .../C.2.19.900 - Esign and Lock access.feature | 2 +- Feature Tests/C/Reporting/C.5.22.100 - Report access.feature | 2 +- .../C/Reporting/C.5.22.200 - Report Management.feature | 2 +- 43 files changed, 46 insertions(+), 46 deletions(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.100 - Create Users.feature b/Feature Tests/A/Add Manage Users/A.2.2.100 - Create Users.feature index a9863d8a..b82fb5a2 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.100 - Create Users.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.100 - Create Users.feature @@ -85,7 +85,7 @@ Then I should NOT see "Control Center" #FUNCTIONAL_REQUIREMENT ##VERIFY: Admin only can make project -When I create a new project named "A.2.2.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +When I create a new project named "A.2.2.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button And I click on the button labeled "I Agree" in the dialog box Then I should see "Request Sent" When I logout @@ -111,6 +111,6 @@ Then I should see "New Project" #FUNCTIONAL_REQUIREMENT ##VERIFY: User can make project -When I create a new project named "A.2.2.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +When I create a new project named "A.2.2.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button And I click on the button labeled "I Agree" in the dialog box Then I should see "Project Setup" diff --git a/Feature Tests/A/Project Setup/A.6.4.1600 - survey edit enable control center.feature b/Feature Tests/A/Project Setup/A.6.4.1600 - survey edit enable control center.feature index 2c81eda3..b05ec31f 100644 --- a/Feature Tests/A/Project Setup/A.6.4.1600 - survey edit enable control center.feature +++ b/Feature Tests/A/Project Setup/A.6.4.1600 - survey edit enable control center.feature @@ -6,7 +6,7 @@ Feature: Control Center: The system shall allow users to edit survey responses t Scenario: A.6.4.1600.100 #SETUP_DEV Given I login to REDCap with the user "Test_Admin" -And I create a new project named "A.6.4.1600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "A.6.4.1600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #FUNCTIONAL REQUIREMENT ##ACTION Admin Disable edit survey response function in control center diff --git a/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature b/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature index bbf7b549..c7fb1356 100644 --- a/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature +++ b/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature @@ -6,7 +6,7 @@ I want to see that My Project is functioning as expected Scenario: A.6.11.100.100 Production status setting in control center #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "A.6.11.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "A.6.11.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button ##USER_RIGHTS When I click on the link labeled "User Rights" diff --git a/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature b/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature index ec92c595..d05db38f 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature @@ -6,7 +6,7 @@ I want to see that data export rights is functioning as expected Scenario: B.2.6.300.100 Data Export Rights #SETUP_PRODUCTION Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.6.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.6.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" diff --git a/Feature Tests/B/Assign User Rights/B.2.6.400 - Creating Copying Deleting Roles.feature b/Feature Tests/B/Assign User Rights/B.2.6.400 - Creating Copying Deleting Roles.feature index f39ad502..17349312 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.400 - Creating Copying Deleting Roles.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.400 - Creating Copying Deleting Roles.feature @@ -6,7 +6,7 @@ I want to see that assign user rights is functioning as expected Scenario: B.2.6.400.100 Create, Copy, & Delete User Roles #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.6.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.6.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #FUNCTIONAL REQUIREMENT: ##ACTION: User Rights Create role diff --git a/Feature Tests/B/Assign User Rights/B.2.6.500 - Adding and Removing Users from Roles.feature b/Feature Tests/B/Assign User Rights/B.2.6.500 - Adding and Removing Users from Roles.feature index a3b8b9d3..ef86c676 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.500 - Adding and Removing Users from Roles.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.500 - Adding and Removing Users from Roles.feature @@ -6,7 +6,7 @@ I want to see that assign user rights is functioning as expected Scenario: B.2.6.500.100 Cancel, Assign, Re-assign, & Remove User Roles #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.6.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.6.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_USER_RIGHTS When I click on the link labeled "User Rights" diff --git a/Feature Tests/B/Data Access Groups/B.2.10.100 - Create Edit Delete.feature b/Feature Tests/B/Data Access Groups/B.2.10.100 - Create Edit Delete.feature index b3d870f6..206deb19 100644 --- a/Feature Tests/B/Data Access Groups/B.2.10.100 - Create Edit Delete.feature +++ b/Feature Tests/B/Data Access Groups/B.2.10.100 - Create Edit Delete.feature @@ -6,7 +6,7 @@ I want to see that Data Access Groups is functioning as expected Scenario: B.2.10.100.100 Create, Edit & Delete DAGs #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.10.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.10.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "DAGs" Then I should see "Assign user to a group" diff --git a/Feature Tests/B/Data Access Groups/B.2.10.200 - Add Remove Users.feature b/Feature Tests/B/Data Access Groups/B.2.10.200 - Add Remove Users.feature index a140aab8..97451e44 100644 --- a/Feature Tests/B/Data Access Groups/B.2.10.200 - Add Remove Users.feature +++ b/Feature Tests/B/Data Access Groups/B.2.10.200 - Add Remove Users.feature @@ -6,7 +6,7 @@ I want to see that Data Access Groups is functioning as expected Scenario: B.2.10.200.100 Assign & Remove User to DAG #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.10.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.10.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_RECORD_DAG_ASSIGN When I click on "Record Status Dashboard" diff --git a/Feature Tests/B/Data Access Groups/B.2.10.300 - Multiple DAGs.feature b/Feature Tests/B/Data Access Groups/B.2.10.300 - Multiple DAGs.feature index 10bcc66d..f1f98540 100644 --- a/Feature Tests/B/Data Access Groups/B.2.10.300 - Multiple DAGs.feature +++ b/Feature Tests/B/Data Access Groups/B.2.10.300 - Multiple DAGs.feature @@ -6,7 +6,7 @@ I want to see that Data Access Groups is functioning as expected Scenario: B.2.10.300.100 Assign user multiple DAGs and DAG Switcher #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.10.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.10.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_RECORD_DAG_ASSIGN When I click on "Record Status Dashboard" diff --git a/Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature b/Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature index c47b0bb5..7494d464 100644 --- a/Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature +++ b/Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature @@ -6,7 +6,7 @@ I want to see that Data Access Groups is functioning as expected Scenario: B.2.10.500.100 Assign DAG to record #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.10.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.10.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "Record Status Dashboard" And I click on the link labeled "2" diff --git a/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature b/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature index 16b0d96f..8d50f309 100644 --- a/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature +++ b/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature @@ -7,7 +7,7 @@ Scenario: B.2.10.600.100 Unique DAGs #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.10.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.10.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "Record Status Dashboard" And I click on the link labeled "3" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature index 8900a42d..2520c18c 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature @@ -6,7 +6,7 @@ I want to see that Manage project user access is functioning as expected Scenario: B.3.15.100.100 Enable/Disable survey in Online Designer #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.3.15.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.3.15.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "Project Setup" #PARENT #B.6.4.1300.100 diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public survey link.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public survey link.feature index f3d3dda7..35a23709 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public survey link.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public survey link.feature @@ -6,7 +6,7 @@ I want to see that Manage project user access is functioning as expected Scenario: B.3.15.1300.100 Public survey link #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.3.15.1300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.3.15.1300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #FUNCTIONAL REQUIREMENT ##ACTION - 1st instrument is not set-up as survey diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature index 7b2641a1..41ca9c5a 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature @@ -6,7 +6,7 @@ I want to see that Manage project user access is functioning as expected Scenario: B.3.15.200.100 Survey Online/Offline Status #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.3.15.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.3.15.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the button labeled "Move project to production" diff --git a/Feature Tests/B/Export data/B.5.21.200 - Export format.feature b/Feature Tests/B/Export data/B.5.21.200 - Export format.feature index b73fd70e..53f35692 100644 --- a/Feature Tests/B/Export data/B.5.21.200 - Export format.feature +++ b/Feature Tests/B/Export data/B.5.21.200 - Export format.feature @@ -7,7 +7,7 @@ Scenario: B.5.21.200.100 Export data format #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.5.21.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.5.21.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #FUNCTIONAL_REQUIREMENT ##ACTION: export CSV raw diff --git a/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature b/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature index 0a323292..f6c9a6e5 100644 --- a/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature +++ b/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature @@ -7,7 +7,7 @@ Scenario: B.5.21.400.100 Export select forms #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.5.21.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.5.21.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #FUNCTIONAL_REQUIREMENT ##ACTION: export CSV and confirm column diff --git a/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature b/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature index d0fda40c..ad0084b8 100644 --- a/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature +++ b/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature @@ -6,7 +6,7 @@ I want to see that Logging Module is functioning as expected Scenario: B.2.23.100.100 Logging module records changes #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.23.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.23.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature b/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature index 94cf2f0f..353108e6 100644 --- a/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature +++ b/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature @@ -6,7 +6,7 @@ I want to see that Logging Module is functioning as expected Scenario: B.2.23.200.100 Logging module export #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.23.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.23.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "My Projects" And I click on the link labeled "B.2.23.200.100" diff --git a/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature b/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature index d35827ae..8bb0dd1a 100644 --- a/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature +++ b/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature @@ -6,7 +6,7 @@ I want to see that Logging Module is functioning as expected Scenario: B.2.23.300.100 Logging module filter function #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.23.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.23.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "My Projects" And I click on the link labeled "B.2.23.300.100" diff --git a/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature b/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature index 647d4199..997707fe 100644 --- a/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature +++ b/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature @@ -6,7 +6,7 @@ I want to see that Logging Module is functioning as expected Scenario: B.2.23.400.100 Logging module security #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.23.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.2.23.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "My Projects" And I click on the link labeled "B.2.23.400.100" diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature index 90962c64..20465944 100644 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature @@ -6,7 +6,7 @@ I want to see that Project Setup is functioning as expected Scenario: B.4.27.300.100 Change project longitudinal status ##SETUP_DEV Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.4.27.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.4.27.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button ##ACTION Verify event exist ##VERIFY_RSD When I click on the link labeled "Record Status Dashboard" diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature index f950353e..db4f5a6b 100644 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature @@ -6,7 +6,7 @@ I want to see that Project Setup is functioning as expected Scenario: B.4.27.400.100 Ability to designate data collection instruments for defined events in each arm ##SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.4.27.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.4.27.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature index 67478364..bc8c2579 100644 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature @@ -6,7 +6,7 @@ I want to see that Manage project user access is functioning as expected Scenario: B.4.27.700.100 Admin delete events and arm in Define My Events #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.4.27.700.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.4.27.700.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the button labeled "Move project to production" diff --git a/Feature Tests/B/My Projects/B.6.13.200 - My project dashboard archive hide.feature b/Feature Tests/B/My Projects/B.6.13.200 - My project dashboard archive hide.feature index 8ae4bad8..867e73f5 100644 --- a/Feature Tests/B/My Projects/B.6.13.200 - My project dashboard archive hide.feature +++ b/Feature Tests/B/My Projects/B.6.13.200 - My project dashboard archive hide.feature @@ -5,7 +5,7 @@ I want to see that My Project is functioning as expected Scenario: B.6.13.200.100 Hide archived projects Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.13.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.13.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "Other Functionality" And I click on the button "Mark project as Completed" And I click on the button "Mark project as Completed" in the dialog box diff --git a/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature b/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature index 2073bf09..1f5e5c36 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature @@ -7,7 +7,7 @@ Scenario: B.6.7.1800.100 Designating field as required through the Online Design #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.7.1800.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.7.1800.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button ##SETUP_PRODUCTION When I click on the link labeled "My Projects" diff --git a/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature b/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature index 93e0cf67..6fa02a66 100644 --- a/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature +++ b/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature @@ -7,7 +7,7 @@ Scenario: B.6.7.400.100 Copy instrument ##SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.7.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.7.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" diff --git a/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature b/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature index 6f14c56b..c8d550de 100644 --- a/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature +++ b/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature @@ -6,7 +6,7 @@ I want to see that Project Setup is functioning as expected Scenario: B.6.4.1100.100 Erase all data only in development as User ##SETUP_DEV Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.6.4.1100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.4.1100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button ##ACTION Verify record exist ##VERIFY_RSD When I click on the link labeled "Record Status Dashboard" @@ -44,7 +44,7 @@ And I logout Scenario: B.6.4.1100.200 Erase all data in production mode as Admin ##SETUP_PRODUCTION Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.4.1100.200.PROD" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.4.1100.200.PROD" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box diff --git a/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature b/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature index 80d4c189..48b9616f 100644 --- a/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature +++ b/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature @@ -59,7 +59,7 @@ And I click on the button labeled "Close" in the dialog box Scenario: B.6.4.1200.300 Projects in production with records require admin ##SETUP_PRODUCTION Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.6.4.1200.300.PROD" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.4.1200.300.PROD" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "My Projects" And I click on the link labeled " B.6.4.1200.300.PROD" diff --git a/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature b/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature index a60b52f5..1ede4d4c 100644 --- a/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature +++ b/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature @@ -6,7 +6,7 @@ I want to see that Manage project user access is functioning as expected Scenario: B.6.4.1400.100 Ability to create repeating surveys #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.6.4.1400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.4.1400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #VERIFY_SETUP repeat instrument When I click on the link labeled "Project Setup" Then I should see a button labeled "Modify" on the field labeled "Repeating instruments and events" diff --git a/Feature Tests/B/Project Setup/B.6.4.800 - Project setup title.feature b/Feature Tests/B/Project Setup/B.6.4.800 - Project setup title.feature index 694590d2..c6e9f364 100644 --- a/Feature Tests/B/Project Setup/B.6.4.800 - Project setup title.feature +++ b/Feature Tests/B/Project Setup/B.6.4.800 - Project setup title.feature @@ -6,7 +6,7 @@ I want to see that Project Setup is functioning as expected Scenario: B.6.4.800.100 Customize project title #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.6.4.800.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.4.800.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "My Projects" And I click on the link labeled "B.6.4.800.100" And I click on the link labeled "Project Setup" diff --git a/Feature Tests/B/Project Setup/B.6.4.900 - Project setup purpose.feature b/Feature Tests/B/Project Setup/B.6.4.900 - Project setup purpose.feature index fc247d2b..192db2c2 100644 --- a/Feature Tests/B/Project Setup/B.6.4.900 - Project setup purpose.feature +++ b/Feature Tests/B/Project Setup/B.6.4.900 - Project setup purpose.feature @@ -6,7 +6,7 @@ I want to see that Project Setup is functioning as expected Scenario: B.6.4.900.100 Change project purpose designation #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.6.4.900.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.4.900.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the link labeled "My Projects" And I click on the link labeled "B.6.4.900.100" And I click on the link labeled "Project Setup" diff --git a/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature b/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature index c6c78a2a..d7314789 100644 --- a/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature +++ b/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature @@ -7,7 +7,7 @@ Scenario: B.6.11.200.100 Move project from development to production to analysis #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.11.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.11.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #FUNCTIONAL REQUIREMENT ##ACTION: move to production diff --git a/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature b/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature index 651b524e..1ba72356 100644 --- a/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature +++ b/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature @@ -6,7 +6,7 @@ I want to see that My Project is functioning as expected Scenario: B.6.11.300.100 Move project from development to production while keeping data #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.6.11.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.11.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #FUNCTIONAL REQUIREMENT ##ACTION: move to production @@ -27,7 +27,7 @@ Then I should see "1" Scenario: B.6.11.300.200 Move project from development to production while deleting data #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.11.300.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "B.6.11.300.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #FUNCTIONAL REQUIREMENT ##ACTION: move to production diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature index c6fc1965..443f1d8b 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature @@ -7,7 +7,7 @@ Scenario: C.2.19.100.100 Display locked and e-signed status #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.2.19.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.2.19.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature index bcf971c5..bf0c65a0 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature @@ -7,7 +7,7 @@ Scenario: C.2.19.100.100 Display locked and e-signed status #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.2.19.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.2.19.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature index 2795924f..6b6b8bd2 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature @@ -6,7 +6,7 @@ I want to see that Record locking and E-signatures is functioning as expected Scenario: C.2.19.300.100 Record locking and E-signatures filtering #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.2.19.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.2.19.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature index 272c50b2..2e5a2dba 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature @@ -6,7 +6,7 @@ I want to see that Record locking and E-signatures is functioning as expected Scenario: C.2.19.400.100 display lock status #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.2.19.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.2.19.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature index dcbe39f2..aff99c29 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature @@ -7,7 +7,7 @@ Scenario: C.2.19.500.100 Display e-signature #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.2.19.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.2.19.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature index 56655797..d805ba50 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature @@ -7,7 +7,7 @@ Scenario: C.2.19.600.100 Navigate to record #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.2.19.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.2.19.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature index 30947c8b..91de76ca 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature @@ -6,7 +6,7 @@ I want to see that Record locking and E-signatures is functioning as expected Scenario: C.2.19.700.100 Customize Record Locking display and text #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.2.19.700.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.2.19.700.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature index d056fadd..dbad2737 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature @@ -7,7 +7,7 @@ Scenario: C.2.19.900.100 Enable user rights for Record Locking Customization mod #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "C.2.19.900.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.2.19.900.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #USER_RIGHTS When I click on the link labeled "User Rights" diff --git a/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature b/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature index 22eec027..60cb7641 100644 --- a/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature +++ b/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature @@ -5,7 +5,7 @@ I want to see that Reporting is functioning as expected #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.5.22.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.5.22.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature b/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature index 3406923f..9278c8c4 100644 --- a/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature +++ b/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature @@ -5,7 +5,7 @@ I want to see that Reporting is functioning as expected #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "C.5.22.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml" and clicking the "Create Project" button +And I create a new project named "C.5.22.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" From 6fd951fc28a4bb40bc5a1ff4748fc4b37cbef00e Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:09:03 -0500 Subject: [PATCH 06/96] Fix the syntax error for all radios across all features --- .../A.3.26.100 - public file share.feature | 2 +- .../A.6.11.100 - limit project status.feature | 4 ++-- .../B.2.6.100 - Basic Privileges.feature | 2 +- .../B.2.6.200 - Data Entry Form Access.feature | 2 +- .../B.2.6.300 - Data Export Rights.feature | 2 +- .../B.4.9.100 - branching logic.feature | 4 ++-- .../B.3.16.100 - Data import template.feature | 2 +- .../B.3.16.1000 - Data import access.feature | 2 +- .../B.3.16.1200 - Data import overwrite.feature | 2 +- .../B.3.16.1300 - Data import dag.feature | 2 +- ...200 - Data import create modify records.feature | 2 +- ...3.16.400 - Data import field validation.feature | 2 +- .../B.3.16.500 - Data import codes.feature | 2 +- ...6.600 - Data import survey id timestamp.feature | 2 +- .../B.3.16.700 - Data import longitudinal.feature | 2 +- .../B.3.16.800 - Data import repeat.feature | 2 +- .../B.3.16.900 - Data import locked.feature | 2 +- .../B.3.14.100 - create record.feature | 2 +- .../B.3.14.1000 - Delete Form Data.feature | 2 +- .../B.3.14.1100 -Delete Record Data.feature | 2 +- .../B.3.14.1200 - Delete Record.feature | 2 +- .../B.3.14.200 - Field Type Data Entry.feature | 2 +- ....14.300 - Multiple choice-radio button.feature | 2 +- .../B.3.14.400 - Date time fields.feature | 2 +- .../B.3.14.500 - Leave without save.feature | 2 +- .../B.3.14.600 - Save options.feature | 2 +- .../B.3.14.700 - Form status option.feature | 2 +- .../B.3.14.900 - Rename record.feature | 2 +- .../B.3.15.100 - Enable Form into Survey.feature | 2 +- .../B.3.15.1000 - Survey participant list.feature | 2 +- .../B.3.15.1100 - Survey track response.feature | 2 +- ...Disabled survey removes survey metadata.feature | 2 +- .../B.3.15.200 - Survey status.feature | 2 +- ... - Survey distribution participant list.feature | 2 +- .../B.3.15.400 - Survey open from form.feature | 2 +- ...3.15.500 - Survey mode alerts form mode.feature | 2 +- .../B.3.15.800 - Survey edit.feature | 2 +- .../B.3.15.900 - Survey status.feature | 2 +- ...B.4.20.300 - Change requires draft mode.feature | 2 +- .../Draft mode/B.4.20.400 - Draft summary.feature | 2 +- .../Draft mode/B.4.20.800 - Draft warning.feature | 2 +- .../B.4.20.900 - Draft version control.feature | 2 +- .../B/Export data/B.5.21.100 - Export PHI.feature | 10 +++++----- .../Export data/B.5.21.200 - Export format.feature | 14 +++++++------- .../Export data/B.5.21.300 - Export fields.feature | 2 +- .../B.5.21.400 - Export select forms.feature | 2 +- .../Export data/B.5.21.600 - Export access.feature | 2 +- .../B.4.8.300 - Field Ranges.feature | 2 +- .../B.2.23.100 - Record Changes.feature | 2 +- .../B.2.23.200 - Export Audit Trail.feature | 2 +- .../B.2.23.300 - Filtering Ability.feature | 2 +- .../B.2.23.400 - Module Security.feature | 2 +- .../B.4.27.300 - Longitudinal.feature | 2 +- .../B.4.27.400 - Longitudinal Events.feature | 2 +- ....4.27.700 - Longitudinal Admin Required.feature | 2 +- .../B.6.7.1000 - Field Multiple Choice.feature | 2 +- .../B.6.7.1200 - Field checkbox.feature | 2 +- .../B.6.7.1300 - Field signature.feature | 2 +- .../B.6.7.1400 - Field file upload.feature | 2 +- .../B.6.7.1500 - Field descriptive.feature | 2 +- .../B.6.7.1600 - Field section.feature | 2 +- .../B.6.7.1800 - Field required.feature | 2 +- .../B.6.7.1900 - Field management.feature | 2 +- .../B.6.7.300 - Forms - Rename Instruments.feature | 2 +- .../B.6.7.400 - Forms - Copy Instruments.feature | 2 +- .../B.6.7.500 - Forms - Delete instruments.feature | 4 ++-- ...B.6.7.600 - Forms - Reorder Instruments.feature | 2 +- .../B.6.7.800 - Field Notes.feature | 2 +- .../B.6.7.900 - Field Calculated.feature | 2 +- .../B.6.4.1000 - Project copy.feature | 2 +- .../B.6.4.1100 - Erase data in dev.feature | 4 ++-- .../B.6.4.1200 - Delete project.feature | 8 ++++---- .../B.6.4.1400 - Repeat survey.feature | 2 +- .../B.6.11.200 - Move project status.feature | 2 +- ...management during project status change.feature | 4 ++-- ...C.4.18.100 - Data Quality default rules.feature | 2 +- .../C.4.18.1000 - Data Quality realtime.feature | 2 +- .../C.4.18.1300 - Data Quality DAG.feature | 2 +- ...1400 - Data Quality support user rights.feature | 2 +- .../C.4.18.200 - Data Quality create rules.feature | 2 +- ...C.4.18.300 - Data Quality execute rules.feature | 2 +- .../C.4.18.500 - Data Quality disrepancies.feature | 2 +- ...C.4.18.600 - Data Quality exclude rules.feature | 2 +- .../C.4.18.700 - Data Quality edit rules.feature | 2 +- .../C.3.26.300 - File Repository folders.feature | 2 +- .../C.2.19.100 - Lock status.feature | 2 +- .../C.2.19.200 - Lock form display.feature | 2 +- .../C.2.19.300 - Locking record filter.feature | 2 +- .../C.2.19.400 - Lock status display.feature | 4 ++-- .../C.2.19.500 - esign display.feature | 4 ++-- .../C.2.19.600 - Locking module navigation.feature | 4 ++-- .../C.2.19.700 - esign customization.feature | 2 +- .../C.2.19.900 - Esign and Lock access.feature | 8 ++++---- .../C/Reporting/C.5.22.100 - Report access.feature | 4 ++-- .../C.5.22.200 - Report Management.feature | 2 +- .../C.3.24.100 - eConsent enable.feature | 8 ++++---- .../C.3.24.200 - eConsent footer.feature | 8 ++++---- .../C.3.24.300 - eConsent status.feature | 4 ++-- .../C.3.24.600 - eConsent edit.feature | 4 ++-- .../C.3.24.800 - eConsent repeat.feature | 4 ++-- 100 files changed, 134 insertions(+), 134 deletions(-) diff --git a/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature b/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature index 4355d599..50574243 100644 --- a/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature +++ b/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature @@ -15,7 +15,7 @@ And I click on the button labeled "Auto-Archiver enabled + e-Consent Framework" ##SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature b/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature index c7fb1356..5f54b897 100644 --- a/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature +++ b/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature @@ -34,7 +34,7 @@ And I click on the link labeled "A.6.11.100.100" ##ACTION: Test user requests move to production And I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "Yes, Request Admin to Move to Production Status" in the dialog box ##VERIFY Then I should see "Success! Your request to move the project to production status has been sent to a REDCap administrator. " @@ -66,7 +66,7 @@ Given I login to REDCap with the user "Test_User1" ##ACTION: Test user move to production And I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "Yes, Move to Production Status" in the dialog box ##VERIFY diff --git a/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature b/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature index 3a373c3e..8fac6949 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature @@ -13,7 +13,7 @@ And I click on the link labeled "My Projects" And I click on the link labeled "B.2.6.100.100" And I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature b/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature index 5400175d..0b823de3 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature @@ -11,7 +11,7 @@ And I create a new project named "B.2.6.200.100" by clicking on "New Project" in When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature b/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature index d05db38f..be61d834 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature @@ -10,7 +10,7 @@ And I create a new project named "B.2.6.300.100" by clicking on "New Project" in When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Branching logic/B.4.9.100 - branching logic.feature b/Feature Tests/B/Branching logic/B.4.9.100 - branching logic.feature index 1cb92b91..b84af7c6 100644 --- a/Feature Tests/B/Branching logic/B.4.9.100 - branching logic.feature +++ b/Feature Tests/B/Branching logic/B.4.9.100 - branching logic.feature @@ -94,13 +94,13 @@ When I click on the link labeled "Designer" And I click on the button labeled "Leave without saving changes" in the dialog box And I click on the instrument labeled "Data Types" And I click on the Branching Logic icon for the field labeled "Descriptive Text with File" -And I click on the radio button labeled "Drag-N-Drop Logic Builder" +And I click on the radio labeled "Drag-N-Drop Logic Builder" And I drag the field choice labeled "radio_button_manual = Choice101 (101)" to the box labeled "Show the field only if" And I click on the button labeled "Save" Then I should see "Branching logic: [radio_button_manual] = '101'" on the field labeled "Descriptive Text with File" When I click on the Branching Logic icon for the field labeled "Required" -And I click on the radio button labeled "Drag-N-Drop Logic Builder" +And I click on the radio labeled "Drag-N-Drop Logic Builder" And I drag the field choice labeled "checkbox = Checkbox (3)" to the box labeled "Show the field only if" And I click on the button labeled "Save" Then I should see "Branching logic: [checkbox(3)] = '1'" on the field labeled "Required" diff --git a/Feature Tests/B/Data import/B.3.16.100 - Data import template.feature b/Feature Tests/B/Data import/B.3.16.100 - Data import template.feature index 99311e10..ec10da35 100644 --- a/Feature Tests/B/Data import/B.3.16.100 - Data import template.feature +++ b/Feature Tests/B/Data import/B.3.16.100 - Data import template.feature @@ -9,7 +9,7 @@ And I create a new project named "B.3.16.100.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Data import/B.3.16.1000 - Data import access.feature b/Feature Tests/B/Data import/B.3.16.1000 - Data import access.feature index a99b810b..3aac9471 100644 --- a/Feature Tests/B/Data import/B.3.16.1000 - Data import access.feature +++ b/Feature Tests/B/Data import/B.3.16.1000 - Data import access.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.16.1000.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature b/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature index 09519f66..7049f110 100644 --- a/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature +++ b/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.16.1200.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box And I click on the button labeled "Ok" in the pop-up box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Data import/B.3.16.1300 - Data import dag.feature b/Feature Tests/B/Data import/B.3.16.1300 - Data import dag.feature index 0d4b92d8..1a352a49 100644 --- a/Feature Tests/B/Data import/B.3.16.1300 - Data import dag.feature +++ b/Feature Tests/B/Data import/B.3.16.1300 - Data import dag.feature @@ -26,7 +26,7 @@ Then I should see a table header and rows containing the following values in the #SETUP_PRODUCTION Given I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Data import/B.3.16.200 - Data import create modify records.feature b/Feature Tests/B/Data import/B.3.16.200 - Data import create modify records.feature index 6e4cc519..c3755d99 100644 --- a/Feature Tests/B/Data import/B.3.16.200 - Data import create modify records.feature +++ b/Feature Tests/B/Data import/B.3.16.200 - Data import create modify records.feature @@ -7,7 +7,7 @@ And I create a new project named "B.3.16.200.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Data import/B.3.16.400 - Data import field validation.feature b/Feature Tests/B/Data import/B.3.16.400 - Data import field validation.feature index 5df2a5a4..47075e99 100644 --- a/Feature Tests/B/Data import/B.3.16.400 - Data import field validation.feature +++ b/Feature Tests/B/Data import/B.3.16.400 - Data import field validation.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.16.400.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Data import/B.3.16.500 - Data import codes.feature b/Feature Tests/B/Data import/B.3.16.500 - Data import codes.feature index 576f26bf..591f69dd 100644 --- a/Feature Tests/B/Data import/B.3.16.500 - Data import codes.feature +++ b/Feature Tests/B/Data import/B.3.16.500 - Data import codes.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.16.500.100" by clicking on "New Project" i #SETUP_PRODUCTION  When I click on the button labeled "Move project to production"   -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box  +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box  And I click on the button labeled "YES, Move to Production Status" in the dialog box  Then I see " Project status:  Production"  diff --git a/Feature Tests/B/Data import/B.3.16.600 - Data import survey id timestamp.feature b/Feature Tests/B/Data import/B.3.16.600 - Data import survey id timestamp.feature index 17581aca..54cf2dfa 100644 --- a/Feature Tests/B/Data import/B.3.16.600 - Data import survey id timestamp.feature +++ b/Feature Tests/B/Data import/B.3.16.600 - Data import survey id timestamp.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.16.600.100" by clicking on "New Project" i #SETUP_PRODUCTION  When I click on the button labeled "Move project to production"   -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box  +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box  And I click on the button labeled "YES, Move to Production Status" in the dialog box  Then I should see "Project status:  Production"  diff --git a/Feature Tests/B/Data import/B.3.16.700 - Data import longitudinal.feature b/Feature Tests/B/Data import/B.3.16.700 - Data import longitudinal.feature index 70f02381..3b2350e5 100644 --- a/Feature Tests/B/Data import/B.3.16.700 - Data import longitudinal.feature +++ b/Feature Tests/B/Data import/B.3.16.700 - Data import longitudinal.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.16.700.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Data import/B.3.16.800 - Data import repeat.feature b/Feature Tests/B/Data import/B.3.16.800 - Data import repeat.feature index 9814caa4..cb98fab0 100644 --- a/Feature Tests/B/Data import/B.3.16.800 - Data import repeat.feature +++ b/Feature Tests/B/Data import/B.3.16.800 - Data import repeat.feature @@ -18,7 +18,7 @@ Then I should see "Successfully saved!" #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Delete ALL data in the project" in the dialog box +And I click on the radio labeled "Delete ALL data in the project" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box And I click on the button labeled "Ok" in the pop-up box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Data import/B.3.16.900 - Data import locked.feature b/Feature Tests/B/Data import/B.3.16.900 - Data import locked.feature index cd7acc50..318c7047 100644 --- a/Feature Tests/B/Data import/B.3.16.900 - Data import locked.feature +++ b/Feature Tests/B/Data import/B.3.16.900 - Data import locked.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.16.900.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - create record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - create record.feature index eb8b4041..4ddb4d07 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - create record.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - create record.feature @@ -10,7 +10,7 @@ And I create a new project named " B.3.14.100.100 " by clicking on "New Project" When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1000 - Delete Form Data.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1000 - Delete Form Data.feature index 984359e3..ddb47ed3 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1000 - Delete Form Data.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1000 - Delete Form Data.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.14.000.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature index ba2de3c7..fd66a87f 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.14.1100.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature index 572b4d99..ce22702a 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.14.1200.100" by clicking on "New Project" #SETUP_PRODUCTION When click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.200 - Field Type Data Entry.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.200 - Field Type Data Entry.feature index cd2fdad8..8b504c9c 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.200 - Field Type Data Entry.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.200 - Field Type Data Entry.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.3.14.200.100" And I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature index 6589cff4..e97d5286 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.14.300.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Date time fields.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Date time fields.feature index d6f535ed..5e7a011f 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Date time fields.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Date time fields.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.14.400.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without save.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without save.feature index 6cb316e7..bda59c0d 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without save.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without save.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.14.500.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save options.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save options.feature index 6139bc37..fb5d6a79 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save options.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save options.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.14.600.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status option.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status option.feature index 2145f573..2ba0cd8e 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status option.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status option.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.14.700.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename record.feature index 0ba04393..72687a4a 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename record.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename record.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.14.900.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature index 2520c18c..57f87dd4 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature @@ -14,7 +14,7 @@ Then I should see a button labeled "Disable" on the field labeled "Use surveys i #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey participant list.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey participant list.feature index 5f9e28aa..769bc14e 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey participant list.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey participant list.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.15.1000.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey track response.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey track response.feature index 43b3d983..4d67127b 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey track response.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey track response.feature @@ -13,7 +13,7 @@ And I create a new project named "B.3.15.1100.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled survey removes survey metadata.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled survey removes survey metadata.feature index d02c4987..a9357fa6 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled survey removes survey metadata.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled survey removes survey metadata.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.15.1200.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature index 41ca9c5a..a1028c4a 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature @@ -10,7 +10,7 @@ And I create a new project named "B.3.15.200.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see " Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey distribution participant list.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey distribution participant list.feature index ba188504..3efc802d 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey distribution participant list.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey distribution participant list.feature @@ -10,7 +10,7 @@ And I create a new project named "B.3.15.300.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Survey open from form.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Survey open from form.feature index bded2108..c4d58318 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Survey open from form.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Survey open from form.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.15.400.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey mode alerts form mode.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey mode alerts form mode.feature index 355e84c4..4d92454a 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey mode alerts form mode.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey mode alerts form mode.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.15.500.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Survey edit.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Survey edit.feature index f70cfaa4..828b33f5 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Survey edit.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Survey edit.feature @@ -11,7 +11,7 @@ And I create a new project named "B.3.15.800.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey status.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey status.feature index 1a8fa248..b4da46b4 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey status.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey status.feature @@ -12,7 +12,7 @@ And I create a new project named "B.3.15.900.100" by clicking on "New Project" i #SETUP_PRODUCTION When I cclick on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Draft mode/B.4.20.300 - Change requires draft mode.feature b/Feature Tests/B/Draft mode/B.4.20.300 - Change requires draft mode.feature index 3e2c2550..435a3a8c 100644 --- a/Feature Tests/B/Draft mode/B.4.20.300 - Change requires draft mode.feature +++ b/Feature Tests/B/Draft mode/B.4.20.300 - Change requires draft mode.feature @@ -12,7 +12,7 @@ And I create a new project named "B.4.20.300.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see Project Status: "Production" diff --git a/Feature Tests/B/Draft mode/B.4.20.400 - Draft summary.feature b/Feature Tests/B/Draft mode/B.4.20.400 - Draft summary.feature index fdd6207e..38d18d3c 100644 --- a/Feature Tests/B/Draft mode/B.4.20.400 - Draft summary.feature +++ b/Feature Tests/B/Draft mode/B.4.20.400 - Draft summary.feature @@ -12,7 +12,7 @@ And I create a new project named "B.4.20.400.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see Project Status: "Production" diff --git a/Feature Tests/B/Draft mode/B.4.20.800 - Draft warning.feature b/Feature Tests/B/Draft mode/B.4.20.800 - Draft warning.feature index 47ecffdd..9ae7b943 100644 --- a/Feature Tests/B/Draft mode/B.4.20.800 - Draft warning.feature +++ b/Feature Tests/B/Draft mode/B.4.20.800 - Draft warning.feature @@ -12,7 +12,7 @@ And I create a new project named "B.4.20.800.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see Project Status: "Production" diff --git a/Feature Tests/B/Draft mode/B.4.20.900 - Draft version control.feature b/Feature Tests/B/Draft mode/B.4.20.900 - Draft version control.feature index 2f2344a0..edafcc66 100644 --- a/Feature Tests/B/Draft mode/B.4.20.900 - Draft version control.feature +++ b/Feature Tests/B/Draft mode/B.4.20.900 - Draft version control.feature @@ -12,7 +12,7 @@ And I create a new project named "B.4.20.900.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see Project Status: "Production" diff --git a/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature b/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature index 34497a89..89f05c19 100644 --- a/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature +++ b/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature @@ -63,7 +63,7 @@ Then I should see a table row containing the following values in the reports tab ##ACTION: export all Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -81,7 +81,7 @@ And I click on the button labeled "Close" in the dialog box When I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table And I click on the checkbox button labeled "Remove All Identifier Fields (tagged in Data Dictionary)" And I click on the checkbox button labeled "Hash the Record ID field (converts record name to an unrecognizable value)" -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -102,7 +102,7 @@ And I deselect the checkbox button labeled "Remove All Identifier Fields (tagged And I deselect the checkbox button labeled "Hash the Record ID field (converts record name to an unrecognizable value)" And I click on the checkbox button labeled "Remove unvalidated Text fields (i.e. Text fields other than dates, numbers, etc.)" And I click on the checkbox button labeled "Remove Notes/Essay box fields" -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -119,7 +119,7 @@ FUNCTIONAL_REQUIREMENT ##ACTION: remove date, datetime fields When I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table And I click on the checkbox button labeled "Remove all date and datetime fields" -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -154,7 +154,7 @@ Given I click on the link labeled "Data Exports, Reports, and Stats" When I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table And I click on the checkbox button labeled "Shift all dates by value between 0 and 364 days" And I click on the checkbox button labeled "Also shift all survey completion timestamps by value between 0 and 364 days" -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" And I should see "All dates within your data have been DATE SHIFTED to an unknown value between 0 and 364 days." diff --git a/Feature Tests/B/Export data/B.5.21.200 - Export format.feature b/Feature Tests/B/Export data/B.5.21.200 - Export format.feature index 53f35692..fd60db18 100644 --- a/Feature Tests/B/Export data/B.5.21.200 - Export format.feature +++ b/Feature Tests/B/Export data/B.5.21.200 - Export format.feature @@ -16,7 +16,7 @@ Then I should see a table row containing the following values in the reports tab | A | All data (all records and fields) | Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -29,7 +29,7 @@ And I click on the button labeled "Close" in the dialog box #FUNCTIONAL_REQUIREMENT ##ACTION: export CSV (labels) Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "CSV / Microsoft Excel (labels)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (labels)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -42,7 +42,7 @@ And I click on the button labeled "Close" in the dialog box #FUNCTIONAL_REQUIREMENT ##ACTION: export SPSS Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "SPSS Statistical Software" in the dialog box +And I click on the radio labeled "SPSS Statistical Software" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -55,7 +55,7 @@ And I click on the button labeled "Close" in the dialog box #FUNCTIONAL_REQUIREMENT ##ACTION: export SAS Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "SAS Statistical Software" in the dialog box +And I click on the radio labeled "SAS Statistical Software" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -68,7 +68,7 @@ And I click on the button labeled "Close" in the dialog box #FUNCTIONAL_REQUIREMENT ##ACTION: export R Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "R Statistical Software" in the dialog box +And I click on the radio labeled "R Statistical Software" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -81,7 +81,7 @@ And I click on the button labeled "Close" in the dialog box #FUNCTIONAL_REQUIREMENT ##ACTION: export STATA Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "Stata Statistical Software" in the dialog box +And I click on the radio labeled "Stata Statistical Software" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" @@ -94,7 +94,7 @@ And I click on the button labeled "Close" in the dialog box #FUNCTIONAL_REQUIREMENT ##ACTION: export XML Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "CDISC ODM (XML)" in the dialog box +And I click on the radio labeled "CDISC ODM (XML)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" diff --git a/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature b/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature index 7281f93b..82e3a01f 100644 --- a/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature +++ b/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature @@ -15,7 +15,7 @@ Then I should see a table row containing the following values in the reports tab | A | All data (all records and fields) | Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" diff --git a/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature b/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature index f6c9a6e5..c9717289 100644 --- a/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature +++ b/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature @@ -19,7 +19,7 @@ Given I click on the "Make custom selections" button for "Selected instruments a When I select the dropdown option labeled "Text Validation" from the dropdown labeled "Instruments" And I select the dropdown option labeled "Event (Arm 1: Arm 1)" from the dropdown labeled "Events" And I click on the button labeled "Export Data" -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" diff --git a/Feature Tests/B/Export data/B.5.21.600 - Export access.feature b/Feature Tests/B/Export data/B.5.21.600 - Export access.feature index d01bdde9..c1619a7e 100644 --- a/Feature Tests/B/Export data/B.5.21.600 - Export access.feature +++ b/Feature Tests/B/Export data/B.5.21.600 - Export access.feature @@ -17,7 +17,7 @@ Then I should see a table row containing the following values in the reports tab #VERIFY: can export Given I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" diff --git a/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature b/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature index f4109c69..bae910d1 100644 --- a/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature +++ b/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature @@ -13,7 +13,7 @@ And I create a new project named "B.4.8.300.100" by clicking on "New Project" in #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature b/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature index ad0084b8..608dc923 100644 --- a/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature +++ b/Feature Tests/B/Logging Module/B.2.23.100 - Record Changes.feature @@ -11,7 +11,7 @@ And I create a new project named "B.2.23.100.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature b/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature index 353108e6..3e04ea61 100644 --- a/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature +++ b/Feature Tests/B/Logging Module/B.2.23.200 - Export Audit Trail.feature @@ -13,7 +13,7 @@ And I click on the link labeled "B.2.23.200.100" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature b/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature index 8bb0dd1a..648002c9 100644 --- a/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature +++ b/Feature Tests/B/Logging Module/B.2.23.300 - Filtering Ability.feature @@ -13,7 +13,7 @@ And I click on the link labeled "B.2.23.300.100" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature b/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature index 997707fe..db5cc20e 100644 --- a/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature +++ b/Feature Tests/B/Logging Module/B.2.23.400 - Module Security.feature @@ -13,7 +13,7 @@ And I click on the link labeled "B.2.23.400.100" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature index 20465944..bf1d2943 100644 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature @@ -51,7 +51,7 @@ Then I should see a table header and rows including the following values in the ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature index db4f5a6b..2811e641 100644 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature @@ -11,7 +11,7 @@ And I create a new project named "B.4.27.400.100" by clicking on "New Project" i ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature index bc8c2579..f20d1e51 100644 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature @@ -10,7 +10,7 @@ And I create a new project named "B.4.27.700.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see "Project status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.1000 - Field Multiple Choice.feature b/Feature Tests/B/Online Designer/B.6.7.1000 - Field Multiple Choice.feature index cce0fac1..6feca25e 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1000 - Field Multiple Choice.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1000 - Field Multiple Choice.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.1000.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.1200 - Field checkbox.feature b/Feature Tests/B/Online Designer/B.6.7.1200 - Field checkbox.feature index 3dc0fc74..7ee69e15 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1200 - Field checkbox.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1200 - Field checkbox.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.1200.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.1300 - Field signature.feature b/Feature Tests/B/Online Designer/B.6.7.1300 - Field signature.feature index 8e8f80ae..54692016 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1300 - Field signature.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1300 - Field signature.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.1300.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.1400 - Field file upload.feature b/Feature Tests/B/Online Designer/B.6.7.1400 - Field file upload.feature index 06b83370..7994c2ff 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1400 - Field file upload.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1400 - Field file upload.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.1400.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.1500 - Field descriptive.feature b/Feature Tests/B/Online Designer/B.6.7.1500 - Field descriptive.feature index f4a46363..0ea2838c 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1500 - Field descriptive.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1500 - Field descriptive.feature @@ -15,7 +15,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.1500.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.1600 - Field section.feature b/Feature Tests/B/Online Designer/B.6.7.1600 - Field section.feature index 6c37dfbd..5f9ea233 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1600 - Field section.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1600 - Field section.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.1600.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature b/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature index 1f5e5c36..e19a347d 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.1800.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.1900 - Field management.feature b/Feature Tests/B/Online Designer/B.6.7.1900 - Field management.feature index 22f97a91..c8674baa 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1900 - Field management.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1900 - Field management.feature @@ -20,7 +20,7 @@ Then I should see "Test User1" within the "1_FullRights" row of the column label ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" And I logout diff --git a/Feature Tests/B/Online Designer/B.6.7.300 - Forms - Rename Instruments.feature b/Feature Tests/B/Online Designer/B.6.7.300 - Forms - Rename Instruments.feature index 4b76580a..3b060f30 100644 --- a/Feature Tests/B/Online Designer/B.6.7.300 - Forms - Rename Instruments.feature +++ b/Feature Tests/B/Online Designer/B.6.7.300 - Forms - Rename Instruments.feature @@ -38,7 +38,7 @@ Then I should see a table header and rows including the following values in the ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature b/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature index 6fa02a66..481a888c 100644 --- a/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature +++ b/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature @@ -12,7 +12,7 @@ And I create a new project named "B.6.7.400.100" by clicking on "New Project" in ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.500 - Forms - Delete instruments.feature b/Feature Tests/B/Online Designer/B.6.7.500 - Forms - Delete instruments.feature index d85949ea..1a4fbd03 100644 --- a/Feature Tests/B/Online Designer/B.6.7.500 - Forms - Delete instruments.feature +++ b/Feature Tests/B/Online Designer/B.6.7.500 - Forms - Delete instruments.feature @@ -12,7 +12,7 @@ And I create a new project named "B.6.7.500.100" by clicking on "New Project" in ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" @@ -64,7 +64,7 @@ And I click on the link labeled "B.6.7.600.100" ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.600 - Forms - Reorder Instruments.feature b/Feature Tests/B/Online Designer/B.6.7.600 - Forms - Reorder Instruments.feature index 1b7c4917..464b3e56 100644 --- a/Feature Tests/B/Online Designer/B.6.7.600 - Forms - Reorder Instruments.feature +++ b/Feature Tests/B/Online Designer/B.6.7.600 - Forms - Reorder Instruments.feature @@ -15,7 +15,7 @@ And I click on the link labeled "B.6.7.600.100" ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.800 - Field Notes.feature b/Feature Tests/B/Online Designer/B.6.7.800 - Field Notes.feature index 43426a00..cb2939a8 100644 --- a/Feature Tests/B/Online Designer/B.6.7.800 - Field Notes.feature +++ b/Feature Tests/B/Online Designer/B.6.7.800 - Field Notes.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.800.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Online Designer/B.6.7.900 - Field Calculated.feature b/Feature Tests/B/Online Designer/B.6.7.900 - Field Calculated.feature index 10eefc25..8de26eba 100644 --- a/Feature Tests/B/Online Designer/B.6.7.900 - Field Calculated.feature +++ b/Feature Tests/B/Online Designer/B.6.7.900 - Field Calculated.feature @@ -13,7 +13,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.7.900.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Project Setup/B.6.4.1000 - Project copy.feature b/Feature Tests/B/Project Setup/B.6.4.1000 - Project copy.feature index 4aa06776..172be9ac 100644 --- a/Feature Tests/B/Project Setup/B.6.4.1000 - Project copy.feature +++ b/Feature Tests/B/Project Setup/B.6.4.1000 - Project copy.feature @@ -42,7 +42,7 @@ Given I click on the link labeled "My Projects" And I click on the link labeled "B.6.4.1000.100" And I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature b/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature index c8d550de..de7c0796 100644 --- a/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature +++ b/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature @@ -30,7 +30,7 @@ Then I should see "No records exist yet" ##SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" @@ -47,7 +47,7 @@ Given I login to REDCap with the user "Test_Admin" And I create a new project named "B.6.4.1100.200.PROD" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature b/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature index 48b9616f..e11ebe98 100644 --- a/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature +++ b/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature @@ -7,7 +7,7 @@ Scenario: B.6.4.1200.100 Projects in development can be deleted by user ##SETUP_DEV Given I login to REDCap with the user "Test_User1" And I create a new project named "B.6.4.1200.100.DEV" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown -And I click on the radio button labeled "Empty project (blank slate)" +And I click on the radio labeled "Empty project (blank slate)" And I click on the button labeled "Create Project" Then I should see "B.6.4.1200.100.DEV" @@ -30,7 +30,7 @@ Scenario: B.6.4.1200.200 Projects in production with no records can be deleted b ##SETUP_PRODUCTION Given I login to REDCap with the user "Test_User1" Given I create a new project named "B.6.4.1200.200.PROD" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown -And I click on the radio button labeled "Empty project (blank slate)" +And I click on the radio labeled "Empty project (blank slate)" And I click on the button labeled "Create Project" Then I should see "B.6.4.1200.200.PROD" @@ -38,7 +38,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled " B.6.4.1200.200.PROD" And I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" @@ -65,7 +65,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled " B.6.4.1200.300.PROD" And I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" diff --git a/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature b/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature index 1ede4d4c..862a5f9e 100644 --- a/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature +++ b/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature @@ -13,7 +13,7 @@ Then I should see a button labeled "Modify" on the field labeled "Repeating inst #SETUP_PRODUCTION When I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I see " Project status: Production" diff --git a/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature b/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature index d7314789..f3a3c6c0 100644 --- a/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature +++ b/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature @@ -13,7 +13,7 @@ And I create a new project named "B.6.11.200.100" by clicking on "New Project" i ##ACTION: move to production When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "Yes, Move to Production Status" in the dialog box ##VERIFY Then I should see "Project status: Production" diff --git a/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature b/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature index 1ba72356..5474adf4 100644 --- a/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature +++ b/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature @@ -14,7 +14,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.11.300.100" And I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "Yes, Move to Production Status" in the dialog box ##VERIFY Then I should see "Project status: Production" @@ -35,7 +35,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "B.6.11.300.200" And I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Delete ALL data" in the dialog box +And I click on the radio labeled "Delete ALL data" in the dialog box And I click on the button labeled "Yes, Move to Production Status" in the dialog box And I click on the button labeled "OK" in the pop-up box ##VERIFY diff --git a/Feature Tests/C/Data Quality/C.4.18.100 - Data Quality default rules.feature b/Feature Tests/C/Data Quality/C.4.18.100 - Data Quality default rules.feature index f0fcaf9a..70665d5b 100644 --- a/Feature Tests/C/Data Quality/C.4.18.100 - Data Quality default rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.100 - Data Quality default rules.feature @@ -12,7 +12,7 @@ And I create a new project named "C.4.18.100.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature b/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature index e85831ea..4ba7ad68 100644 --- a/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature +++ b/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature @@ -12,7 +12,7 @@ And I create a new project named "C.4.18.1000.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Data Quality/C.4.18.1300 - Data Quality DAG.feature b/Feature Tests/C/Data Quality/C.4.18.1300 - Data Quality DAG.feature index 55157f5a..a0042a49 100644 --- a/Feature Tests/C/Data Quality/C.4.18.1300 - Data Quality DAG.feature +++ b/Feature Tests/C/Data Quality/C.4.18.1300 - Data Quality DAG.feature @@ -13,7 +13,7 @@ And I create a new project named "C.4.18.1300.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Data Quality/C.4.18.1400 - Data Quality support user rights.feature b/Feature Tests/C/Data Quality/C.4.18.1400 - Data Quality support user rights.feature index f51cef48..dc437339 100644 --- a/Feature Tests/C/Data Quality/C.4.18.1400 - Data Quality support user rights.feature +++ b/Feature Tests/C/Data Quality/C.4.18.1400 - Data Quality support user rights.feature @@ -12,7 +12,7 @@ And I create a new project named "C.4.18.1400.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Data Quality/C.4.18.200 - Data Quality create rules.feature b/Feature Tests/C/Data Quality/C.4.18.200 - Data Quality create rules.feature index 4c7a81cb..b1aa0705 100644 --- a/Feature Tests/C/Data Quality/C.4.18.200 - Data Quality create rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.200 - Data Quality create rules.feature @@ -13,7 +13,7 @@ And I create a new project named "C.4.18.200.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Data Quality/C.4.18.300 - Data Quality execute rules.feature b/Feature Tests/C/Data Quality/C.4.18.300 - Data Quality execute rules.feature index 3f0fea12..76440035 100644 --- a/Feature Tests/C/Data Quality/C.4.18.300 - Data Quality execute rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.300 - Data Quality execute rules.feature @@ -11,7 +11,7 @@ And I create a new project named "C.4.18.300.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" #FUNCTIONAL REQUIREMENT diff --git a/Feature Tests/C/Data Quality/C.4.18.500 - Data Quality disrepancies.feature b/Feature Tests/C/Data Quality/C.4.18.500 - Data Quality disrepancies.feature index 51ed5e29..7e4a584f 100644 --- a/Feature Tests/C/Data Quality/C.4.18.500 - Data Quality disrepancies.feature +++ b/Feature Tests/C/Data Quality/C.4.18.500 - Data Quality disrepancies.feature @@ -11,7 +11,7 @@ And I create a new project named "C.4.18.500.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box ##ACTION executing all rules. diff --git a/Feature Tests/C/Data Quality/C.4.18.600 - Data Quality exclude rules.feature b/Feature Tests/C/Data Quality/C.4.18.600 - Data Quality exclude rules.feature index d955dcd9..9e215e76 100644 --- a/Feature Tests/C/Data Quality/C.4.18.600 - Data Quality exclude rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.600 - Data Quality exclude rules.feature @@ -11,7 +11,7 @@ And I create a new project named "C.4.18.600.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box ##ACTION executing all rules. diff --git a/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature b/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature index f49b1024..da31087a 100644 --- a/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature @@ -12,7 +12,7 @@ And I create a new project named "C.4.18.700.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box #USER_RIGHTS When I click on the link labeled "User Rights" diff --git a/Feature Tests/C/File Repository/C.3.26.300 - File Repository folders.feature b/Feature Tests/C/File Repository/C.3.26.300 - File Repository folders.feature index 2abfa48b..86c62c12 100644 --- a/Feature Tests/C/File Repository/C.3.26.300 - File Repository folders.feature +++ b/Feature Tests/C/File Repository/C.3.26.300 - File Repository folders.feature @@ -14,7 +14,7 @@ And I click on the link labeled "A.3.26.300.100" #SETUP Export data automatically placed in file repo Given I click on the link labeled "Data Exports, Reports, and Stats" And I click on the "Export Data" button for "All data (all records and fields)" report in the My Reports & Exports table -And I click on the radio button labeled "CSV / Microsoft Excel (raw data)" in the dialog box +And I click on the radio labeled "CSV / Microsoft Excel (raw data)" in the dialog box And I click on the button labeled "Export Data" in the dialog box Then I should see a dialog containing the following text: "Data export was successful!" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature index 443f1d8b..d668b12b 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.100 - Lock status.feature @@ -12,7 +12,7 @@ And I create a new project named "C.2.19.100.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature index bf0c65a0..8d6de079 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.200 - Lock form display.feature @@ -12,7 +12,7 @@ And I create a new project named "C.2.19.100.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature index 6b6b8bd2..c0c7d46c 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.300 - Locking record filter.feature @@ -11,7 +11,7 @@ And I create a new project named "C.2.19.300.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature index 2e5a2dba..b674163e 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.400 - Lock status display.feature @@ -11,7 +11,7 @@ And I create a new project named "C.2.19.400.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" @@ -22,7 +22,7 @@ And I click on the button labeled "Add with custom rights" Then I should see "Adding new user "test_user1"" When I click on the checkbox for the field labeled "Record Locking Customization" -And I click on the radio button labeled "Locking / Unlocking" for the field labeled "Lock / Unlock Records (instrument level)" +And I click on the radio labeled "Locking / Unlocking" for the field labeled "Lock / Unlock Records (instrument level)" And I click on the checkbox for the field labeled "Lock/Unlock *Entire* Records (record level)" And I click on the button labeled "Add user" And I click on the checkbox for the field labeled "Logging" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature index aff99c29..e9eb8dae 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature @@ -12,7 +12,7 @@ And I create a new project named "C.2.19.500.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" @@ -24,7 +24,7 @@ Then I should see "Adding new user "test_user1"" When I click on the checkbox for the field labeled "Logging" And I click on the checkbox for the field labeled "Record Locking Customization" -And I click on the radio button labeled "Locking / Unlocking with E-signature authority" for the field labeled "Lock / Unlock Records (instrument level)" +And I click on the radio labeled "Locking / Unlocking with E-signature authority" for the field labeled "Lock / Unlock Records (instrument level)" And I click on the button labeled "Close" in the dialog box And I click on the button labeled "Add user" Then I should see "User "test_user1" was successfully added" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature index d805ba50..de9a0716 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.600 - Locking module navigation.feature @@ -12,7 +12,7 @@ And I create a new project named "C.2.19.600.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" @@ -23,7 +23,7 @@ And I click on the button labeled "Add with custom rights" Then I should see "Adding new user "test_user1"" When I click on the checkbox for the field labeled "Record Locking Customization" -And I click on the radio button labeled "Locking / Unlocking with E-signature authority" for the field labeled "Lock / Unlock Records (instrument level)" +And I click on the radio labeled "Locking / Unlocking with E-signature authority" for the field labeled "Lock / Unlock Records (instrument level)" And I click on the button labeled "Close" in the dialog box And I click on the checkbox for the field labeled "Lock/Unlock *Entire* Records (record level)" And I click on the button labeled "Add user" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature index 91de76ca..ea12db4f 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature @@ -11,7 +11,7 @@ And I create a new project named "C.2.19.700.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature index dbad2737..601e7aa2 100644 --- a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature +++ b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature @@ -16,7 +16,7 @@ And I click on the button labeled "Edit user privileges" Then I should see "Editing existing user "test_user1"" When I click on the checkbox for the field labeled "Record Locking Customization" -And I click on the radio button labeled "Locking / Unlocking with E-signature authority" for the field labeled "Lock / Unlock Records (instrument level)" +And I click on the radio labeled "Locking / Unlocking with E-signature authority" for the field labeled "Lock / Unlock Records (instrument level)" And I click on the button labeled "Close" in the dialog box And I click on the checkbox for the field labeled "Lock/Unlock *Entire* Records (record level)" And I click on the button labeled "Save changes" @@ -44,7 +44,7 @@ And I click on the button labeled "Edit user privileges" Then I should see "Editing existing user "test_user1"" When I deselect the checkbox for the field labeled "Record Locking Customization" -And I click on the radio button labeled "Disabled" for the field labeled "Lock / Unlock Records (instrument level)" +And I click on the radio labeled "Disabled" for the field labeled "Lock / Unlock Records (instrument level)" And I verify the checkbox for the field labeled "Lock/Unlock *Entire* Records (record level)" is not checked And I click on the button labeled "Save Changes" Then I should see "User "test_user1" was successfully edited" @@ -61,7 +61,7 @@ And I should NOT see the link labeled "Customize and Manage the Record Locking a ##SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" @@ -87,7 +87,7 @@ And I verify the checkbox for the field labeled "Lock/Unlock *Entire* Records (r ##USER_RIGHTS When I click on the checkbox for the field labeled "Record Locking Customization" -And I click on the radio button labeled "Locking / Unlocking with E-signature authority" for the field labeled "Lock / Unlock Records (instrument level)" +And I click on the radio labeled "Locking / Unlocking with E-signature authority" for the field labeled "Lock / Unlock Records (instrument level)" And I click on the button labeled "Close" in the dialog box And I click on the checkbox for the field labeled "Lock/Unlock *Entire* Records (record level)" And I click on the button labeled "Save Changes" diff --git a/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature b/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature index 60cb7641..3da7933f 100644 --- a/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature +++ b/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature @@ -10,7 +10,7 @@ And I create a new project named "C.5.22.100.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" @@ -140,7 +140,7 @@ Then I should see "Edit Existing Report: "C.5.22.100.100 REPORT" When I click on the radio button labeled "Custom user access" for the field labeled "View Access" And I select "test_user1" from the dropdown field labeled "Selected users" And I select "test_user2" from the dropdown field labeled "Selected users" -And I click on the radio button labeled "Custom user access" for the field labeled "Edit Access" +And I click on the radio labeled "Custom user access" for the field labeled "Edit Access" And I select "test_user1" from the dropdown field labeled "Selected users" And I click on the button labeled "Save Report" Then I should see "Your report has been saved!" in the dialog box diff --git a/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature b/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature index 9278c8c4..c307fdb6 100644 --- a/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature +++ b/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature @@ -10,7 +10,7 @@ And I create a new project named "C.5.22.200.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project status: Production" diff --git a/Feature Tests/C/e-Consent framework/C.3.24.100 - eConsent enable.feature b/Feature Tests/C/e-Consent framework/C.3.24.100 - eConsent enable.feature index e40a4e81..f9aedc2a 100644 --- a/Feature Tests/C/e-Consent framework/C.3.24.100 - eConsent enable.feature +++ b/Feature Tests/C/e-Consent framework/C.3.24.100 - eConsent enable.feature @@ -12,7 +12,7 @@ And I create a new project named " C.3.24.100.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" @@ -20,7 +20,7 @@ Then I should see "Project Status: Production" ##ACTION: e-consent survey settings - disabled When I click on the link labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Disabled" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Disabled" for the field labeled "e-Consent Framework" And I click on the button labeled "Save Changes" Then I should see "Your survey settings were successfully saved!" @@ -54,7 +54,7 @@ Then I should see a table header and rows including the following values in the #FUNCTIONAL_REQUIREMENTauto-archive enabled When I click on the link labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Auto-Archiver enabled" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Auto-Archiver enabled" for the field labeled "e-Consent Framework" And I click on the button labeled "Save Changes" Then I should see "Your survey settings were successfully saved!" @@ -90,7 +90,7 @@ Then I should see a table header and rows including the following values in the ##ACTION: e-consent survey settings - auto-archive and e-consent When I click on the link labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" And I click on the button labeled "Save Changes" Then I should see "Your survey settings were successfully saved!" diff --git a/Feature Tests/C/e-Consent framework/C.3.24.200 - eConsent footer.feature b/Feature Tests/C/e-Consent framework/C.3.24.200 - eConsent footer.feature index 98ef66c0..abb0d72e 100644 --- a/Feature Tests/C/e-Consent framework/C.3.24.200 - eConsent footer.feature +++ b/Feature Tests/C/e-Consent framework/C.3.24.200 - eConsent footer.feature @@ -12,14 +12,14 @@ And I create a new project named " C.3.24.200.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" #SETUP_eConsent When I click on the button labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" And I verify I see "version test" in the field labeled "e-Consent version:" And I verify I see "fname "Name"" in the field labeled "First name field:" And I verify I see "lname "Name"" in the field labeled "Last name field:" @@ -300,7 +300,7 @@ Then I should have a pdf file with the following values in the footer: "Version: #SETUP_eConsent_change field When I click on the button labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" And I enter "UPDATED VERSION TEST" in the field labeled "e-Consent version:" And I verify I see "fname "Name"" in the field labeled "First name field:" And I verify I see "lname "Name"" in the field labeled "Last name field:" @@ -359,7 +359,7 @@ Then I should have a pdf file with the following values in the footer: "Name Nam #SETUP_eConsent_change field When I click on the button labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Auto-Archiver enabled" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Auto-Archiver enabled" for the field labeled "e-Consent Framework" And I click on the button labeled "Save Changes" Then I should see "Your survey settings were successfully saved!" diff --git a/Feature Tests/C/e-Consent framework/C.3.24.300 - eConsent status.feature b/Feature Tests/C/e-Consent framework/C.3.24.300 - eConsent status.feature index 808a74ae..b3a7d427 100644 --- a/Feature Tests/C/e-Consent framework/C.3.24.300 - eConsent status.feature +++ b/Feature Tests/C/e-Consent framework/C.3.24.300 - eConsent status.feature @@ -12,7 +12,7 @@ And I create a new project named " C.3.24.300.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" @@ -27,7 +27,7 @@ Then I should see "Successfully saved!" #SETUP_eConsent When I click on the button labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" And I click on the button labeled "Save Changes" Then I should see "Your survey settings were successfully saved!" diff --git a/Feature Tests/C/e-Consent framework/C.3.24.600 - eConsent edit.feature b/Feature Tests/C/e-Consent framework/C.3.24.600 - eConsent edit.feature index 8b232f42..0c7ef28b 100644 --- a/Feature Tests/C/e-Consent framework/C.3.24.600 - eConsent edit.feature +++ b/Feature Tests/C/e-Consent framework/C.3.24.600 - eConsent edit.feature @@ -12,14 +12,14 @@ And I create a new project named " C.3.24.600.100" by clicking on "New Project" #SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" ##ACTION: e-consent survey settings - auto-archive and e-consent When I click on the link labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" And I click on the button labeled "Save Changes" Then I should see "Your survey settings were successfully saved!" diff --git a/Feature Tests/C/e-Consent framework/C.3.24.800 - eConsent repeat.feature b/Feature Tests/C/e-Consent framework/C.3.24.800 - eConsent repeat.feature index 50f3981e..d2e5fc80 100644 --- a/Feature Tests/C/e-Consent framework/C.3.24.800 - eConsent repeat.feature +++ b/Feature Tests/C/e-Consent framework/C.3.24.800 - eConsent repeat.feature @@ -12,7 +12,7 @@ And I create a new project named "C.3.24.800.100" by clicking on "New Project" i #SETUP_PRODUCTION When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" -And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box Then I should see "Project Status: Production" @@ -27,7 +27,7 @@ Then I should see "Successfully saved!" #SETUP_eConsent When I click on the button labeled "Designer" And I click on the button labeled "Survey settings" for the instrument labeled "Consent" -And I click on the radio button labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" +And I click on the radio labeled "Auto-Archiver + e-Consent Framework" for the field labeled "e-Consent Framework" And I click on the button labeled "Save Changes" Then I should see "Your survey settings were successfully saved!" From 51236a48f5d2a76ccee8cb932ba59f2017efdf25 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:17:28 -0500 Subject: [PATCH 07/96] Update A.6.11.100 - limit project status.feature --- .../A.6.11.100 - limit project status.feature | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/A/{Project status => Project Status}/A.6.11.100 - limit project status.feature (100%) diff --git a/Feature Tests/A/Project status/A.6.11.100 - limit project status.feature b/Feature Tests/A/Project Status/A.6.11.100 - limit project status.feature similarity index 100% rename from Feature Tests/A/Project status/A.6.11.100 - limit project status.feature rename to Feature Tests/A/Project Status/A.6.11.100 - limit project status.feature From 9e358b222e01d16ccfefa6fc0d24a0110da7b5aa Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:17:58 -0500 Subject: [PATCH 08/96] Fix syntax error on this project creation step for features --- .../B.3.14.1100 -Delete Record Data.feature | 2 +- .../B.3.14.1200 - Delete Record.feature | 2 +- Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature | 2 +- Feature Tests/B/Export data/B.5.21.300 - Export fields.feature | 2 +- Feature Tests/B/Export data/B.5.21.600 - Export access.feature | 2 +- .../B/Field validation/B.4.8.300 - Field Ranges.feature | 2 +- .../C.4.18.100 - Data Quality default rules.feature | 2 +- .../C/Data Quality/C.4.18.1000 - Data Quality realtime.feature | 2 +- .../C/Data Quality/C.4.18.1300 - Data Quality DAG.feature | 2 +- .../C.4.18.1400 - Data Quality support user rights.feature | 2 +- .../Data Quality/C.4.18.200 - Data Quality create rules.feature | 2 +- .../C.4.18.300 - Data Quality execute rules.feature | 2 +- .../Data Quality/C.4.18.500 - Data Quality disrepancies.feature | 2 +- .../C.4.18.600 - Data Quality exclude rules.feature | 2 +- .../C/Data Quality/C.4.18.700 - Data Quality edit rules.feature | 2 +- 15 files changed, 15 insertions(+), 15 deletions(-) diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature index fd66a87f..95e52392 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature @@ -7,7 +7,7 @@ Scenario: B.3.14.1100.100 Delete all data in an event for a given record #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.3.14.1100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_3.14.xml" and clicking the "Create Project" button +And I create a new project named "B.3.14.1100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_3.14.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature index ce22702a..9e4c2e1a 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1200 - Delete Record.feature @@ -7,7 +7,7 @@ Scenario: B.3.14.1200.100 Delete record #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.3.14.1200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_3.14.xml" and clicking the "Create Project" button +And I create a new project named "B.3.14.1200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_3.14.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When click on the link labeled "Project Setup" diff --git a/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature b/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature index 89f05c19..50cdfa1d 100644 --- a/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature +++ b/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature @@ -6,7 +6,7 @@ I want to see that export data is functioning as expected Scenario: B.5.21.100.100 Limit identified data export #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.5.21.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_5.21.xml" and clicking the "Create Project" button +And I create a new project named "B.5.21.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_5.21.xml", and clicking the "Create Project" button #SETUP_USER_RIGHTS When I click on the link labeled "User Rights" diff --git a/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature b/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature index 82e3a01f..d66b43df 100644 --- a/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature +++ b/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature @@ -6,7 +6,7 @@ I want to see that export data is functioning as expected Scenario: B.5.21.300.100 Export all fields #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.5.21.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_5.21.xml" and clicking the "Create Project" button +And I create a new project named "B.5.21.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_5.21.xml", and clicking the "Create Project" button #FUNCTIONAL_REQUIREMENT ##ACTION: export CSV and confirm column diff --git a/Feature Tests/B/Export data/B.5.21.600 - Export access.feature b/Feature Tests/B/Export data/B.5.21.600 - Export access.feature index c1619a7e..480b484d 100644 --- a/Feature Tests/B/Export data/B.5.21.600 - Export access.feature +++ b/Feature Tests/B/Export data/B.5.21.600 - Export access.feature @@ -7,7 +7,7 @@ Scenario: B.5.21.600.100 Restrict users from exporting data #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.5.21.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_5.21.xml" and clicking the "Create Project" button +And I create a new project named "B.5.21.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_5.21.xml", and clicking the "Create Project" button #FUNCTIONAL_REQUIREMENT ##ACTION: export CSV and confirm can export diff --git a/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature b/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature index bae910d1..9b898e74 100644 --- a/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature +++ b/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature @@ -8,7 +8,7 @@ Scenario: B.4.8.300.100 Field range validation #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.4.8.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_4.8.xml" and clicking the "Create Project" button +And I create a new project named "B.4.8.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_4.8.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Data Quality/C.4.18.100 - Data Quality default rules.feature b/Feature Tests/C/Data Quality/C.4.18.100 - Data Quality default rules.feature index 70665d5b..91a7fda5 100644 --- a/Feature Tests/C/Data Quality/C.4.18.100 - Data Quality default rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.100 - Data Quality default rules.feature @@ -7,7 +7,7 @@ Scenario: C.4.18.100.100 Default data quality rules #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.4.18.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature b/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature index 4ba7ad68..41a865dd 100644 --- a/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature +++ b/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature @@ -7,7 +7,7 @@ Scenario: C.4.18.1000.100 Real-time rule execution #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.4.18.1000.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.1000.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Data Quality/C.4.18.1300 - Data Quality DAG.feature b/Feature Tests/C/Data Quality/C.4.18.1300 - Data Quality DAG.feature index a0042a49..ce0d0a9d 100644 --- a/Feature Tests/C/Data Quality/C.4.18.1300 - Data Quality DAG.feature +++ b/Feature Tests/C/Data Quality/C.4.18.1300 - Data Quality DAG.feature @@ -8,7 +8,7 @@ Scenario: C.4.18.1300.100 DAG limits rule viewing #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.4.18.1300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.1300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Data Quality/C.4.18.1400 - Data Quality support user rights.feature b/Feature Tests/C/Data Quality/C.4.18.1400 - Data Quality support user rights.feature index dc437339..6424d11c 100644 --- a/Feature Tests/C/Data Quality/C.4.18.1400 - Data Quality support user rights.feature +++ b/Feature Tests/C/Data Quality/C.4.18.1400 - Data Quality support user rights.feature @@ -7,7 +7,7 @@ Scenario: C.4.18.1400.100 User access limit rule viewing #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.4.18.1400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.1400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Data Quality/C.4.18.200 - Data Quality create rules.feature b/Feature Tests/C/Data Quality/C.4.18.200 - Data Quality create rules.feature index b1aa0705..906a4b6b 100644 --- a/Feature Tests/C/Data Quality/C.4.18.200 - Data Quality create rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.200 - Data Quality create rules.feature @@ -8,7 +8,7 @@ Scenario: C.4.18.200.100 Data quality rule creation #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.4.18.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" diff --git a/Feature Tests/C/Data Quality/C.4.18.300 - Data Quality execute rules.feature b/Feature Tests/C/Data Quality/C.4.18.300 - Data Quality execute rules.feature index 76440035..78f60f81 100644 --- a/Feature Tests/C/Data Quality/C.4.18.300 - Data Quality execute rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.300 - Data Quality execute rules.feature @@ -7,7 +7,7 @@ Scenario: C.4.18.300.100 Executing data quality rule #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.4.18.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" diff --git a/Feature Tests/C/Data Quality/C.4.18.500 - Data Quality disrepancies.feature b/Feature Tests/C/Data Quality/C.4.18.500 - Data Quality disrepancies.feature index 7e4a584f..78560f87 100644 --- a/Feature Tests/C/Data Quality/C.4.18.500 - Data Quality disrepancies.feature +++ b/Feature Tests/C/Data Quality/C.4.18.500 - Data Quality disrepancies.feature @@ -7,7 +7,7 @@ Scenario: C.4.18.500.100 View discrepancies #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.4.18.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" diff --git a/Feature Tests/C/Data Quality/C.4.18.600 - Data Quality exclude rules.feature b/Feature Tests/C/Data Quality/C.4.18.600 - Data Quality exclude rules.feature index 9e215e76..2d40757f 100644 --- a/Feature Tests/C/Data Quality/C.4.18.600 - Data Quality exclude rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.600 - Data Quality exclude rules.feature @@ -7,7 +7,7 @@ Scenario: C.4.18.600.100 Exclude discrepancies #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "C.4.18.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" diff --git a/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature b/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature index da31087a..8672cccb 100644 --- a/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature @@ -7,7 +7,7 @@ Scenario: C.4.18.700.100 Edit rule #SETUP Given I login to REDCap with the user "Test_User1" -And I create a new project named "C.4.18.700.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project418.xml" and clicking the "Create Project" button +And I create a new project named "C.4.18.700.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project418.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" From 1152a4ffbb289f94ae4c38826d9105f17ca1ae21 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:33:04 -0500 Subject: [PATCH 09/96] Add missing scenario titles --- Feature Tests/C/Reporting/C.5.22.100 - Report access.feature | 2 ++ .../C/Reporting/C.5.22.200 - Report Management.feature | 2 ++ 2 files changed, 4 insertions(+) diff --git a/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature b/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature index 3da7933f..97c4db74 100644 --- a/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature +++ b/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature @@ -3,6 +3,8 @@ Feature: User Interface: The system shall support the ability to assign the User As a REDCap end user I want to see that Reporting is functioning as expected +Scenario: C.5.22.100.100 - MISSING SCENARIO TITLE + #SETUP Given I login to REDCap with the user "Test_Admin" And I create a new project named "C.5.22.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button diff --git a/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature b/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature index c307fdb6..51e6293c 100644 --- a/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature +++ b/Feature Tests/C/Reporting/C.5.22.200 - Report Management.feature @@ -3,6 +3,8 @@ Feature: User Interface: The system shall support the ability to create, modify As a REDCap end user I want to see that Reporting is functioning as expected +Scenario: C.5.22.200.100 - MISSING SCENARIO TITLE + #SETUP Given I login to REDCap with the user "Test_User1" And I create a new project named "C.5.22.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button From a868590753f818a2ee9053be8ef2812c5cf29556 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:46:21 -0500 Subject: [PATCH 10/96] More adjustments --- ...r.feature => A.6.4.1500 - Enable & Disable Survey.feature} | 0 ...00 - Enable & Disable Editing of Survey Responses.feature} | 0 ...eate record.feature => B.3.14.100 - Create record.feature} | 0 ...ture => B.3.14.300 - Multiple choice-radio button.feature} | 0 ...feature => C.3.26.200 - View Access & User Rights.feature} | 2 +- ...rs.feature => C.3.26.300 - Storage & Organization.feature} | 4 ++-- ...File Repository.feature => C.3.26.400 - REDUNDANT.feature} | 0 ...File Repository.feature => C.3.26.500 - REDUNDANT.feature} | 0 ...port access.feature => C.5.22.100 - Report Access.feature} | 0 9 files changed, 3 insertions(+), 3 deletions(-) rename Feature Tests/A/Project Setup/{A.6.4.1500 - enable survey control center.feature => A.6.4.1500 - Enable & Disable Survey.feature} (100%) rename Feature Tests/A/Project Setup/{A.6.4.1600 - survey edit enable control center.feature => A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.100 - create record.feature => B.3.14.100 - Create record.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.300 - Multiple choice-radio button.feature => B.3.14.300 - Multiple choice-radio button.feature} (100%) rename Feature Tests/C/File Repository/{C.3.26.200 - File Repository viewing.feature => C.3.26.200 - View Access & User Rights.feature} (98%) rename Feature Tests/C/File Repository/{C.3.26.300 - File Repository folders.feature => C.3.26.300 - Storage & Organization.feature} (98%) rename Feature Tests/C/File Repository/{C.3.26.400 - File Repository.feature => C.3.26.400 - REDUNDANT.feature} (100%) rename Feature Tests/C/File Repository/{C.3.26.500 - File Repository.feature => C.3.26.500 - REDUNDANT.feature} (100%) rename Feature Tests/C/Reporting/{C.5.22.100 - Report access.feature => C.5.22.100 - Report Access.feature} (100%) diff --git a/Feature Tests/A/Project Setup/A.6.4.1500 - enable survey control center.feature b/Feature Tests/A/Project Setup/A.6.4.1500 - Enable & Disable Survey.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.1500 - enable survey control center.feature rename to Feature Tests/A/Project Setup/A.6.4.1500 - Enable & Disable Survey.feature diff --git a/Feature Tests/A/Project Setup/A.6.4.1600 - survey edit enable control center.feature b/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.1600 - survey edit enable control center.feature rename to Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - create record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create record.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - create record.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create record.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature diff --git a/Feature Tests/C/File Repository/C.3.26.200 - File Repository viewing.feature b/Feature Tests/C/File Repository/C.3.26.200 - View Access & User Rights.feature similarity index 98% rename from Feature Tests/C/File Repository/C.3.26.200 - File Repository viewing.feature rename to Feature Tests/C/File Repository/C.3.26.200 - View Access & User Rights.feature index 1963ff09..6b066ce7 100644 --- a/Feature Tests/C/File Repository/C.3.26.200 - File Repository viewing.feature +++ b/Feature Tests/C/File Repository/C.3.26.200 - View Access & User Rights.feature @@ -7,7 +7,7 @@ Scenario: C.3.26.200.100 Limit user view and export access based on User Rights #SETUP Given I login to REDCap with the user "Test_Admin" -When I create a "New Project" named "A.3.26.200.100", select "Practice / Just for Fun" from the dropdown, choose file "Project_1.xml" and click on the "Create Project" button +When I create a new project named "A.3.26.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button And I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.200.100" diff --git a/Feature Tests/C/File Repository/C.3.26.300 - File Repository folders.feature b/Feature Tests/C/File Repository/C.3.26.300 - Storage & Organization.feature similarity index 98% rename from Feature Tests/C/File Repository/C.3.26.300 - File Repository folders.feature rename to Feature Tests/C/File Repository/C.3.26.300 - Storage & Organization.feature index 86c62c12..7b8e3e4f 100644 --- a/Feature Tests/C/File Repository/C.3.26.300 - File Repository folders.feature +++ b/Feature Tests/C/File Repository/C.3.26.300 - Storage & Organization.feature @@ -7,7 +7,7 @@ Scenario: C.3.26.300.100 Automatic uploading of data export logs into the data e #SETUP Given I login to REDCap with the user "Test_Admin" -When I create a "New Project" named "C.3.26.300.100", select "Practice / Just for Fun" from the dropdown, choose file "Project_1.xml" and click on the "Create Project" button +When I create a "New Project" named "C.3.26.300.100", select "Practice / Just for Fun" from the dropdown, choose file "Project_1.xml" and click on the "Create Project" button And I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.300.100" @@ -35,7 +35,7 @@ Scenario: C.3.26.300.300 Recycle bin function - permanently force delete #SETUP Given I login to REDCap with the user "Test_Admin" -When I create a "New Project" named "C.3.26.300.300", select "Practice / Just for Fun" from the dropdown, choose file "Project_1.xml" and click on the "Create Project" button +When I create a "New Project" named "C.3.26.300.300", select "Practice / Just for Fun" from the dropdown, choose file "Project_1.xml" and click on the "Create Project" button And I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.300.300" diff --git a/Feature Tests/C/File Repository/C.3.26.400 - File Repository.feature b/Feature Tests/C/File Repository/C.3.26.400 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/File Repository/C.3.26.400 - File Repository.feature rename to Feature Tests/C/File Repository/C.3.26.400 - REDUNDANT.feature diff --git a/Feature Tests/C/File Repository/C.3.26.500 - File Repository.feature b/Feature Tests/C/File Repository/C.3.26.500 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/File Repository/C.3.26.500 - File Repository.feature rename to Feature Tests/C/File Repository/C.3.26.500 - REDUNDANT.feature diff --git a/Feature Tests/C/Reporting/C.5.22.100 - Report access.feature b/Feature Tests/C/Reporting/C.5.22.100 - Report Access.feature similarity index 100% rename from Feature Tests/C/Reporting/C.5.22.100 - Report access.feature rename to Feature Tests/C/Reporting/C.5.22.100 - Report Access.feature From 7cdd817d4ab14b7df6645c8a6aa6cc29d6954ddb Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:47:37 -0500 Subject: [PATCH 11/96] Fix syntax errors on A.6.11.100 --- .../A.6.11.100 - limit project status.feature | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/Feature Tests/A/Project Status/A.6.11.100 - limit project status.feature b/Feature Tests/A/Project Status/A.6.11.100 - limit project status.feature index 5f54b897..f27374c1 100644 --- a/Feature Tests/A/Project Status/A.6.11.100 - limit project status.feature +++ b/Feature Tests/A/Project Status/A.6.11.100 - limit project status.feature @@ -40,13 +40,16 @@ And I click on the button labeled "Yes, Request Admin to Move to Production Stat Then I should see "Success! Your request to move the project to production status has been sent to a REDCap administrator. " ##VERIFY_LOG -When I click on the button labeled "Logging" - Then I should see a table header and rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | | test_user1 | Manage/Design | Send request to move project to production status| +When I click on the button labeled "Logging" +Then I should see a table header and rows containing the following values in the logging table: + | Username | Action | List of Data Changes OR Fields Exported | + | test_user1 | Manage/Design | Send request to move project to production status| ##ACTION: cancel request When I click on the link labeled "Project Setup" And I click on the button labeled "Cancel request" -And I click on the button labeled "Submit" in the dialog box Then I should see "Project status: Development" +And I click on the button labeled "Submit" in the dialog box +Then I should see "Project status: Development" And I logout #SETUP @@ -55,7 +58,9 @@ Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "User Settings" Then I should see "System-level User Settings" When I select "Yes, normal users can move projects to production" on the dropdown field labeled "Allow normal users to move projects to production?" -And I click on the button labeled "Save Changes" ##VERIFY Then I should see "Your system configuration values have now been changed!" +And I click on the button labeled "Save Changes" +##VERIFY +Then I should see "Your system configuration values have now been changed!" And I logout #SETUP @@ -73,6 +78,8 @@ And I click on the button labeled "Yes, Move to Production Status" in the dialog Then I should see "Project status: Production" ##VERIFY_LOG -When I click on the button labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | | test_user1 | Manage/Design | Move project to Production status | +When I click on the button labeled "Logging" +And I should see a table header and rows containing the following values in the logging table: + | Username | Action | List of Data Changes OR Fields Exported | + | test_user1 | Manage/Design | Move project to Production status | From a4ca3e122944664059a86871e3e9dd8e26b3a7b4 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:49:15 -0500 Subject: [PATCH 12/96] Update A.6.11.100 - Administrative Controls in Control Center.feature --- ....6.11.100 - Administrative Controls in Control Center.feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/A/Project Status/{A.6.11.100 - limit project status.feature => A.6.11.100 - Administrative Controls in Control Center.feature} (100%) diff --git a/Feature Tests/A/Project Status/A.6.11.100 - limit project status.feature b/Feature Tests/A/Project Status/A.6.11.100 - Administrative Controls in Control Center.feature similarity index 100% rename from Feature Tests/A/Project Status/A.6.11.100 - limit project status.feature rename to Feature Tests/A/Project Status/A.6.11.100 - Administrative Controls in Control Center.feature From ccdcac881c86ab1f178e25f9f45e17524be5506f Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:52:36 -0500 Subject: [PATCH 13/96] More syntax error fixes --- .../A.3.26.100 - public file share.feature | 7 ++++--- .../C.3.26.300 - Storage & Organization.feature | 8 ++++---- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature b/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature index 50574243..61d0185e 100644 --- a/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature +++ b/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature @@ -4,9 +4,10 @@ As a REDCap end user I want to see that file repository is functioning as expected Scenario: C.3.26.100.100 Enable/Disable file repository public links via Control Center -#SETUP Given I login to REDCap with the user "Test_Admin" -When I create a "New Project" named "A.3.26.100.100", select "Practice / Just for Fun" from the dropdown, choose file "Project_1.xml" and click on the "Create Project" button -And I click on the link labeled "My Projects" +#SETUP +Given I login to REDCap with the user "Test_Admin" +And I create a new project named "A.3.26.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_3.16.xml", and clicking the "Create Project" button +And I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.100.100" And I click the link labeled "Designer" And I click the button labeled "Survey Settings" for the instrument "Consent" diff --git a/Feature Tests/C/File Repository/C.3.26.300 - Storage & Organization.feature b/Feature Tests/C/File Repository/C.3.26.300 - Storage & Organization.feature index 7b8e3e4f..1da61489 100644 --- a/Feature Tests/C/File Repository/C.3.26.300 - Storage & Organization.feature +++ b/Feature Tests/C/File Repository/C.3.26.300 - Storage & Organization.feature @@ -7,8 +7,8 @@ Scenario: C.3.26.300.100 Automatic uploading of data export logs into the data e #SETUP Given I login to REDCap with the user "Test_Admin" -When I create a "New Project" named "C.3.26.300.100", select "Practice / Just for Fun" from the dropdown, choose file "Project_1.xml" and click on the "Create Project" button -And I click on the link labeled "My Projects" +And I create a new project named "C.3.26.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button +And I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.300.100" #SETUP Export data automatically placed in file repo @@ -35,8 +35,8 @@ Scenario: C.3.26.300.300 Recycle bin function - permanently force delete #SETUP Given I login to REDCap with the user "Test_Admin" -When I create a "New Project" named "C.3.26.300.300", select "Practice / Just for Fun" from the dropdown, choose file "Project_1.xml" and click on the "Create Project" button -And I click on the link labeled "My Projects" +And I create a new project named "C.3.26.300.300" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button +And I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.300.300" ##ACTION Upload to top tier file repo From 59d5e9a4e8a57da8edc18e96732ce675aaa98207 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 14:54:52 -0500 Subject: [PATCH 14/96] Update A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature --- ... - Enable & Disable Editing of Survey Responses.feature | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature b/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature index b05ec31f..077f40a1 100644 --- a/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature +++ b/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature @@ -34,7 +34,7 @@ Then I should see "Your system configuration values have now been changed!" ##VERIFY: Admin Go to user rights and look for the edit survey checkbox (should be there) Given I click on the link labeled "My Projects" When I click on the link labeled "A.6.4.1600.100" -nd I click on the link labeled "User Rights" +And I click on the link labeled "User Rights" And I click on the link labeled "test_admin" And I click on the button labeled "Edit user privileges" Then I should see the checkbox labeled "Edit user privileges" for the instrument labeled "Survey" @@ -68,4 +68,7 @@ Then I should see "EDITED SURVEY RESPONSE" in the field labeled "Name" ##VERIFY_LOG When I click the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | | test_admin | Update record 1 | name_survey = 'EDITED SURVEY RESPONSE ' | | [survey respondent] | Update Response 1 | name_survey = 'SURVEY RESPONSE ' | +Then I should see a table header and rows including the following values in the logging table: + | Username | Action | List of Data Changes OR Fields Exported | + | test_admin | Update record 1 | name_survey = 'EDITED SURVEY RESPONSE ' | + | [survey respondent] | Update Response 1 | name_survey = 'SURVEY RESPONSE ' | From 121d66869e58f31714112c06b613922a3d0cd2b0 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 16:37:21 -0500 Subject: [PATCH 15/96] Lots of renaming and adjustments --- ...A.2.3.400 - Assign Administrators and Account Managers.feature | 0 .../ A.1.5.100 - Browse Projects.feature | 0 .../A.4.8.100 - Enable field validation.feature | 0 ... file share.feature => A.3.26.100 - Public File Share.feature} | 0 .../A.2.12.100 - System Status.feature | 0 .../B.4.9.100 - Branching Logic.feature} | 0 .../B.3.16.100 - Import Templates - Columns & Rows.feature} | 0 .../B.3.16.1000 - Access Restrictions.feature} | 0 .../B.3.16.1200 - Overwrite Existing Data.feature} | 0 .../B.3.16.1300 - Data Import - DAGs.feature} | 0 .../B.3.16.200 - Create & Modify Records.feature} | 0 .../B/{Data import => Data Import}/B.3.16.300 - REDUNDANT.feature | 0 .../B.3.16.400 - Field Validation.feature} | 0 ....3.16.500 - Choices for Radios, Dropdowns, Checkboxes.feature} | 0 .../B.3.16.600 - Survey Data Import.feature} | 0 .../B.3.16.700 - Longitudinal Data Import.feature} | 0 .../B.3.16.800 - Repeat Instrument Import.feature} | 0 .../B.3.16.900 - Import Restrictions.feature} | 0 ...- Create record.feature => B.3.14.100 - Create Record.feature} | 0 ...cord Data.feature => B.3.14.1100 - Delete Record Data.feature} | 0 ... button.feature => B.3.14.300 - Radio button behavior.feature} | 0 ...e time fields.feature => B.3.14.400 - Datetime Fields.feature} | 0 ...us option.feature => B.3.14.700 - Form status options.feature} | 0 ...board.feature => B.3.14.800 - Record Status Dashboard.feature} | 0 ...- Rename record.feature => B.3.14.900 - Rename Record.feature} | 0 ...y.feature => B.3.15.100 - Enable Instrument as Survey.feature} | 0 ...list.feature => B.3.15.1000 - Survey Participant List.feature} | 0 ...nse.feature => B.3.15.1100 - Survey Response Tracking.feature} | 0 ...ata.feature => B.3.15.1200 - Disabled Survey Behavior.feature} | 0 ...rvey link.feature => B.3.15.1300 - Public Survey Link.feature} | 0 ...- Survey status.feature => B.3.15.200 - Survey Status.feature} | 0 ... => B.3.15.300 - Survey Distribution Participant List.feature} | 0 ...om form.feature => B.3.15.400 - Open Survey from Form.feature} | 0 ...ode.feature => B.3.15.500 - Survey Alerts and Prompts.feature} | 0 ...ey edit.feature => B.3.15.800 - Edit Survey Responses.feature} | 0 ...status.feature => B.3.15.900 - Survey Response Status.feature} | 0 .../B.4.20.100 - REDUNDANT.feature} | 0 .../B.4.20.300 - Instrument Behavior.feature} | 0 .../B.4.20.400 - Draft Mode Summary.feature} | 0 .../B.4.20.500 - REDUNDANT.feature} | 0 .../B.4.20.600 - REDUNDANT.feature} | 0 .../B.4.20.700 - REDUNDANT.feature} | 0 .../{Draft mode => Draft Mode}/B.4.20.800 - Draft warning.feature | 0 .../B.4.20.900 - Draft version control.feature | 0 .../{Export data => Export Data}/B.5.21.100 - Export PHI.feature | 0 .../B.5.21.200 - Export Data to External Format.feature} | 0 .../B.5.21.300 - Export All Fields.feature} | 0 .../B.5.21.400 - Export Specific Forms.feature} | 0 .../B.5.21.500 - REDUNDANT.feature} | 0 .../B.5.21.600 - User Access Restrictions.feature} | 0 .../B.4.8.200 - Text Validation.feature} | 0 .../B.4.8.300 - Field Ranges.feature | 0 ....100 - Longitudinal.feature => B.4.27.100 - REDUNDANT.feature} | 0 ....200 - Longitudinal.feature => B.4.27.200 - REDUNDANT.feature} | 0 ...7.300 - Enable & Disable Longitudinal Data Collection.feature} | 0 ...inal Events.feature => B.4.27.400 - Event Designation.feature} | 0 ...ms.feature => B.4.27.500 - Longitudinal Arms & Events.feature} | 0 ...ture => B.4.27.600 - Repeating Events and Instruments.feature} | 0 ... => B.4.27.700 - Longitudinal Administrative Controls.feature} | 0 ...shboard.feature => B.6.13.100 - My Projects Dashboard.feature} | 0 ...rchive hide.feature => B.6.13.200 - Archived Projects.feature} | 0 ...re => B.6.7.100 - New Instruments via Data Dictionary.feature} | 0 ...Field checkbox.feature => B.6.7.1200 - Field Checkbox.feature} | 0 ...eld signature.feature => B.6.7.1300 - Field Signature.feature} | 0 ...file upload.feature => B.6.7.1400 - Field File Upload.feature} | 0 ...iptive.feature => B.6.7.1500 - Field Descriptive Text.feature} | 0 ...eld section.feature => B.6.7.1600 - Field New Section.feature} | 0 ... identifier.feature => B.6.7.1700 - Identifier Fields.feature} | 0 ...ield required.feature => B.6.7.1800 - Required Fields.feature} | 0 ...d management.feature => B.6.7.1900 - Field Management.feature} | 0 ...e Instrument.feature => B.6.7.200 - Create Instrument.feature} | 0 ... Instruments.feature => B.6.7.300 - Rename Instrument.feature} | 0 ...py Instruments.feature => B.6.7.400 - Copy Instrument.feature} | 0 ... instruments.feature => B.6.7.500 - Delete Instrument.feature} | 0 ...Instruments.feature => B.6.7.600 - Reorder Instrument.feature} | 0 ...0 - Project copy.feature => B.6.4.1000 - Project Copy.feature} | 0 ...eature => B.6.4.1100 - Erase data in Development Mode.feature} | 0 ...Delete project.feature => B.6.4.1200 - Delete Project.feature} | 0 ...urvey.feature => B.6.4.1300 - Enable & Disable Survey.feature} | 0 ...peat survey.feature => B.6.4.1400 - Repeating Surveys.feature} | 0 ...ject setup title.feature => B.6.4.800 - Project Title.feature} | 0 ... setup purpose.feature => B.6.4.900 - Project Purpose.feature} | 0 .../B.6.11.200 - Move project status.feature | 0 ....11.300 - Data management during project status change.feature | 0 ...100 - Data Quality.feature => C.4.18.1100 - REDUNDANT.feature} | 0 ...200 - Data Quality.feature => C.4.18.1200 - REDUNDANT.feature} | 0 ....400 - Data Quality.feature => C.4.18.400 - REDUNDANT.feature} | 0 ....800 - Data Quality.feature => C.4.18.800 - REDUNDANT.feature} | 0 ....900 - Data Quality.feature => C.4.18.900 - REDUNDANT.feature} | 0 ...- esign display.feature => C.2.19.500 - eSign display.feature} | 0 ...omization.feature => C.2.19.700 - eSign customization.feature} | 0 ...00 - Esign and Lock.feature => C.2.19.800 - REDUNDANT.feature} | 0 ... access.feature => C.2.19.900 - eSign and Lock access.feature} | 0 ...3.24.400 - eConsent.feature => C.3.24.400 - REDUNDANT.feature} | 0 ...3.24.500 - eConsent.feature => C.3.24.500 - REDUNDANT.feature} | 0 95 files changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/A/{Assign administrators => Assign Administrators}/A.2.3.400 - Assign Administrators and Account Managers.feature (100%) rename Feature Tests/A/{Browse projects => Browse Projects}/ A.1.5.100 - Browse Projects.feature (100%) rename Feature Tests/A/{Field validation => Field Validation}/A.4.8.100 - Enable field validation.feature (100%) rename Feature Tests/A/File Repository/{A.3.26.100 - public file share.feature => A.3.26.100 - Public File Share.feature} (100%) rename Feature Tests/A/{Security settings => Security Settings}/A.2.12.100 - System Status.feature (100%) rename Feature Tests/B/{Branching logic/B.4.9.100 - branching logic.feature => Branching Logic/B.4.9.100 - Branching Logic.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.100 - Data import template.feature => Data Import/B.3.16.100 - Import Templates - Columns & Rows.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.1000 - Data import access.feature => Data Import/B.3.16.1000 - Access Restrictions.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.1200 - Data import overwrite.feature => Data Import/B.3.16.1200 - Overwrite Existing Data.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.1300 - Data import dag.feature => Data Import/B.3.16.1300 - Data Import - DAGs.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.200 - Data import create modify records.feature => Data Import/B.3.16.200 - Create & Modify Records.feature} (100%) rename Feature Tests/B/{Data import => Data Import}/B.3.16.300 - REDUNDANT.feature (100%) rename Feature Tests/B/{Data import/B.3.16.400 - Data import field validation.feature => Data Import/B.3.16.400 - Field Validation.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.500 - Data import codes.feature => Data Import/B.3.16.500 - Choices for Radios, Dropdowns, Checkboxes.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.600 - Data import survey id timestamp.feature => Data Import/B.3.16.600 - Survey Data Import.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.700 - Data import longitudinal.feature => Data Import/B.3.16.700 - Longitudinal Data Import.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.800 - Data import repeat.feature => Data Import/B.3.16.800 - Repeat Instrument Import.feature} (100%) rename Feature Tests/B/{Data import/B.3.16.900 - Data import locked.feature => Data Import/B.3.16.900 - Import Restrictions.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.100 - Create record.feature => B.3.14.100 - Create Record.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.1100 -Delete Record Data.feature => B.3.14.1100 - Delete Record Data.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.300 - Multiple choice-radio button.feature => B.3.14.300 - Radio button behavior.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.400 - Date time fields.feature => B.3.14.400 - Datetime Fields.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.700 - Form status option.feature => B.3.14.700 - Form status options.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.800 - Display record status dashboard.feature => B.3.14.800 - Record Status Dashboard.feature} (100%) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.900 - Rename record.feature => B.3.14.900 - Rename Record.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.100 - Enable Form into Survey.feature => B.3.15.100 - Enable Instrument as Survey.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.1000 - Survey participant list.feature => B.3.15.1000 - Survey Participant List.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.1100 - Survey track response.feature => B.3.15.1100 - Survey Response Tracking.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.1200 - Disabled survey removes survey metadata.feature => B.3.15.1200 - Disabled Survey Behavior.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.1300 - Public survey link.feature => B.3.15.1300 - Public Survey Link.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.200 - Survey status.feature => B.3.15.200 - Survey Status.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.300 - Survey distribution participant list.feature => B.3.15.300 - Survey Distribution Participant List.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.400 - Survey open from form.feature => B.3.15.400 - Open Survey from Form.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.500 - Survey mode alerts form mode.feature => B.3.15.500 - Survey Alerts and Prompts.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.800 - Survey edit.feature => B.3.15.800 - Edit Survey Responses.feature} (100%) rename Feature Tests/B/Direct Data Entry - Survey/{B.3.15.900 - Survey status.feature => B.3.15.900 - Survey Response Status.feature} (100%) rename Feature Tests/B/{Draft mode/B.4.20.100 - .feature => Draft Mode/B.4.20.100 - REDUNDANT.feature} (100%) rename Feature Tests/B/{Draft mode/B.4.20.300 - Change requires draft mode.feature => Draft Mode/B.4.20.300 - Instrument Behavior.feature} (100%) rename Feature Tests/B/{Draft mode/B.4.20.400 - Draft summary.feature => Draft Mode/B.4.20.400 - Draft Mode Summary.feature} (100%) rename Feature Tests/B/{Draft mode/B.4.20.500 - .feature => Draft Mode/B.4.20.500 - REDUNDANT.feature} (100%) rename Feature Tests/B/{Draft mode/B.4.20.600 - .feature => Draft Mode/B.4.20.600 - REDUNDANT.feature} (100%) rename Feature Tests/B/{Draft mode/B.4.20.700 - .feature => Draft Mode/B.4.20.700 - REDUNDANT.feature} (100%) rename Feature Tests/B/{Draft mode => Draft Mode}/B.4.20.800 - Draft warning.feature (100%) rename Feature Tests/B/{Draft mode => Draft Mode}/B.4.20.900 - Draft version control.feature (100%) rename Feature Tests/B/{Export data => Export Data}/B.5.21.100 - Export PHI.feature (100%) rename Feature Tests/B/{Export data/B.5.21.200 - Export format.feature => Export Data/B.5.21.200 - Export Data to External Format.feature} (100%) rename Feature Tests/B/{Export data/B.5.21.300 - Export fields.feature => Export Data/B.5.21.300 - Export All Fields.feature} (100%) rename Feature Tests/B/{Export data/B.5.21.400 - Export select forms.feature => Export Data/B.5.21.400 - Export Specific Forms.feature} (100%) rename Feature Tests/B/{Export data/B.5.21.500 - Export.feature => Export Data/B.5.21.500 - REDUNDANT.feature} (100%) rename Feature Tests/B/{Export data/B.5.21.600 - Export access.feature => Export Data/B.5.21.600 - User Access Restrictions.feature} (100%) rename Feature Tests/B/{Field validation/B.4.8.200 - Text validation.feature => Field Validation/B.4.8.200 - Text Validation.feature} (100%) rename Feature Tests/B/{Field validation => Field Validation}/B.4.8.300 - Field Ranges.feature (100%) rename Feature Tests/B/Longitudinal Project Setup/{B.4.27.100 - Longitudinal.feature => B.4.27.100 - REDUNDANT.feature} (100%) rename Feature Tests/B/Longitudinal Project Setup/{B.4.27.200 - Longitudinal.feature => B.4.27.200 - REDUNDANT.feature} (100%) rename Feature Tests/B/Longitudinal Project Setup/{B.4.27.300 - Longitudinal.feature => B.4.27.300 - Enable & Disable Longitudinal Data Collection.feature} (100%) rename Feature Tests/B/Longitudinal Project Setup/{B.4.27.400 - Longitudinal Events.feature => B.4.27.400 - Event Designation.feature} (100%) rename Feature Tests/B/Longitudinal Project Setup/{B.4.27.500 - Longitudinal Arms.feature => B.4.27.500 - Longitudinal Arms & Events.feature} (100%) rename Feature Tests/B/Longitudinal Project Setup/{B.4.27.600 - Longitudinal repeat.feature => B.4.27.600 - Repeating Events and Instruments.feature} (100%) rename Feature Tests/B/Longitudinal Project Setup/{B.4.27.700 - Longitudinal Admin Required.feature => B.4.27.700 - Longitudinal Administrative Controls.feature} (100%) rename Feature Tests/B/My Projects/{B.6.13.100 - My project dashboard.feature => B.6.13.100 - My Projects Dashboard.feature} (100%) rename Feature Tests/B/My Projects/{B.6.13.200 - My project dashboard archive hide.feature => B.6.13.200 - Archived Projects.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.100 - Forms - Data Dictionary and Online Designer.feature => B.6.7.100 - New Instruments via Data Dictionary.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.1200 - Field checkbox.feature => B.6.7.1200 - Field Checkbox.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.1300 - Field signature.feature => B.6.7.1300 - Field Signature.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.1400 - Field file upload.feature => B.6.7.1400 - Field File Upload.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.1500 - Field descriptive.feature => B.6.7.1500 - Field Descriptive Text.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.1600 - Field section.feature => B.6.7.1600 - Field New Section.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.1700 - Field identifier.feature => B.6.7.1700 - Identifier Fields.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.1800 - Field required.feature => B.6.7.1800 - Required Fields.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.1900 - Field management.feature => B.6.7.1900 - Field Management.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.200 - Forms - Create Instrument.feature => B.6.7.200 - Create Instrument.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.300 - Forms - Rename Instruments.feature => B.6.7.300 - Rename Instrument.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.400 - Forms - Copy Instruments.feature => B.6.7.400 - Copy Instrument.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.500 - Forms - Delete instruments.feature => B.6.7.500 - Delete Instrument.feature} (100%) rename Feature Tests/B/Online Designer/{B.6.7.600 - Forms - Reorder Instruments.feature => B.6.7.600 - Reorder Instrument.feature} (100%) rename Feature Tests/B/Project Setup/{B.6.4.1000 - Project copy.feature => B.6.4.1000 - Project Copy.feature} (100%) rename Feature Tests/B/Project Setup/{B.6.4.1100 - Erase data in dev.feature => B.6.4.1100 - Erase data in Development Mode.feature} (100%) rename Feature Tests/B/Project Setup/{B.6.4.1200 - Delete project.feature => B.6.4.1200 - Delete Project.feature} (100%) rename Feature Tests/B/Project Setup/{B.6.4.1300 - Project level survey.feature => B.6.4.1300 - Enable & Disable Survey.feature} (100%) rename Feature Tests/B/Project Setup/{B.6.4.1400 - Repeat survey.feature => B.6.4.1400 - Repeating Surveys.feature} (100%) rename Feature Tests/B/Project Setup/{B.6.4.800 - Project setup title.feature => B.6.4.800 - Project Title.feature} (100%) rename Feature Tests/B/Project Setup/{B.6.4.900 - Project setup purpose.feature => B.6.4.900 - Project Purpose.feature} (100%) rename Feature Tests/B/{Project status => Project Status}/B.6.11.200 - Move project status.feature (100%) rename Feature Tests/B/{Project status => Project Status}/B.6.11.300 - Data management during project status change.feature (100%) rename Feature Tests/C/Data Quality/{C.4.18.1100 - Data Quality.feature => C.4.18.1100 - REDUNDANT.feature} (100%) rename Feature Tests/C/Data Quality/{C.4.18.1200 - Data Quality.feature => C.4.18.1200 - REDUNDANT.feature} (100%) rename Feature Tests/C/Data Quality/{C.4.18.400 - Data Quality.feature => C.4.18.400 - REDUNDANT.feature} (100%) rename Feature Tests/C/Data Quality/{C.4.18.800 - Data Quality.feature => C.4.18.800 - REDUNDANT.feature} (100%) rename Feature Tests/C/Data Quality/{C.4.18.900 - Data Quality.feature => C.4.18.900 - REDUNDANT.feature} (100%) rename Feature Tests/C/Record Locking & E-Signatures/{C.2.19.500 - esign display.feature => C.2.19.500 - eSign display.feature} (100%) rename Feature Tests/C/Record Locking & E-Signatures/{C.2.19.700 - esign customization.feature => C.2.19.700 - eSign customization.feature} (100%) rename Feature Tests/C/Record Locking & E-Signatures/{C.2.19.800 - Esign and Lock.feature => C.2.19.800 - REDUNDANT.feature} (100%) rename Feature Tests/C/Record Locking & E-Signatures/{C.2.19.900 - Esign and Lock access.feature => C.2.19.900 - eSign and Lock access.feature} (100%) rename Feature Tests/C/e-Consent framework/{C.3.24.400 - eConsent.feature => C.3.24.400 - REDUNDANT.feature} (100%) rename Feature Tests/C/e-Consent framework/{C.3.24.500 - eConsent.feature => C.3.24.500 - REDUNDANT.feature} (100%) diff --git a/Feature Tests/A/Assign administrators/A.2.3.400 - Assign Administrators and Account Managers.feature b/Feature Tests/A/Assign Administrators/A.2.3.400 - Assign Administrators and Account Managers.feature similarity index 100% rename from Feature Tests/A/Assign administrators/A.2.3.400 - Assign Administrators and Account Managers.feature rename to Feature Tests/A/Assign Administrators/A.2.3.400 - Assign Administrators and Account Managers.feature diff --git a/Feature Tests/A/Browse projects/ A.1.5.100 - Browse Projects.feature b/Feature Tests/A/Browse Projects/ A.1.5.100 - Browse Projects.feature similarity index 100% rename from Feature Tests/A/Browse projects/ A.1.5.100 - Browse Projects.feature rename to Feature Tests/A/Browse Projects/ A.1.5.100 - Browse Projects.feature diff --git a/Feature Tests/A/Field validation/A.4.8.100 - Enable field validation.feature b/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature similarity index 100% rename from Feature Tests/A/Field validation/A.4.8.100 - Enable field validation.feature rename to Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature diff --git a/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature b/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature similarity index 100% rename from Feature Tests/A/File Repository/A.3.26.100 - public file share.feature rename to Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature diff --git a/Feature Tests/A/Security settings/A.2.12.100 - System Status.feature b/Feature Tests/A/Security Settings/A.2.12.100 - System Status.feature similarity index 100% rename from Feature Tests/A/Security settings/A.2.12.100 - System Status.feature rename to Feature Tests/A/Security Settings/A.2.12.100 - System Status.feature diff --git a/Feature Tests/B/Branching logic/B.4.9.100 - branching logic.feature b/Feature Tests/B/Branching Logic/B.4.9.100 - Branching Logic.feature similarity index 100% rename from Feature Tests/B/Branching logic/B.4.9.100 - branching logic.feature rename to Feature Tests/B/Branching Logic/B.4.9.100 - Branching Logic.feature diff --git a/Feature Tests/B/Data import/B.3.16.100 - Data import template.feature b/Feature Tests/B/Data Import/B.3.16.100 - Import Templates - Columns & Rows.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.100 - Data import template.feature rename to Feature Tests/B/Data Import/B.3.16.100 - Import Templates - Columns & Rows.feature diff --git a/Feature Tests/B/Data import/B.3.16.1000 - Data import access.feature b/Feature Tests/B/Data Import/B.3.16.1000 - Access Restrictions.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.1000 - Data import access.feature rename to Feature Tests/B/Data Import/B.3.16.1000 - Access Restrictions.feature diff --git a/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature b/Feature Tests/B/Data Import/B.3.16.1200 - Overwrite Existing Data.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature rename to Feature Tests/B/Data Import/B.3.16.1200 - Overwrite Existing Data.feature diff --git a/Feature Tests/B/Data import/B.3.16.1300 - Data import dag.feature b/Feature Tests/B/Data Import/B.3.16.1300 - Data Import - DAGs.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.1300 - Data import dag.feature rename to Feature Tests/B/Data Import/B.3.16.1300 - Data Import - DAGs.feature diff --git a/Feature Tests/B/Data import/B.3.16.200 - Data import create modify records.feature b/Feature Tests/B/Data Import/B.3.16.200 - Create & Modify Records.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.200 - Data import create modify records.feature rename to Feature Tests/B/Data Import/B.3.16.200 - Create & Modify Records.feature diff --git a/Feature Tests/B/Data import/B.3.16.300 - REDUNDANT.feature b/Feature Tests/B/Data Import/B.3.16.300 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.300 - REDUNDANT.feature rename to Feature Tests/B/Data Import/B.3.16.300 - REDUNDANT.feature diff --git a/Feature Tests/B/Data import/B.3.16.400 - Data import field validation.feature b/Feature Tests/B/Data Import/B.3.16.400 - Field Validation.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.400 - Data import field validation.feature rename to Feature Tests/B/Data Import/B.3.16.400 - Field Validation.feature diff --git a/Feature Tests/B/Data import/B.3.16.500 - Data import codes.feature b/Feature Tests/B/Data Import/B.3.16.500 - Choices for Radios, Dropdowns, Checkboxes.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.500 - Data import codes.feature rename to Feature Tests/B/Data Import/B.3.16.500 - Choices for Radios, Dropdowns, Checkboxes.feature diff --git a/Feature Tests/B/Data import/B.3.16.600 - Data import survey id timestamp.feature b/Feature Tests/B/Data Import/B.3.16.600 - Survey Data Import.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.600 - Data import survey id timestamp.feature rename to Feature Tests/B/Data Import/B.3.16.600 - Survey Data Import.feature diff --git a/Feature Tests/B/Data import/B.3.16.700 - Data import longitudinal.feature b/Feature Tests/B/Data Import/B.3.16.700 - Longitudinal Data Import.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.700 - Data import longitudinal.feature rename to Feature Tests/B/Data Import/B.3.16.700 - Longitudinal Data Import.feature diff --git a/Feature Tests/B/Data import/B.3.16.800 - Data import repeat.feature b/Feature Tests/B/Data Import/B.3.16.800 - Repeat Instrument Import.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.800 - Data import repeat.feature rename to Feature Tests/B/Data Import/B.3.16.800 - Repeat Instrument Import.feature diff --git a/Feature Tests/B/Data import/B.3.16.900 - Data import locked.feature b/Feature Tests/B/Data Import/B.3.16.900 - Import Restrictions.feature similarity index 100% rename from Feature Tests/B/Data import/B.3.16.900 - Data import locked.feature rename to Feature Tests/B/Data Import/B.3.16.900 - Import Restrictions.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create Record.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create record.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create Record.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 - Delete Record Data.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 -Delete Record Data.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 - Delete Record Data.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Radio button behavior.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Multiple choice-radio button.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.300 - Radio button behavior.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Date time fields.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Datetime Fields.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Date time fields.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Datetime Fields.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status option.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status options.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status option.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.700 - Form status options.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.800 - Display record status dashboard.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.800 - Record Status Dashboard.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.800 - Display record status dashboard.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.800 - Record Status Dashboard.feature diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename Record.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename record.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.900 - Rename Record.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Instrument as Survey.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Form into Survey.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.100 - Enable Instrument as Survey.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey participant list.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey Participant List.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey participant list.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.1000 - Survey Participant List.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey track response.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey Response Tracking.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey track response.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey Response Tracking.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled survey removes survey metadata.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled Survey Behavior.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled survey removes survey metadata.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.1200 - Disabled Survey Behavior.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public survey link.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public Survey Link.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public survey link.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.1300 - Public Survey Link.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey Status.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey status.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.200 - Survey Status.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey distribution participant list.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey Distribution Participant List.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey distribution participant list.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.300 - Survey Distribution Participant List.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Survey open from form.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Open Survey from Form.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Survey open from form.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.400 - Open Survey from Form.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey mode alerts form mode.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey Alerts and Prompts.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey mode alerts form mode.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.500 - Survey Alerts and Prompts.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Survey edit.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Edit Survey Responses.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Survey edit.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.800 - Edit Survey Responses.feature diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey status.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey Response Status.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey status.feature rename to Feature Tests/B/Direct Data Entry - Survey/B.3.15.900 - Survey Response Status.feature diff --git a/Feature Tests/B/Draft mode/B.4.20.100 - .feature b/Feature Tests/B/Draft Mode/B.4.20.100 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Draft mode/B.4.20.100 - .feature rename to Feature Tests/B/Draft Mode/B.4.20.100 - REDUNDANT.feature diff --git a/Feature Tests/B/Draft mode/B.4.20.300 - Change requires draft mode.feature b/Feature Tests/B/Draft Mode/B.4.20.300 - Instrument Behavior.feature similarity index 100% rename from Feature Tests/B/Draft mode/B.4.20.300 - Change requires draft mode.feature rename to Feature Tests/B/Draft Mode/B.4.20.300 - Instrument Behavior.feature diff --git a/Feature Tests/B/Draft mode/B.4.20.400 - Draft summary.feature b/Feature Tests/B/Draft Mode/B.4.20.400 - Draft Mode Summary.feature similarity index 100% rename from Feature Tests/B/Draft mode/B.4.20.400 - Draft summary.feature rename to Feature Tests/B/Draft Mode/B.4.20.400 - Draft Mode Summary.feature diff --git a/Feature Tests/B/Draft mode/B.4.20.500 - .feature b/Feature Tests/B/Draft Mode/B.4.20.500 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Draft mode/B.4.20.500 - .feature rename to Feature Tests/B/Draft Mode/B.4.20.500 - REDUNDANT.feature diff --git a/Feature Tests/B/Draft mode/B.4.20.600 - .feature b/Feature Tests/B/Draft Mode/B.4.20.600 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Draft mode/B.4.20.600 - .feature rename to Feature Tests/B/Draft Mode/B.4.20.600 - REDUNDANT.feature diff --git a/Feature Tests/B/Draft mode/B.4.20.700 - .feature b/Feature Tests/B/Draft Mode/B.4.20.700 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Draft mode/B.4.20.700 - .feature rename to Feature Tests/B/Draft Mode/B.4.20.700 - REDUNDANT.feature diff --git a/Feature Tests/B/Draft mode/B.4.20.800 - Draft warning.feature b/Feature Tests/B/Draft Mode/B.4.20.800 - Draft warning.feature similarity index 100% rename from Feature Tests/B/Draft mode/B.4.20.800 - Draft warning.feature rename to Feature Tests/B/Draft Mode/B.4.20.800 - Draft warning.feature diff --git a/Feature Tests/B/Draft mode/B.4.20.900 - Draft version control.feature b/Feature Tests/B/Draft Mode/B.4.20.900 - Draft version control.feature similarity index 100% rename from Feature Tests/B/Draft mode/B.4.20.900 - Draft version control.feature rename to Feature Tests/B/Draft Mode/B.4.20.900 - Draft version control.feature diff --git a/Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature b/Feature Tests/B/Export Data/B.5.21.100 - Export PHI.feature similarity index 100% rename from Feature Tests/B/Export data/B.5.21.100 - Export PHI.feature rename to Feature Tests/B/Export Data/B.5.21.100 - Export PHI.feature diff --git a/Feature Tests/B/Export data/B.5.21.200 - Export format.feature b/Feature Tests/B/Export Data/B.5.21.200 - Export Data to External Format.feature similarity index 100% rename from Feature Tests/B/Export data/B.5.21.200 - Export format.feature rename to Feature Tests/B/Export Data/B.5.21.200 - Export Data to External Format.feature diff --git a/Feature Tests/B/Export data/B.5.21.300 - Export fields.feature b/Feature Tests/B/Export Data/B.5.21.300 - Export All Fields.feature similarity index 100% rename from Feature Tests/B/Export data/B.5.21.300 - Export fields.feature rename to Feature Tests/B/Export Data/B.5.21.300 - Export All Fields.feature diff --git a/Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature b/Feature Tests/B/Export Data/B.5.21.400 - Export Specific Forms.feature similarity index 100% rename from Feature Tests/B/Export data/B.5.21.400 - Export select forms.feature rename to Feature Tests/B/Export Data/B.5.21.400 - Export Specific Forms.feature diff --git a/Feature Tests/B/Export data/B.5.21.500 - Export.feature b/Feature Tests/B/Export Data/B.5.21.500 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Export data/B.5.21.500 - Export.feature rename to Feature Tests/B/Export Data/B.5.21.500 - REDUNDANT.feature diff --git a/Feature Tests/B/Export data/B.5.21.600 - Export access.feature b/Feature Tests/B/Export Data/B.5.21.600 - User Access Restrictions.feature similarity index 100% rename from Feature Tests/B/Export data/B.5.21.600 - Export access.feature rename to Feature Tests/B/Export Data/B.5.21.600 - User Access Restrictions.feature diff --git a/Feature Tests/B/Field validation/B.4.8.200 - Text validation.feature b/Feature Tests/B/Field Validation/B.4.8.200 - Text Validation.feature similarity index 100% rename from Feature Tests/B/Field validation/B.4.8.200 - Text validation.feature rename to Feature Tests/B/Field Validation/B.4.8.200 - Text Validation.feature diff --git a/Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature b/Feature Tests/B/Field Validation/B.4.8.300 - Field Ranges.feature similarity index 100% rename from Feature Tests/B/Field validation/B.4.8.300 - Field Ranges.feature rename to Feature Tests/B/Field Validation/B.4.8.300 - Field Ranges.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.100 - Longitudinal.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.100 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Longitudinal Project Setup/B.4.27.100 - Longitudinal.feature rename to Feature Tests/B/Longitudinal Project Setup/B.4.27.100 - REDUNDANT.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.200 - Longitudinal.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.200 - REDUNDANT.feature similarity index 100% rename from Feature Tests/B/Longitudinal Project Setup/B.4.27.200 - Longitudinal.feature rename to Feature Tests/B/Longitudinal Project Setup/B.4.27.200 - REDUNDANT.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Enable & Disable Longitudinal Data Collection.feature similarity index 100% rename from Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Longitudinal.feature rename to Feature Tests/B/Longitudinal Project Setup/B.4.27.300 - Enable & Disable Longitudinal Data Collection.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Event Designation.feature similarity index 100% rename from Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Longitudinal Events.feature rename to Feature Tests/B/Longitudinal Project Setup/B.4.27.400 - Event Designation.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - Longitudinal Arms.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - Longitudinal Arms & Events.feature similarity index 100% rename from Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - Longitudinal Arms.feature rename to Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - Longitudinal Arms & Events.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - Longitudinal repeat.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - Repeating Events and Instruments.feature similarity index 100% rename from Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - Longitudinal repeat.feature rename to Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - Repeating Events and Instruments.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Administrative Controls.feature similarity index 100% rename from Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Admin Required.feature rename to Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Administrative Controls.feature diff --git a/Feature Tests/B/My Projects/B.6.13.100 - My project dashboard.feature b/Feature Tests/B/My Projects/B.6.13.100 - My Projects Dashboard.feature similarity index 100% rename from Feature Tests/B/My Projects/B.6.13.100 - My project dashboard.feature rename to Feature Tests/B/My Projects/B.6.13.100 - My Projects Dashboard.feature diff --git a/Feature Tests/B/My Projects/B.6.13.200 - My project dashboard archive hide.feature b/Feature Tests/B/My Projects/B.6.13.200 - Archived Projects.feature similarity index 100% rename from Feature Tests/B/My Projects/B.6.13.200 - My project dashboard archive hide.feature rename to Feature Tests/B/My Projects/B.6.13.200 - Archived Projects.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.100 - Forms - Data Dictionary and Online Designer.feature b/Feature Tests/B/Online Designer/B.6.7.100 - New Instruments via Data Dictionary.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.100 - Forms - Data Dictionary and Online Designer.feature rename to Feature Tests/B/Online Designer/B.6.7.100 - New Instruments via Data Dictionary.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.1200 - Field checkbox.feature b/Feature Tests/B/Online Designer/B.6.7.1200 - Field Checkbox.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1200 - Field checkbox.feature rename to Feature Tests/B/Online Designer/B.6.7.1200 - Field Checkbox.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.1300 - Field signature.feature b/Feature Tests/B/Online Designer/B.6.7.1300 - Field Signature.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1300 - Field signature.feature rename to Feature Tests/B/Online Designer/B.6.7.1300 - Field Signature.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.1400 - Field file upload.feature b/Feature Tests/B/Online Designer/B.6.7.1400 - Field File Upload.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1400 - Field file upload.feature rename to Feature Tests/B/Online Designer/B.6.7.1400 - Field File Upload.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.1500 - Field descriptive.feature b/Feature Tests/B/Online Designer/B.6.7.1500 - Field Descriptive Text.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1500 - Field descriptive.feature rename to Feature Tests/B/Online Designer/B.6.7.1500 - Field Descriptive Text.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.1600 - Field section.feature b/Feature Tests/B/Online Designer/B.6.7.1600 - Field New Section.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1600 - Field section.feature rename to Feature Tests/B/Online Designer/B.6.7.1600 - Field New Section.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.1700 - Field identifier.feature b/Feature Tests/B/Online Designer/B.6.7.1700 - Identifier Fields.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1700 - Field identifier.feature rename to Feature Tests/B/Online Designer/B.6.7.1700 - Identifier Fields.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature b/Feature Tests/B/Online Designer/B.6.7.1800 - Required Fields.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1800 - Field required.feature rename to Feature Tests/B/Online Designer/B.6.7.1800 - Required Fields.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.1900 - Field management.feature b/Feature Tests/B/Online Designer/B.6.7.1900 - Field Management.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1900 - Field management.feature rename to Feature Tests/B/Online Designer/B.6.7.1900 - Field Management.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.200 - Forms - Create Instrument.feature b/Feature Tests/B/Online Designer/B.6.7.200 - Create Instrument.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.200 - Forms - Create Instrument.feature rename to Feature Tests/B/Online Designer/B.6.7.200 - Create Instrument.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.300 - Forms - Rename Instruments.feature b/Feature Tests/B/Online Designer/B.6.7.300 - Rename Instrument.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.300 - Forms - Rename Instruments.feature rename to Feature Tests/B/Online Designer/B.6.7.300 - Rename Instrument.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature b/Feature Tests/B/Online Designer/B.6.7.400 - Copy Instrument.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.400 - Forms - Copy Instruments.feature rename to Feature Tests/B/Online Designer/B.6.7.400 - Copy Instrument.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.500 - Forms - Delete instruments.feature b/Feature Tests/B/Online Designer/B.6.7.500 - Delete Instrument.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.500 - Forms - Delete instruments.feature rename to Feature Tests/B/Online Designer/B.6.7.500 - Delete Instrument.feature diff --git a/Feature Tests/B/Online Designer/B.6.7.600 - Forms - Reorder Instruments.feature b/Feature Tests/B/Online Designer/B.6.7.600 - Reorder Instrument.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.600 - Forms - Reorder Instruments.feature rename to Feature Tests/B/Online Designer/B.6.7.600 - Reorder Instrument.feature diff --git a/Feature Tests/B/Project Setup/B.6.4.1000 - Project copy.feature b/Feature Tests/B/Project Setup/B.6.4.1000 - Project Copy.feature similarity index 100% rename from Feature Tests/B/Project Setup/B.6.4.1000 - Project copy.feature rename to Feature Tests/B/Project Setup/B.6.4.1000 - Project Copy.feature diff --git a/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature b/Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in Development Mode.feature similarity index 100% rename from Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in dev.feature rename to Feature Tests/B/Project Setup/B.6.4.1100 - Erase data in Development Mode.feature diff --git a/Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature b/Feature Tests/B/Project Setup/B.6.4.1200 - Delete Project.feature similarity index 100% rename from Feature Tests/B/Project Setup/B.6.4.1200 - Delete project.feature rename to Feature Tests/B/Project Setup/B.6.4.1200 - Delete Project.feature diff --git a/Feature Tests/B/Project Setup/B.6.4.1300 - Project level survey.feature b/Feature Tests/B/Project Setup/B.6.4.1300 - Enable & Disable Survey.feature similarity index 100% rename from Feature Tests/B/Project Setup/B.6.4.1300 - Project level survey.feature rename to Feature Tests/B/Project Setup/B.6.4.1300 - Enable & Disable Survey.feature diff --git a/Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature b/Feature Tests/B/Project Setup/B.6.4.1400 - Repeating Surveys.feature similarity index 100% rename from Feature Tests/B/Project Setup/B.6.4.1400 - Repeat survey.feature rename to Feature Tests/B/Project Setup/B.6.4.1400 - Repeating Surveys.feature diff --git a/Feature Tests/B/Project Setup/B.6.4.800 - Project setup title.feature b/Feature Tests/B/Project Setup/B.6.4.800 - Project Title.feature similarity index 100% rename from Feature Tests/B/Project Setup/B.6.4.800 - Project setup title.feature rename to Feature Tests/B/Project Setup/B.6.4.800 - Project Title.feature diff --git a/Feature Tests/B/Project Setup/B.6.4.900 - Project setup purpose.feature b/Feature Tests/B/Project Setup/B.6.4.900 - Project Purpose.feature similarity index 100% rename from Feature Tests/B/Project Setup/B.6.4.900 - Project setup purpose.feature rename to Feature Tests/B/Project Setup/B.6.4.900 - Project Purpose.feature diff --git a/Feature Tests/B/Project status/B.6.11.200 - Move project status.feature b/Feature Tests/B/Project Status/B.6.11.200 - Move project status.feature similarity index 100% rename from Feature Tests/B/Project status/B.6.11.200 - Move project status.feature rename to Feature Tests/B/Project Status/B.6.11.200 - Move project status.feature diff --git a/Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature b/Feature Tests/B/Project Status/B.6.11.300 - Data management during project status change.feature similarity index 100% rename from Feature Tests/B/Project status/B.6.11.300 - Data management during project status change.feature rename to Feature Tests/B/Project Status/B.6.11.300 - Data management during project status change.feature diff --git a/Feature Tests/C/Data Quality/C.4.18.1100 - Data Quality.feature b/Feature Tests/C/Data Quality/C.4.18.1100 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/Data Quality/C.4.18.1100 - Data Quality.feature rename to Feature Tests/C/Data Quality/C.4.18.1100 - REDUNDANT.feature diff --git a/Feature Tests/C/Data Quality/C.4.18.1200 - Data Quality.feature b/Feature Tests/C/Data Quality/C.4.18.1200 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/Data Quality/C.4.18.1200 - Data Quality.feature rename to Feature Tests/C/Data Quality/C.4.18.1200 - REDUNDANT.feature diff --git a/Feature Tests/C/Data Quality/C.4.18.400 - Data Quality.feature b/Feature Tests/C/Data Quality/C.4.18.400 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/Data Quality/C.4.18.400 - Data Quality.feature rename to Feature Tests/C/Data Quality/C.4.18.400 - REDUNDANT.feature diff --git a/Feature Tests/C/Data Quality/C.4.18.800 - Data Quality.feature b/Feature Tests/C/Data Quality/C.4.18.800 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/Data Quality/C.4.18.800 - Data Quality.feature rename to Feature Tests/C/Data Quality/C.4.18.800 - REDUNDANT.feature diff --git a/Feature Tests/C/Data Quality/C.4.18.900 - Data Quality.feature b/Feature Tests/C/Data Quality/C.4.18.900 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/Data Quality/C.4.18.900 - Data Quality.feature rename to Feature Tests/C/Data Quality/C.4.18.900 - REDUNDANT.feature diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - eSign display.feature similarity index 100% rename from Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - esign display.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.500 - eSign display.feature diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - eSign customization.feature similarity index 100% rename from Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - esign customization.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.700 - eSign customization.feature diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.800 - Esign and Lock.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.800 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/Record Locking & E-Signatures/C.2.19.800 - Esign and Lock.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.800 - REDUNDANT.feature diff --git a/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature b/Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - eSign and Lock access.feature similarity index 100% rename from Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - Esign and Lock access.feature rename to Feature Tests/C/Record Locking & E-Signatures/C.2.19.900 - eSign and Lock access.feature diff --git a/Feature Tests/C/e-Consent framework/C.3.24.400 - eConsent.feature b/Feature Tests/C/e-Consent framework/C.3.24.400 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/e-Consent framework/C.3.24.400 - eConsent.feature rename to Feature Tests/C/e-Consent framework/C.3.24.400 - REDUNDANT.feature diff --git a/Feature Tests/C/e-Consent framework/C.3.24.500 - eConsent.feature b/Feature Tests/C/e-Consent framework/C.3.24.500 - REDUNDANT.feature similarity index 100% rename from Feature Tests/C/e-Consent framework/C.3.24.500 - eConsent.feature rename to Feature Tests/C/e-Consent framework/C.3.24.500 - REDUNDANT.feature From 73ccebd40e484706455e9fd4ad2ef284bb0b975b Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 16:45:23 -0500 Subject: [PATCH 16/96] Rename B.3.14.500 - Leave without save.feature to B.3.14.500 - Leave without Save.feature --- ...thout save.feature => B.3.14.500 - Leave without Save.feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.500 - Leave without save.feature => B.3.14.500 - Leave without Save.feature} (100%) diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without save.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without Save.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without save.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.500 - Leave without Save.feature From 17f6bd1f38b2544ef5969b172f3c41301f249d72 Mon Sep 17 00:00:00 2001 From: Adam De Fouw Date: Thu, 5 Oct 2023 16:45:50 -0500 Subject: [PATCH 17/96] More naming adjustments --- ...0 - Save options.feature => B.3.14.600 - Save Options.feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/B/Direct Data Entry - Data Collection Instrument/{B.3.14.600 - Save options.feature => B.3.14.600 - Save Options.feature} (100%) diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save options.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save Options.feature similarity index 100% rename from Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save options.feature rename to Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save Options.feature From 23ec6c3a045c8b9788b1fbd91a286c44aff696f0 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 6 Oct 2023 12:42:57 -0400 Subject: [PATCH 18/96] Update A.3.26.100 - public file share.feature added spaces --- .../A/File Repository/A.3.26.100 - public file share.feature | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature b/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature index 4355d599..c6f2d864 100644 --- a/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature +++ b/Feature Tests/A/File Repository/A.3.26.100 - public file share.feature @@ -59,3 +59,6 @@ And I click on the file share icon for "testusers_bulk_upload.csv" Then I should see Send the file securely using Send-It" Then I should see "Share a public link to view the file" And I click on the button labeled "Close" in the dialog box + + + From bc5f15d994de6bbfefb851f4a75c433f67b11638 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Tue, 10 Oct 2023 16:18:21 -0400 Subject: [PATCH 19/96] Update A.3.26.100 - Public File Share.feature fix file --- .../A/File Repository/A.3.26.100 - Public File Share.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature b/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature index 61d0185e..194ebed9 100644 --- a/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature +++ b/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature @@ -6,7 +6,7 @@ As a REDCap end user Scenario: C.3.26.100.100 Enable/Disable file repository public links via Control Center #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "A.3.26.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_3.16.xml", and clicking the "Create Project" button +And I create a new project named "A.3.26.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button And I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.100.100" And I click the link labeled "Designer" From 23d783daceacb30ad0d0e1b57cbb95e0c82686c5 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Tue, 10 Oct 2023 16:25:44 -0400 Subject: [PATCH 20/96] Update A.3.26.100 - Public File Share.feature fix syntax --- .../A.3.26.100 - Public File Share.feature | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature b/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature index 194ebed9..ae91d8ba 100644 --- a/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature +++ b/Feature Tests/A/File Repository/A.3.26.100 - Public File Share.feature @@ -11,7 +11,8 @@ And I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.100.100" And I click the link labeled "Designer" And I click the button labeled "Survey Settings" for the instrument "Consent" -And I click on the button labeled "Auto-Archiver enabled + e-Consent Framework" Then I click the button labeled "Save Changes" +And I click on the button labeled "Auto-Archiver enabled + e-Consent Framework" +Then I click the button labeled "Save Changes" ##SETUP_PRODUCTION When I click on the link labeled "Project Setup" @@ -22,7 +23,8 @@ Then I see "Project status: Production" ##ACTION Upload to top tier file repo (all users will see file) - using the Select files to upload button When I click on the link labeled "File Repository" -When I upload a "csv" format file located at "import_files/testusers_bulk_upload.csv", by clicking the button near "Select files to upload" to browse for the file, and clicking the button labeled "Open" to upload the file ##VERIFY_FiRe file uploaded in folder +When I upload a "csv" format file located at "import_files/testusers_bulk_upload.csv", by clicking the button near "Select files to upload" to browse for the file, and clicking the button labeled "Open" to upload the file +##VERIFY_FiRe file uploaded in folder Then I should see "testusers_bulk_upload.csv" #FUNCTIONAL_REQUIREMENT @@ -41,7 +43,7 @@ When I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.100.100" When I click on the link labeled "File Repository." And I click on the file share icon for "testusers_bulk_upload.csv" -Then I should see Send the file securely using Send-It" +Then I should see "Send the file securely using Send-It" And I should NOT see "Share a public link to view the file" #FUNCTIONAL_REQUIREMENT @@ -55,8 +57,8 @@ Then I should see "Your system configuration values have now been changed!" ##VERIFY Project settings shareability in File Repository When I click on the link labeled "My Projects" And I click on the link labeled "A.3.26.100.100" - And I click on the link labeled "File Repository." +And I click on the link labeled "File Repository." And I click on the file share icon for "testusers_bulk_upload.csv" Then I should see Send the file securely using Send-It" -Then I should see "Share a public link to view the file" +And I should see "Share a public link to view the file" And I click on the button labeled "Close" in the dialog box From 12be58b45d3fb304974663b910d3f179bd87ea44 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 16:13:26 -0400 Subject: [PATCH 21/96] Update A.2.2.400 - Delete.feature added conditional user creation section --- .../A.2.2.400 - Delete.feature | 57 +++++++++++-------- 1 file changed, 34 insertions(+), 23 deletions(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature index 358ec76d..03501789 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature @@ -4,52 +4,63 @@ Feature: A.2.2.400 Add/Manage users I want to see that Delete Users is functioning as expected. Scenario: A.2.2.400.100 Delete User Function - - Given I login to REDCap with the user "Test_Admin" + + #SETUP_USER +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" - And I click on the link labeled "Add Users (Table-based Only)" - Then I should see "Create single user" + And I click on the link labeled "Browse Users" + And I click on the link labeled "Browse Users" +Then I should see "User Search: Search for user by username, first name, last name, or primary email" + +##ACTION_MANUAL_TESTING: Verify Delete_User is already created. If Delete_User is not created, skip to line 22. +#When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" +# And I click on the button labeled "Search" +#Then I should see "Delete_User" -#SETUP_USER - When I enter "Delete_User" into the input field labeled "Username:" +#Manual skip to Functional Requirement test (Line 40) +##ACTION_AUTOMATED_TESTING: Create Delete_User +When I click on the link labeled "Add Users (Table-based Only)" +Then I should see "Create single user" + +When I enter "Delete_User" into the input field labeled "Username:" And I enter "User_firstname" into the input field labeled "First name:" And I enter "User_lastname" into the input field labeled "Last name:" And I enter "Delete_User@test.edu" into the input field labeled "Primary email:" And I click on the button labeled "Save" - Then I should see "User has been successfully saved." +Then I should see "User has been successfully saved." - When I click on the link labeled "Browse Users" - Then I should see "User Search: Search for user by username, first name, last name, or primary email" +When I click on the link labeled "Browse Users" +Then I should see "User Search: Search for user by username, first name, last name, or primary email" - When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" +When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" And I click on the button labeled "Search" - Then I should see "Editable user attributes" +Then I should see "Editable user attributes" And I should see "Delete_User" #FUNCTIONAL REQUIREMENT ##ACTION Cancel delete user - When I click on the button labeled "Delete user from system" and cancel the confirmation window - Then I should NOT see "The user 'Delete_User' has now been removed and deleted from all REDCap projects" +When I click on the button labeled "Delete user from system" and cancel the confirmation window +Then I should NOT see "The user 'Delete_User' has now been removed and deleted from all REDCap projects" - When I click on the link labeled "Browse Users" - Then I should see "User Search: Search for user by username, first name, last name, or primary email" +When I click on the link labeled "Browse Users" +Then I should see "User Search: Search for user by username, first name, last name, or primary email" #VERIFY User exist - When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" +When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" And I click on the button labeled "Search" - Then I should see "Editable user attributes" +Then I should see "Editable user attributes" And I should see "Delete_User" #FUNCTIONAL REQUIREMENT ##ACTION Delete user - When I click on the button labeled "Delete user from system" and accept the confirmation window - Then I should see "The user 'Delete_User' has now been removed and deleted from all REDCap projects" +When I click on the button labeled "Delete user from system" and accept the confirmation window +Then I should see "The user 'Delete_User' has now been removed and deleted from all REDCap projects" And I click on the button labeled "Close" #VERIFY User does not exist - When I click on the link labeled "Browse Users" - Then I should see "User Search: Search for user by username, first name, last name, or primary email" +When I click on the link labeled "Browse Users" +Then I should see "User Search: Search for user by username, first name, last name, or primary email" - When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" +When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" And I click on the button labeled "Search" - Then I should see "User does not exist!" +Then I should see "User does not exist!" From 0c9a05fd3c96f30d28d36d49b4618b5694b95fd6 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 16:38:27 -0400 Subject: [PATCH 22/96] Update A.2.2.600 - Account Lockout.feature Add comments --- .../A.2.2.600 - Account Lockout.feature | 71 +++++++++++-------- 1 file changed, 42 insertions(+), 29 deletions(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature b/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature index 362d531c..5f3f9de8 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature @@ -4,66 +4,79 @@ Feature: A.2.2.600 Add/Manage users I want to see that Users failed login lockout is functioning as expected. Scenario: A.2.2.600.100 User account locked out after too many attempts - Given I login to REDCap with the user "Test_Admin" +#SETUP +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Security & Authentication" - Then I should see "Security & Authentication Configuration" +Then I should see "Security & Authentication Configuration" - When I clear the field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." +#FUNCTIONAL REQUIREMENT +##ACTION Setup the failed login attempts +When I clear the field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." And I enter "1" into the input field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." And I clear the field labeled "Amount of time user will be locked out after having failed login attempts exceeding the limit set above." And I enter "2" into the input field labeled "Amount of time user will be locked out after having failed login attempts exceeding the limit set above." And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout +Then I should see "Your system configuration values have now been changed!" +Given I logout - Given I enter "Test_User1" into the input field labeled "Username:" +##ACTION incorrect attempt +Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" - Then I should see "ERROR: You entered an invalid user name or password!" +Then I should see "ERROR: You entered an invalid user name or password!" - Given I enter "Test_User1" into the input field labeled "Username:" +##ACTION incorrect attempt +Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" - Then I should see "ACCESS DENIED!" +##VERIFY Timeout / lockout +Then I should see "ACCESS DENIED!" - Given I wait for 2 minutes +Given I wait for 2 minutes - Given I login to REDCap with the user "Test_User1" - And I see "My Projects" - Given I logout +##VERIFY Login after timeout/lockout +Given I login to REDCap with the user "Test_User1" +Then I see "My Projects" +Given I logout - Given I login to REDCap with the user "Test_Admin" +#SETUP +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Security & Authentication" - Then I should see "Security & Authentication Configuration" +Then I should see "Security & Authentication Configuration" - When I clear the field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." +##ACTION Change failed login attempts settings +When I clear the field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." And I enter "2" into the input field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." And I clear the field labeled "Amount of time user will be locked out after having failed login attempts exceeding the limit set above." And I enter "1" into the input field labeled "Amount of time user will be locked out after having failed login attempts exceeding the limit set above." And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout +Then I should see "Your system configuration values have now been changed!" +Given I logout - Given I enter "Test_User1" into the input field labeled "Username:" +##ACTION incorrect attempt +Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" - Then I should see "ERROR" +Then I should see "ERROR" - Given I enter "Test_User1" into the input field labeled "Username:" +##ACTION incorrect attempt +Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" - Then I should see "ERROR" +Then I should see "ERROR" - Given I enter "Test_User1" into the input field labeled "Username:" +##ACTION incorrect attempt +Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" - Then I should see "ACCESS DENIED!" +##VERIFY Timeout / lockout +Then I should see "ACCESS DENIED!" - Given I wait for 1 minute +Given I wait for 1 minute - Given I login to REDCap with the user "Test_User1" - And I see "My Projects" - Given I logout - +##VERIFY Login after timeout/lockout +Given I login to REDCap with the user "Test_User1" +Then I see "My Projects" +Given I logout From 3ec636f9eeb886f68da1ad7432d7a7b3f7de9c50 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 16:44:23 -0400 Subject: [PATCH 23/96] Update A.2.2.600 - Account Lockout.feature Update comments --- .../A.2.2.600 - Account Lockout.feature | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature b/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature index 5f3f9de8..6cfe68c0 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.600 - Account Lockout.feature @@ -20,17 +20,17 @@ When I clear the field labeled "Number of failed login attempts before user is l Then I should see "Your system configuration values have now been changed!" Given I logout -##ACTION incorrect attempt +##ACTION Login with bad password; first failed attempt at logging in Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" Then I should see "ERROR: You entered an invalid user name or password!" -##ACTION incorrect attempt +##ACTION Try to login again with a bad password; we will be locked out Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" -##VERIFY Timeout / lockout +##VERIFY Timeout / lockout We only have to wait for 2 minute total this time Then I should see "ACCESS DENIED!" Given I wait for 2 minutes @@ -55,23 +55,23 @@ When I clear the field labeled "Number of failed login attempts before user is l Then I should see "Your system configuration values have now been changed!" Given I logout -##ACTION incorrect attempt +##ACTION Login with bad password; first failed attempt at logging in Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" Then I should see "ERROR" -##ACTION incorrect attempt +##ACTION Login with bad password; failed attempt at logging in Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" Then I should see "ERROR" -##ACTION incorrect attempt +##ACTION Try to login again with a bad password and we will be locked out Given I enter "Test_User1" into the input field labeled "Username:" And I enter "test" into the input field labeled "Password:" And I click on the button labeled "Log In" -##VERIFY Timeout / lockout +##VERIFY Timeout / lockout; We only have to wait for 1 minute total this time Then I should see "ACCESS DENIED!" Given I wait for 1 minute From 0749fabe1163f25c661bc1f8f37e918159dacd3c Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 16:46:02 -0400 Subject: [PATCH 24/96] Update A.2.2.700 - Account Lockout Time Change.feature Update as a REDUNDANT --- ....700 - Account Lockout Time Change.feature | 73 +------------------ 1 file changed, 4 insertions(+), 69 deletions(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature b/Feature Tests/A/Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature index 7d4bf03f..ee17033c 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature @@ -1,72 +1,7 @@ Feature: A.2.2.700 Add/Manage users - As a REDCap end user - I want to see that Users failed login lockout is functioning as expected. +As a REDCap end user +I want to see that Users failed login lockout is functioning as expected. - Scenario: A.2.2.700.100 User account locked time - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "Control Center" - And I click on the link labeled "Security & Authentication" - Then I should see "Security & Authentication Configuration" - - Given I clear the field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." - When I enter "1" into the input field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." - And I clear the field labeled "Amount of time user will be locked out after having failed login attempts exceeding the limit set above." - And I enter "2" into the input field labeled "Amount of time user will be locked out after having failed login attempts exceeding the limit set above." - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - And I logout - - #Login with bad password; first failed attempt at logging in - Given I enter "Test_User1" into the input field labeled "Username:" - And I enter "test" into the input field labeled "Password:" - And I click on the button labeled "Log In" - Then I should see "ERROR: You entered an invalid user name or password!" - - #Try to login again with a bad password; we will be locked out - Given I enter "Test_User1" into the input field labeled "Username:" - And I enter "test" into the input field labeled "Password:" - And I click on the button labeled "Log In" - Then I should see "ACCESS DENIED!" - - #Try logging in again after 1 minute - Given I wait for 1 minute - Given I attempt to login to REDCap with the user "Test_User1" - Then I should see "ACCESS DENIED!" - - #2 minutes of waiting total; now we can login - Given I wait for another 1 minute - When I attempt to login to REDCap with the user "Test_User1" - Then I should see "My Projects" - And I logout - - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "Control Center" - Then I click on the link labeled "Security & Authentication" - And I should see "Security & Authentication Configuration" - - Given I clear the field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." - When I enter "1" into the input field labeled "Number of failed login attempts before user is locked out for a specified amount of time, which is set below." - And I clear the field labeled "Amount of time user will be locked out after having failed login attempts exceeding the limit set above." - And I enter "1" into the input field labeled "Amount of time user will be locked out after having failed login attempts exceeding the limit set above." - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - And I logout - - #Login with bad password; first failed attempt at logging in - Given I enter "Test_User1" into the input field labeled "Username:" - And I enter "test" into the input field labeled "Password:" - And I click on the button labeled "Log In" - Then I should see "ERROR: You entered an invalid user name or password!" - - #Try to login again with a bad password and we will be locked out - Given I enter "Test_User1" into the input field labeled "Username:" - And I enter "test" into the input field labeled "Password:" - And I click on the button labeled "Log In" - Then I should see "ACCESS DENIED!" - - #We only have to wait for 1 minute total this time - Given I wait for 1 minute - When I attempt to login to REDCap with the user "Test_User1" - Then I should see "My Projects" - And I logout +Scenario: A.2.2.700.100 User account locked time +This feature test is REDUNDANT and can be viewed in A.2.2.600.100 From 4468d6116d948cd98b2df7a457418eaef90c7d5d Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 16:46:54 -0400 Subject: [PATCH 25/96] Rename A.2.2.700 - Account Lockout Time Change.feature to A.2.2.700 - REDUNDANT -Account Lockout Time Change.feature --- ...=> A.2.2.700 - REDUNDANT -Account Lockout Time Change.feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/A/Add Manage Users/{A.2.2.700 - Account Lockout Time Change.feature => A.2.2.700 - REDUNDANT -Account Lockout Time Change.feature} (100%) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature b/Feature Tests/A/Add Manage Users/A.2.2.700 - REDUNDANT -Account Lockout Time Change.feature similarity index 100% rename from Feature Tests/A/Add Manage Users/A.2.2.700 - Account Lockout Time Change.feature rename to Feature Tests/A/Add Manage Users/A.2.2.700 - REDUNDANT -Account Lockout Time Change.feature From 5ea8769bd6beae53167bd096c4b60898bb56b737 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 17:03:19 -0400 Subject: [PATCH 26/96] Update A.2.2.800 - Auto-Logout Inactivity Time.feature Add comments --- ....800 - Auto-Logout Inactivity Time.feature | 101 +++++++++++------- 1 file changed, 60 insertions(+), 41 deletions(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.800 - Auto-Logout Inactivity Time.feature b/Feature Tests/A/Add Manage Users/A.2.2.800 - Auto-Logout Inactivity Time.feature index 0934ca92..87165462 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.800 - Auto-Logout Inactivity Time.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.800 - Auto-Logout Inactivity Time.feature @@ -1,70 +1,89 @@ Feature: A.2.2.800 Add/Manage users - As a REDCap end user - I want to see that amount of inactivity time before auto logout time is functioning as expected. +As a REDCap end user +I want to see that amount of inactivity time before auto logout time is functioning as expected. - Scenario: A.2.2.800.100 User account locked time - - Given I login to REDCap with the user "Test_Admin" +Scenario: A.2.2.800.100 User account locked time +#SETUP control center Auto logout time +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Security & Authentication" - Then I should see "Security & Authentication Configuration" +Then I should see "Security & Authentication Configuration" - When I clear the field labeled "Auto logout time" +When I clear the field labeled "Auto logout time" And I enter "4" into the input field labeled "Auto logout time" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout +Then I should see "Your system configuration values have now been changed!" + +Given I logout + +#SETUP timeout warning +Given I login to REDCap with the user "Test_User1" +Then I should see"My Projects" - Given I login to REDCap with the user "Test_User1" - And I see "My Projects" +#FUNCTIONAL REQUIREMENT +##ACTION wait for timeout warning +Given I wait for 2 minutes +##VERIFY warning +Then I should see a dialog containing the following text: "REDCap Auto Logout Warning" - Given I wait for 2 minutes - Then I should see a dialog containing the following text: "REDCap Auto Logout Warning" +##ACTION wait for login expiration +Given I wait for another 2 minutes +##VERIFY login expiration message +Then I should see a dialog containing the following text: "Due to inactivity, your REDCap session has expired" - Given I wait for another 2 minutes - Then I should see a dialog containing the following text: "Due to inactivity, your REDCap session has expired" +##ACTION re-login +Given I click on the button labeled "Log In" in the dialog box +Then I should see "Please log in with your user name and password." - Given I click on the button labeled "Log In" in the dialog box - Then I should see "Please log in with your user name and password." +Given I login to REDCap with the user "Test_User1" +##VERIFY Can login +Then I should see"My Projects" - Given I login to REDCap with the user "Test_User1" - And I see "My Projects" - Given I logout +#SETUP control center Auto logout time +Given I logout - Given I login to REDCap with the user "Test_Admin" +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Security & Authentication" - Then I should see "Security & Authentication Configuration" +Then I should see "Security & Authentication Configuration" - When I clear the field labeled "Auto logout time" +When I clear the field labeled "Auto logout time" And I enter "3" into the input field labeled "Auto logout time" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout +Then I should see "Your system configuration values have now been changed!" + +Given I logout + +#FUNCTIONAL REQUIREMENT +##ACTION wait for timeout warning +Given I login to REDCap with the user "Test_User1" + And I wait for 2 minutes +##VERIFY warning +Then I should see a dialog containing the following text: "REDCap Auto Logout Warning" - Given I login to REDCap with the user "Test_User1" - Given I wait for 2 minutes - Then I should see a dialog containing the following text: "REDCap Auto Logout Warning" +##ACTION wait for login expiration +Given I wait for 1 minute +##VERIFY login expiration message +Then I should see a dialog containing the following text: "Due to inactivity, your REDCap session has expired" - Given I wait for 1 minute - Then I should see a dialog containing the following text: "Due to inactivity, your REDCap session has expired" +##ACTION re-login +Given I click on the button labeled "Log In" in the dialog box +Then I should see "Please log in with your user name and password." - Given I click on the button labeled "Log In" in the dialog box - Then I should see "Please log in with your user name and password." +Given I login to REDCap with the user "Test_User1" +##VERIFY Can login +Then I should see"My Projects" - Given I login to REDCap with the user "Test_User1" - And I see "My Projects" - Given I logout +Given I logout - Given I login to REDCap with the user "Test_Admin" +#SETUP control center Auto logout time +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Security & Authentication" - Then I should see "Security & Authentication Configuration" +Then I should see "Security & Authentication Configuration" - When I clear the field labeled "Auto logout time" +When I clear the field labeled "Auto logout time" And I enter "20" into the input field labeled "Auto logout time" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout - +Then I should see "Your system configuration values have now been changed!" From 1635fbc871df36325bf0bbfbbff701e04c6c199e Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 17:21:26 -0400 Subject: [PATCH 27/96] Update and rename A.2.2.500 - Tabular View.feature to A.2.2.500 - REDUNDANT Tabular View.feature REDUNDANT - updated with new status --- ...A.2.2.500 - REDUNDANT Tabular View.feature | 7 ++++++ .../A.2.2.500 - Tabular View.feature | 22 ------------------- 2 files changed, 7 insertions(+), 22 deletions(-) create mode 100644 Feature Tests/A/Add Manage Users/A.2.2.500 - REDUNDANT Tabular View.feature delete mode 100644 Feature Tests/A/Add Manage Users/A.2.2.500 - Tabular View.feature diff --git a/Feature Tests/A/Add Manage Users/A.2.2.500 - REDUNDANT Tabular View.feature b/Feature Tests/A/Add Manage Users/A.2.2.500 - REDUNDANT Tabular View.feature new file mode 100644 index 00000000..43b7ef0f --- /dev/null +++ b/Feature Tests/A/Add Manage Users/A.2.2.500 - REDUNDANT Tabular View.feature @@ -0,0 +1,7 @@ +Feature: A.2.2.500 Add/Manage users + + As a REDCap end user + I want to see that Users in tabular form is functioning as expected + + Scenario: A.2.2.500.100 Users in tabular form + This feature test is REDUNDANT and can be viewed in A.2.2.300.100 diff --git a/Feature Tests/A/Add Manage Users/A.2.2.500 - Tabular View.feature b/Feature Tests/A/Add Manage Users/A.2.2.500 - Tabular View.feature deleted file mode 100644 index c71c8558..00000000 --- a/Feature Tests/A/Add Manage Users/A.2.2.500 - Tabular View.feature +++ /dev/null @@ -1,22 +0,0 @@ -Feature: A.2.2.500 Add/Manage users - - As a REDCap end user - I want to see that Users in tabular form is functioning as expected - - Scenario: A.2.2.500.100 Users in tabular form - Given I login to REDCap with the user "Test_Admin" - And I click on the link labeled "Control Center" - And I click on the link labeled "Browse Users" - Then I should see "User Search: Search for user by username, first name, last name, or primary email" - -#FUNCTIONAL REQUIREMENT -##ACTION View Users in tabular form - When I click on the link labeled "View User List By Criteria" - And I select "All users" on the dropdown field labeled "Display only:" - And I click on the button labeled "Display User List" - -#VERIFY View Users in tabular form - Then I should see a table header and rows containing the following values in the browse users table: - | Username | First Name | Last Name | Email | - | test_admin | Admin | User | test_admin@test.edu | - From e2b13f5d6fa26f50ce330597a44afdb6753eb163 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 18:03:00 -0400 Subject: [PATCH 28/96] Update A.2.3.300 - Super Users and Account Managers.feature update comments and add relationship --- ...- Super Users and Account Managers.feature | 68 ++++++++++++++----- 1 file changed, 50 insertions(+), 18 deletions(-) diff --git a/Feature Tests/A/Assign Administrators/A.2.3.300 - Super Users and Account Managers.feature b/Feature Tests/A/Assign Administrators/A.2.3.300 - Super Users and Account Managers.feature index 45dcfaa9..2d945fc8 100644 --- a/Feature Tests/A/Assign Administrators/A.2.3.300 - Super Users and Account Managers.feature +++ b/Feature Tests/A/Assign Administrators/A.2.3.300 - Super Users and Account Managers.feature @@ -3,45 +3,77 @@ Feature: A.2.3.300 Assign administrators and account managers As a REDCap end user I want to see that Assign Super Users / Account Managers is functioning as expected - Scenario: A.2.3.300.100 Modify and Revoke Admin's User Rights - Given I login to REDCap with the user "Test_Admin" +Scenario: A.2.3.300.100 Modify and Revoke Admin's User Rights +#SETUP control center +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Administrator Privileges" - Then I should see "Set administrator privileges" +Then I should see "Set administrator privileges" - When I enter "Test_User1" into the field with the placeholder text of "Search users to add as admin" +#FUNCTIONAL REQUIREMENT +##ACTION Add administrator #A.2.3.200.100 +When I enter "Test_User1" into the field with the placeholder text of "Search users to add as admin" And I enable the Administrator Privilege "Set administrator privileges" for a new administrator And I click on the button labeled "Add" - Then I should see 'The user "Test_User1" has now been granted one or more administrator privileges' +Then I should see 'The user "Test_User1" has now been granted one or more administrator privileges' And I click on the button labeled "OK" And I should see "Test_User1" - When I click on the link labeled "Control Center" +##VERIFY added administrator +When I click on the link labeled "Control Center" And I click on the link labeled "Administrator Privileges" - Then I should see "Set administrator privileges" +Then I should see "Set administrator privileges" And I enable the Administrator Privilege "Manage user accounts" for the administrator "Test_User1" And I enable the Administrator Privilege "Modify system configuration pages" for the administrator "Test_User1" - Given I logout - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "Control Center" - Then I should see "Control Center Home" +Given I logout + +##VERIFY new administrator access to control center +Given I login to REDCap with the user "Test_User1" +When I click on the link labeled "Control Center" +Then I should see "Control Center Home" And I should see a link labeled "Browse Projects" And I should see a link labeled "Browse Users" And I should see a link labeled "Multi-Language Management" And I should see a link labeled "General Configuration" - Given I logout - Given I login to REDCap with the user "Test_Admin" +Given I logout + +##ACTION change new admins rights +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Administrator Privileges" - Then I should see "Set administrator privileges" +Then I should see "Set administrator privileges" - Given I enable the Administrator Privilege "Access to Control Center dashboards" for the administrator "Test_User1" - When I disable the Administrator Privilege "Set administrator privileges" for the administrator "Test_User1" +Given I enable the Administrator Privilege "Access to Control Center dashboards" for the administrator "Test_User1" +When I disable the Administrator Privilege "Set administrator privileges" for the administrator "Test_User1" And I disable the Administrator Privilege "Manage user accounts" for the administrator "Test_User1" And I disable the Administrator Privilege "Modify system configuration pages" for the administrator "Test_User1" And I logout - And I login to REDCap with the user "Test_User1" - Then I should see a link labeled "Control Center" + +##VERIFY limited admin rights +Given I login to REDCap with the user "Test_User1" +Then I should see a link labeled "Control Center" + +Given I logout + +##ACTION Remove new admin #A.2.3.200.100 +Given I login to REDCap with the user "Test_Admin" + And I click on the link labeled "Control Center" + And I click on the link labeled "Administrator Privileges" +Then I should see "Set administrator privileges" + +Given I disable the Administrator Privilege "Set administrator privileges" for the administrator "Test_User1" +Then I should see a dialog containing the following text: "Please be aware that you have unchecked ALL the administrator privileges for this user" + +Given I click on the button labeled "Close" in the dialog box + When I click on the link labeled "Administrator Privileges" +Then I should see "Set administrator privileges" + And I should NOT see "Test_User1" + +Given I logout + +##VERIFY user is no longer admin. +When I login to REDCap with the user "Test_User1" +Then I should NOT see a link labeled "Control Center" From 4a3cf1d166a0bfe3c15d76b5b64e16da4be272f9 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 18:09:55 -0400 Subject: [PATCH 29/96] Update A.2.3.400 - Assign Administrators and Account Managers.feature update test to add A.2.3.300.100 and A.2.3.200.100 --- ...dministrators and Account Managers.feature | 65 ++++++++++++++----- 1 file changed, 48 insertions(+), 17 deletions(-) diff --git a/Feature Tests/A/Assign Administrators/A.2.3.400 - Assign Administrators and Account Managers.feature b/Feature Tests/A/Assign Administrators/A.2.3.400 - Assign Administrators and Account Managers.feature index 7bbabf26..3b01f7cf 100644 --- a/Feature Tests/A/Assign Administrators/A.2.3.400 - Assign Administrators and Account Managers.feature +++ b/Feature Tests/A/Assign Administrators/A.2.3.400 - Assign Administrators and Account Managers.feature @@ -1,15 +1,18 @@ Feature: A.2.3.400 Assign administrators and account managers - As a REDCap end user - I want to see that Assign Super Users / Account Managers is functioning as expected +As a REDCap end user +I want to see that Assign Super Users / Account Managers is functioning as expected - Scenario: A.2.3.400.100 Give and remove user maximum user privileges - Given I login to REDCap with the user "Test_Admin" +Scenario: A.2.3.400.100 Give and remove user maximum user privileges + #SETUP control center +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Administrator Privileges" - Then I should see "Set administrator privileges" +Then I should see "Set administrator privileges" - When I enter "Test_User1" into the field with the placeholder text of "Search users to add as admin" +#FUNCTIONAL REQUIREMENT +##ACTION Add administrator #A.2.3.200.100 and #A.2.3.300.100 +When I enter "Test_User1" into the field with the placeholder text of "Search users to add as admin" And I enable the Administrator Privilege "Set administrator privileges" for a new administrator And I enable the Administrator Privilege "Access to all projects and data" for a new administrator And I enable the Administrator Privilege "Manage user accounts" for a new administrator @@ -18,35 +21,63 @@ Feature: A.2.3.400 Assign administrators and account managers And I enable the Administrator Privilege "Modify system configuration pages" for a new administrator And I enable the Administrator Privilege "Access to Control Center dashboards" for a new administrator And I click on the button labeled "Add" - Then I should see 'The user "Test_User1" has now been granted one or more administrator privileges' +##VERIFY added administrator +Then I should see 'The user "Test_User1" has now been granted one or more administrator privileges' And I click on the button labeled "OK" in the dialog box - Given I logout - And I login to REDCap with the user "Test_User1" +Given I logout + +##VERIFY new administrator access to control center +Given I login to REDCap with the user "Test_User1" And I click on the link labeled "Control Center" - Then I should see "Control Center Home" +Then I should see "Control Center Home" And I should see a link labeled "Browse Projects" And I should see a link labeled "Browse Users" And I should see a link labeled "General Configuration" - Given I logout - And I login to REDCap with the user "Test_Admin" +Given I logout + +##ACTION change new admins rights +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Administrator Privilege" - Then I should see "Set administrator privileges" - When I disable the Administrator Privilege "Set administrator privileges" for the administrator "Test_User1" +Then I should see "Set administrator privileges" + +When I disable the Administrator Privilege "Set administrator privileges" for the administrator "Test_User1" And I disable the Administrator Privilege "Access to all projects and data" for the administrator "Test_User1" And I disable the Administrator Privilege "Manage user accounts" for the administrator "Test_User1" And I disable the Administrator Privilege "Perform REDCap upgrades" for the administrator "Test_User1" And I disable the Administrator Privilege "Install, upgrade, and configure" for the administrator "Test_User1" And I disable the Administrator Privilege "Modify system configuration pages" for the administrator "Test_User1" And I disable the Administrator Privilege "Access to Control Center dashboards" for the administrator "Test_User1" - Then I should see a dialog containing the following text: "NOTICE" +Then I should see a dialog containing the following text: "NOTICE" And I should see a dialog containing the following text: "Please be aware that you have unchecked ALL the administrator privileges for this user" And I click on the button labeled "Close" in the dialog box - Given I logout - And I login to REDCap with the user "Test_User1" +Given I logout + +##VERIFY limited admin rights +Given I login to REDCap with the user "Test_User1" Then I should NOT see "Control Panel" And I logout +##ACTION Remove new admin #A.2.3.200.100 +Given I login to REDCap with the user "Test_Admin" + And I click on the link labeled "Control Center" + And I click on the link labeled "Administrator Privileges" +Then I should see "Set administrator privileges" + +Given I disable the Administrator Privilege "Set administrator privileges" for the administrator "Test_User1" +Then I should see a dialog containing the following text: "Please be aware that you have unchecked ALL the administrator privileges for this user" + +Given I click on the button labeled "Close" in the dialog box + When I click on the link labeled "Administrator Privileges" +Then I should see "Set administrator privileges" + And I should NOT see "Test_User1" + +Given I logout + +##VERIFY user is no longer admin. +When I login to REDCap with the user "Test_User1" +Then I should NOT see a link labeled "Control Center" + From 3b0d3800c8bbc374839000bc8c42d1857c2e9ad2 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 18:21:38 -0400 Subject: [PATCH 30/96] Update A.2.12.100 - System Status.feature Update feature test --- .../A.2.12.100 - System Status.feature | 47 +++++++++++-------- 1 file changed, 27 insertions(+), 20 deletions(-) diff --git a/Feature Tests/A/Security Settings/A.2.12.100 - System Status.feature b/Feature Tests/A/Security Settings/A.2.12.100 - System Status.feature index 32661c3d..08306074 100644 --- a/Feature Tests/A/Security Settings/A.2.12.100 - System Status.feature +++ b/Feature Tests/A/Security Settings/A.2.12.100 - System Status.feature @@ -1,39 +1,46 @@ Feature: A.2.12.100 Security Settings- The system shall support changing the system status between online and offline. - As a REDCap end user - I want to see that system status is functioning as expected +As a REDCap end user +I want to see that system status is functioning as expected - Scenario: A.2.12.100.100 System Status Online/Offline - Given I login to REDCap with the user "Test_Admin" +Scenario: A.2.12.100.100 System Status Online/Offline +#SETUP_CONTROL_CENTER +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "General Configuration" - Then I should see "Server configuration settings" +Then I should see "Server configuration settings" And I should see "System Status" And I should see the dropdown field labeled "System Status" with the option "SYSTEM ONLINE" selected - Given I select "SYSTEM OFFLINE" on the dropdown field labeled "System Status" +#FUNCTIONAL REQUIREMENT +##ACTION Move SYSTEM OFFLINE +Given I select "SYSTEM OFFLINE" on the dropdown field labeled "System Status" And I enter "This is a test. The Vanderbilt REDCap System is offline and will be back online shortly." into the textarea field labeled "Custom message to display to users when system is offline" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" +Then I should see "Your system configuration values have now been changed!" When I logout - #Test REDCap offline for Standard User - Given I login to REDCap with the user "Test_User1" - Then I should see "This is a test. The Vanderbilt REDCap System is offline and will be back online shortly." +##VERIFY #Test REDCap offline for Standard User +Given I login to REDCap with the user "Test_User1" +Then I should see "This is a test. The Vanderbilt REDCap System is offline and will be back online shortly." And I logout - #Test REDCap offline for Admin User - Given I login to REDCap with the user "Test_Admin" - Then I should see "REDCap and all its projects are currently OFFLINE and are not accessible to normal users." - And I click on the link labeled "Control Center" +##VERIFY #Test REDCap offline for Admin User +Given I login to REDCap with the user "Test_Admin" +Then I should see "REDCap and all its projects are currently OFFLINE and are not accessible to normal users." + + When I click on the link labeled "Control Center" And I click on the link labeled "General Configuration" - Then I should see "Server configuration settings" - Then I should see "System Status" - Given I select "SYSTEM ONLINE" on the dropdown field labeled "System Status" +Then I should see "Server configuration settings" + And I should see "System Status" + +#FUNCTIONAL REQUIREMENT +##ACTION Move SYSTEM ONLINE +Given I select "SYSTEM ONLINE" on the dropdown field labeled "System Status" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" +Then I should see "Your system configuration values have now been changed!" - #Test REDCap online for "Test_User1" - Given I login to REDCap with the user "Test_User1" +##VERIFY #Test REDCap online for "Test_User1" +Given I login to REDCap with the user "Test_User1" Then I should see "My Projects" From afab4622d3d8e97c2e6fffd5d22f9e55524c9b66 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 18:34:50 -0400 Subject: [PATCH 31/96] Update A.4.8.100 - Enable field validation.feature update --- ....4.8.100 - Enable field validation.feature | 120 +++++++++--------- 1 file changed, 61 insertions(+), 59 deletions(-) diff --git a/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature b/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature index 92a593e5..0017806c 100644 --- a/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature +++ b/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature @@ -6,95 +6,97 @@ I want to see that Field validation is functioning as expected Scenario: A.4.8.100.100 Control center Enable/disable field validation #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named "A.4.8.100.100 " by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_3.14.xml", and clicking the "Create Project" button + And I create a new project named "A.4.8.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_3.14.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the link labeled "Project Setup" -And I click on the button labeled "Move project to production" -And I click on the radio labeled "Keep ALL data saved so far" in the dialog box -And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status + And I click on the button labeled "Move project to production" + And I click on the radio labeled "Keep ALL data saved so far" in the dialog box + And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status Then I should see Project status: "Production" #FUNCTIONAL REQUIREMENT ##ACTION - Verify field validation Disable When I click on the link labeled "Control Center" -And I click on the link labeled "Field Validation Types" + And I click on the link labeled "Field Validation Types" Then I should see "Validation Types Currently Available for Use in All Projects" When I click on the button labeled "Disable" for the field labeled "Date (D-M-Y)" -And I click on the button labeled "Disable" for the field labeled "Datetime (M-D-Y H:M)" -And I click on the button labeled "Disable" for the field labeled "Datetime w/seconds (Y-M-D H:M:S)" -And I click on the button labeled "Disable" for the field labeled "Email" -And I click on the button labeled "Disable" for the field labeled "Integer" -And I click on the button labeled "Disable" for the field labeled "Number" -And I click on the button labeled "Disable" for the field labeled "Number (1 decimal place - comma as decimal)" -And I click on the button labeled "Disable" for the field labeled "Time (HH:MM)" + And I click on the button labeled "Disable" for the field labeled "Datetime (M-D-Y H:M)" + And I click on the button labeled "Disable" for the field labeled "Datetime w/seconds (Y-M-D H:M:S)" + And I click on the button labeled "Disable" for the field labeled "Email" + And I click on the button labeled "Disable" for the field labeled "Integer" + And I click on the button labeled "Disable" for the field labeled "Number" + And I click on the button labeled "Disable" for the field labeled "Number (1 decimal place - comma as decimal)" + And I click on the button labeled "Disable" for the field labeled "Time (HH:MM)" Then I should see the disabled icon for the field labeled "Date (D-M-Y)" -And I should see the disabled icon for the field labeled "Datetime (M-D-Y H:M)" -And I should see the disabled icon for the field labeled "Datetime w/seconds (Y-M-D H:M:S)" -And I should see the disabled icon for the field labeled "Email" And I should see the disabled icon for the field labeled "Integer" -And I should see the disabled icon for the field labeled "Number" -And I should see the disabled icon for the field labeled "Number (1 decimal place - comma as decimal)" - And I should see the disabled icon for the field labeled "Time (HH:MM)" + And I should see the disabled icon for the field labeled "Datetime (M-D-Y H:M)" + And I should see the disabled icon for the field labeled "Datetime w/seconds (Y-M-D H:M:S)" + And I should see the disabled icon for the field labeled "Email" And I should see the disabled icon for the field labeled "Integer" + And I should see the disabled icon for the field labeled "Number" + And I should see the disabled icon for the field labeled "Number (1 decimal place - comma as decimal)" + And I should see the disabled icon for the field labeled "Time (HH:MM)" ##VERIFY: options not available on validation dropdown field When I click on the link labeled "My Projects" -And I click on the link labeled "A.4.8.100.100" -And I click on the link labeled "Designer" -And I click on the button labeled "Enter Draft Mode" + And I click on the link labeled "A.4.8.100.100" + And I click on the link labeled "Designer" + And I click on the button labeled "Enter Draft Mode" Then I should see "The project is now in Draft Mode." + When I click on the instrument labeled "Data Types" -And I click on the button labeled "Add Field" at the bottom of the instrument -And I select the dropdown option labeled "Text Box" from the dropdown field with the placeholder text "Select a Type of Field" + And I click on the button labeled "Add Field" at the bottom of the instrument + And I select the dropdown option labeled "Text Box" from the dropdown field with the placeholder text "Select a Type of Field" Then I should see the field labeled "Validation?" When I click on the dropdown field for the field labeled "Validation?" Then I should NOT see the dropdown option "Date (D-M-Y)" -And I should NOT see the dropdown option " Datetime (M-D-Y H:M)" -And I should NOT see the dropdown option " Datetime w/seconds (Y-M-D H:M:S)" -And I should NOT see the dropdown option "Email" -And I should NOT see the dropdown option "Integer" -And I should NOT see the dropdown option "Number" - And I should NOT see the dropdown option "Number (1 decimal place - comma as decimal)" -And I should NOT see the dropdown option "Time (HH:MM)" + And I should NOT see the dropdown option " Datetime (M-D-Y H:M)" + And I should NOT see the dropdown option " Datetime w/seconds (Y-M-D H:M:S)" + And I should NOT see the dropdown option "Email" + And I should NOT see the dropdown option "Integer" + And I should NOT see the dropdown option "Number" + And I should NOT see the dropdown option "Number (1 decimal place - comma as decimal)" + And I should NOT see the dropdown option "Time (HH:MM)" #SETUP -Given I click on the button labeled "Cancel" - When I click on the link labeled "Control Center" - And I click on the link labeled "Field Validation Types" + Given I click on the button labeled "Cancel" + And I click on the link labeled "Control Center" + And I click on the link labeled "Field Validation Types" Then I should see "Validation Types Currently Available for Use in All Projects" - When I click on the button labeled "Enable" for the field labeled "Date (D-M-Y)" -And I click on the button labeled "Enable" for the field labeled "Datetime (M-D-Y H:M)" - And I click on the button labeled "Enable" for the field labeled "Datetime w/seconds (Y-M-D H:M:S)" - And I click on the button labeled "Enable" for the field labeled "Email" -And I click on the button labeled "Enable" for the field labeled "Integer" -And I click on the button labeled "Enable" for the field labeled "Number" -And I click on the button labeled "Enable" for the field labeled "Number (1 decimal place - comma as decimal)" -And I click on the button labeled "Enable" for the field labeled "Time (HH:MM)" + +When I click on the button labeled "Enable" for the field labeled "Date (D-M-Y)" + And I click on the button labeled "Enable" for the field labeled "Datetime (M-D-Y H:M)" + And I click on the button labeled "Enable" for the field labeled "Datetime w/seconds (Y-M-D H:M:S)" + And I click on the button labeled "Enable" for the field labeled "Email" + And I click on the button labeled "Enable" for the field labeled "Integer" + And I click on the button labeled "Enable" for the field labeled "Number" + And I click on the button labeled "Enable" for the field labeled "Number (1 decimal place - comma as decimal)" + And I click on the button labeled "Enable" for the field labeled "Time (HH:MM)" Then I should see the green checkmark icon for the field labeled "Date (D-M-Y)" - And I should see the green checkmark icon for the field labeled "Datetime (M-D-Y H:M)" -And I should see the green checkmark icon for the field labeled "Datetime w/seconds (Y-M-D H:M:S)" -And I should see the green checkmark icon for the field labeled "Email" -And I should see the green checkmark icon for the field labeled "Integer" - And I should see the green checkmark icon for the field labeled "Number" -And I should see the green checkmark icon for the field labeled "Number (1 decimal place - comma as decimal)" -And I should see the green checkmark icon for the field labeled "Time (HH:MM)" + And I should see the green checkmark icon for the field labeled "Datetime (M-D-Y H:M)" + And I should see the green checkmark icon for the field labeled "Datetime w/seconds (Y-M-D H:M:S)" + And I should see the green checkmark icon for the field labeled "Email" + And I should see the green checkmark icon for the field labeled "Integer" + And I should see the green checkmark icon for the field labeled "Number" + And I should see the green checkmark icon for the field labeled "Number (1 decimal place - comma as decimal)" + And I should see the green checkmark icon for the field labeled "Time (HH:MM)" #FUNCTIONAL REQUIREMENT ##ACTION - Verify field validation Enable ##VERIFY: options are available on validation dropdown field When I click on the link labeled "My Projects" -And I click on the link labeled "A.4.8.100.100" And I click on the link labeled "Designer" -And I click on the instrument labeled "Data Types" -And I click on the button labeled "Add Field" at the bottom of the instrument -And I select the dropdown option labeled "Text Box" from the dropdown field with the placeholder text "Select a Type of Field" Then I should see the field labeled "Validation?" -When I click on the dropdown field for the field labeled "Validation?" + And I click on the link labeled "A.4.8.100.100" And I click on the link labeled "Designer" + And I click on the instrument labeled "Data Types" + And I click on the button labeled "Add Field" at the bottom of the instrument + And I select the dropdown option labeled "Text Box" from the dropdown field with the placeholder text "Select a Type of Field" Then I should see the field labeled "Validation?" + And I click on the dropdown field for the field labeled "Validation?" Then I should see the dropdown option "Date (D-M-Y)" -And I should see the dropdown option " Datetime (M-D-Y H:M)" -And I should see the dropdown option " Datetime w/seconds (Y-M-D H:M:S)" -And I should see the dropdown option "Email" + And I should see the dropdown option " Datetime (M-D-Y H:M)" + And I should see the dropdown option " Datetime w/seconds (Y-M-D H:M:S)" + And I should see the dropdown option "Email" And I should see the dropdown option "Integer" -And I should see the dropdown option "Number" -And I should see the dropdown option "Number (1 decimal place - comma as decimal)" -And I should see the dropdown option "Time (HH:MM)" And I click on the button labeled "Cancel" + And I should see the dropdown option "Number" + And I should see the dropdown option "Number (1 decimal place - comma as decimal)" + And I should see the dropdown option "Time (HH:MM)" And I click on the button labeled "Cancel" From b69f226e206320302535b73c691ea5046dd869e8 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 18:40:39 -0400 Subject: [PATCH 32/96] Update A.4.8.100 - Enable field validation.feature fix --- .../A.4.8.100 - Enable field validation.feature | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature b/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature index 0017806c..7053a5da 100644 --- a/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature +++ b/Feature Tests/A/Field Validation/A.4.8.100 - Enable field validation.feature @@ -50,7 +50,8 @@ When I click on the instrument labeled "Data Types" Then I should see the field labeled "Validation?" When I click on the dropdown field for the field labeled "Validation?" -Then I should NOT see the dropdown option "Date (D-M-Y)" +Then I should see the dropdown option "None" + And I should NOT see the dropdown option "Date (D-M-Y)" And I should NOT see the dropdown option " Datetime (M-D-Y H:M)" And I should NOT see the dropdown option " Datetime w/seconds (Y-M-D H:M:S)" And I should NOT see the dropdown option "Email" From 56dab49ec79d729165a41b0d5f1640a68f73a2d8 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 18:54:30 -0400 Subject: [PATCH 33/96] Update A.6.4.100 - User Create Projects.feature --- .../A.6.4.100 - User Create Projects.feature | 61 +++++++++++-------- 1 file changed, 35 insertions(+), 26 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature b/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature index 88d647a2..15d6208f 100644 --- a/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature +++ b/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature @@ -4,47 +4,56 @@ Feature: A.6.4.100 Manage project creation, deletion, and settings Control Center: The system shall support the option to limit the creation of new projects to administrators. Scenario: A.6.4.100.100 User's ability to create new projects - - Given I login to REDCap with the user "Test_Admin" +#SETUP_CONTROL_CENTER +Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" +Then I should see "System-level User Settings" - When I select "No, only Administrators can create new projects" on the dropdown field labeled "Allow normal users to create new projects?" +#FUNCTIONAL REQUIREMENT +##ACTION Admin only can make project +When I select "No, only Administrators can create new projects" on the dropdown field labeled "Allow normal users to create new projects?" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" +Then I should see "Your system configuration values have now been changed!" - # BEGIN: STEPS FOR ATS - # - EMAIL ADDRESS SET FOR REDCAP ADMIN - without it, project request behavior does not work properly - # - CUSTOM MESSAGE SET - Makes the dialog box pop up when requesting a project - Given I click on the link labeled "General Configuration" - Then I should see "General Configuration" +# Manual tester skips next step. +# BEGIN: STEPS FOR ATS +# - EMAIL ADDRESS SET FOR REDCAP ADMIN - without it, project request behavior does not work properly +# - CUSTOM MESSAGE SET - Makes the dialog box pop up when requesting a project +Given I click on the link labeled "General Configuration" +Then I should see "General Configuration" - When I enter "redcap@test.instance" into the input field labeled "Email Address of REDCap Administrator" +When I enter "redcap@test.instance" into the input field labeled "Email Address of REDCap Administrator" And I enter "You are now creating a test project" into the textarea field labeled "Custom message when creating/copying project" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed" - # END: STEPS FOR ATS ### +Then I should see "Your system configuration values have now been changed" +# END: STEPS FOR ATS ### - Given I logout +Given I logout - Given I login to REDCap with the user "Test_User1" +##VERIFY User can create new project with request to Admin +Given I login to REDCap with the user "Test_User1" And I create a new project named "A.6.4.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Send Request" button And I click on the button labeled "I Agree" in the dialog box - Then I should see "Request Sent!" - Given I logout +Then I should see "Request Sent!" + +Given I logout - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "Control Center" +#FUNCTIONAL REQUIREMENT +##ACTION Normal user can make new project +Given I login to REDCap with the user "Test_Admin" + And I click on the link labeled "Control Center" And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" +Then I should see "System-level User Settings" - When I select "Yes, normal users can create new projects" on the dropdown field labeled "Allow normal users to create new projects?" +When I select "Yes, normal users can create new projects" on the dropdown field labeled "Allow normal users to create new projects?" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout +Then I should see "Your system configuration values have now been changed!" + +Given I logout - Given I login to REDCap with the user "Test_User1" - And I create a new project named "A.6.4.100.101" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button +##VERIFY User can create new project without request +Given I login to REDCap with the user "Test_User1" + And I create a new project named "A.6.4.100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button And I click on the button labeled "I Agree" in the dialog box - Then I should see "Your new REDCap project has been created" +Then I should see "Your new REDCap project has been created" From fd9d2d00123dd36c363fd2195e215db07b002b2f Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 13 Oct 2023 19:13:51 -0400 Subject: [PATCH 34/96] Update A.6.4.200 - Move to Production.feature update feature --- .../A.6.4.200 - Move to Production.feature | 132 +++++++++--------- 1 file changed, 65 insertions(+), 67 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.200 - Move to Production.feature b/Feature Tests/A/Project Setup/A.6.4.200 - Move to Production.feature index 4bfbb9f7..b331be44 100644 --- a/Feature Tests/A/Project Setup/A.6.4.200 - Move to Production.feature +++ b/Feature Tests/A/Project Setup/A.6.4.200 - Move to Production.feature @@ -3,98 +3,96 @@ Feature: A.6.4.200 Manage project creation, deletion, and settings As a REDCap end user I want to see that project management features are functioning as expected - Scenario: A.6.4.200.100 User requests admin move project to production - Given I login to REDCap with the user "Test_Admin" - And I create a new project named "A.6.4.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.200.100" - And I click on the link labeled "User Rights" - And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" - And I click on the button labeled "Assign to role" - And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown - When I click on the button labeled exactly "Assign" on the role selector dropdown - Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table - - When I click on the link labeled "Control Center" +Scenario: A.6.4.200.100 User requests admin move project to production +#SETUP_CONTROL_CENTER +Given I login to REDCap with the user "Test_Admin" + And I click on the link labeled "Control Center" And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "No, only Administrators can move projects to production" on the dropdown field labeled "Allow normal users to move projects to production?" +Then I should see "System-level User Settings" + +When I select "No, only Administrators can move projects to production" on the dropdown field labeled "Allow normal users to move projects to production?" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout +Then I should see "Your system configuration values have now been changed!" + +Given I logout - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.200.100" - And I click on the link labeled "Project Setup" - Then I should see a button labeled "Move project to production" +#SETUP_DEV +Given I login to REDCap with the user "Test_User1" + And I create a new project named "A.6.4.200.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button +Then I should see "Project Setup" - When I click on the button labeled "Move project to production" +#FUNCTIONAL REQUIREMENT +##ACTION User request move to production +When I click on the button labeled "Move project to production" And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "Yes, Request Admin to Move to Production Status" in the dialog box to request a change in project status - Then I should see "Request pending" - And I click on the link labeled "Logging" - Then I should see a table header and rows containing the following values in the logging table: +##VERIFY +Then I should see "Request pending" + +##VERIFY_LOG +When I click on the link labeled "Logging" +Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | | mm/dd/yyyy hh:mm | test_user1 | Manage/Design | Send request to move project to production status | - Given I logout - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "My Projects" +Given I logout + +##ACTION Admin moves project to production +Given I login to REDCap with the user "Test_Admin" + And I click on the link labeled "My Projects" And I click on the link labeled "A.6.4.200.100" And I click on the link labeled "Control Center" And I click on the link labeled "To-Do List" +Then I should see "Pending Requests" + And I should see the "Move to prod" request created for the project named "A.6.4.200.100" within the "Pending Requests" table - Then I should see "Pending Requests" +When I click on the "process request" icon for the "Move to prod" request created for the project named "A.6.4.200.100" within the "Pending Requests" table +Then I should see "Move Project To Production Status" in the iframe - Given I should see the "Move to prod" request created for the project named "A.6.4.200.100" within the "Pending Requests" table - When I click on the "process request" icon for the "Move to prod" request created for the project named "A.6.4.200.100" within the "Pending Requests" table - Then I should see "Move Project To Production Status" in the iframe - - Given I click on the radio labeled "Keep ALL data saved so far." in the dialog box in the iframe - When I click on the button labeled "YES, Move to Production Status" in the dialog box in the iframe +When I click on the radio labeled "Keep ALL data saved so far." in the dialog box in the iframe + And I click on the button labeled "YES, Move to Production Status" in the dialog box in the iframe And I close the iframe window - Then I should see the "Move to prod" request created for the project named "A.6.4.200.100" within the "Completed & Archived Requests" table +Then I should see the "Move to prod" request created for the project named "A.6.4.200.100" within the "Completed & Archived Requests" table - Given I click on the link labeled "My Projects" +##VERIFY +When I click on the link labeled "My Projects" And I click on the link labeled "A.6.4.200.100" - Then I should see Project status: "Production" - And I click on the link labeled "Logging" - Then I should see a table header and rows containing the following values in the logging table: +Then I should see Project status: "Production" + +##VERIFY_LOG +When I click on the link labeled "Logging" +Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | | mm/dd/yyyy hh:mm | test_admin | Manage/Design | Move project to Production status | - Scenario: A.6.4.200.200 User moves project to production - Given I login to REDCap with the user "Test_Admin" - And I create a new project named "A.6.4.200.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.200.200" - And I click on the link labeled "User Rights" - And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" - And I click on the button labeled "Assign to role" - And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown - And I click on the button labeled exactly "Assign" on the role selector dropdown - Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table - - When I click on the link labeled "Control Center" + +Scenario: A.6.4.200.200 User moves project to production +#SETUP_CONTROL_CENTER +When I click on the link labeled "Control Center" And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "Yes, normal users can move projects to production" on the dropdown field labeled "Allow normal users to move projects to production?" +Then I should see "System-level User Settings" + +When I select "Yes, normal users can move projects to production" on the dropdown field labeled "Allow normal users to move projects to production?" And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout +Then I should see "Your system configuration values have now been changed!" + +Given I logout - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.200.200" - And I click on the link labeled "Project Setup" - Then I should see a button labeled "Move project to production" +#SETUP_DEV +Given I login to REDCap with the user "Test_Admin" + And I create a new project named "A.6.4.200.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button +Then I should see "Project Setup" - Given I click on the button labeled "Move project to production" +#FUNCTIONAL REQUIREMENT +##ACTION User moves project into production +When I should see a button labeled "Move project to production" And I click on the radio labeled "Keep ALL data saved so far." in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status - Then I should see Project status: "Production" - Given I click on the link labeled "Logging" - Then I should see a table header and rows containing the following values in the logging table: +##VERIFY_PRODUCTION +Then I should see Project status: "Production" + +##VERIFY_LOG +When I click on the link labeled "Logging" +Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | | mm/dd/yyyy hh:mm | test_user1 | Manage/Design | Move project to Production status | From e794cbdfd5b4798b1e816cb6ffcc985a129fde52 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 20 Oct 2023 12:37:49 -0400 Subject: [PATCH 35/96] Update A.6.4.300 - Edit Survey Responses.feature #REDUNDANT - Tested in A.6.4.1600.100 #CHILD --- .../A.6.4.300 - Edit Survey Responses.feature | 51 +------------------ 1 file changed, 2 insertions(+), 49 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.300 - Edit Survey Responses.feature b/Feature Tests/A/Project Setup/A.6.4.300 - Edit Survey Responses.feature index 74d9cb44..49216841 100644 --- a/Feature Tests/A/Project Setup/A.6.4.300 - Edit Survey Responses.feature +++ b/Feature Tests/A/Project Setup/A.6.4.300 - Edit Survey Responses.feature @@ -5,53 +5,6 @@ Feature: A.6.4.300 Manage project creation, deletion, and settings Scenario: A.6.4.300.100 User's ability to edit survey responses - Given I login to REDCap with the user "Test_Admin" - And I create a new project named "A.6.4.300.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.300.100" - - When I click on the link labeled "Project Setup" - And I click on the button labeled "Move project to production" - And I click on the radio labeled "Keep ALL data saved so far" in the dialog box - And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status - Then I should see Project status: "Production" - - And I click on the link labeled "User Rights" - And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" - And I click on the button labeled "Assign to role" - And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown - When I click on the button labeled exactly "Assign" on the role selector dropdown - Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table - - When I click on the link labeled "Control Center" - And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "Enabled" on the dropdown field labeled "Allow users to edit survey responses?" - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout - - Given I login to REDCap with the user "Test_User1" - And I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.300.100" - And I click on the link labeled "Record Status Dashboard" - And I locate the bubble for the "Survey" instrument on event "Event 1" for record ID "1" and click on the bubble - #Then I should see "Survey response is editable" - Given I logout - - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "Control Center" - And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "Disabled" on the dropdown field labeled "Allow users to edit survey responses?" - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout - - Given I login to REDCap with the user "Test_User1" - And I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.300.100" - And I click on the link labeled "Record Status Dashboard" - And I locate the bubble for the "Survey" instrument on event "Event 1" for record ID "1" and click on the bubble - #Then I should see "Survey response is read-only" +#REDUNDANT - Tested in A.6.4.1600.100 +#CHILD From 269022e5035766de20f469bfdf61d65afda34cfc Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 20 Oct 2023 12:38:02 -0400 Subject: [PATCH 36/96] Update A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature #PARENT to A.6.4.300.100 User's ability to edit survey responses --- ...600 - Enable & Disable Editing of Survey Responses.feature | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature b/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature index 077f40a1..4238bd9f 100644 --- a/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature +++ b/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature @@ -4,6 +4,7 @@ Feature: Control Center: The system shall allow users to edit survey responses t I want to see that allow edit survey response is functioning as expected Scenario: A.6.4.1600.100 +#PARENT to A.6.4.300.100 User's ability to edit survey responses #SETUP_DEV Given I login to REDCap with the user "Test_Admin" And I create a new project named "A.6.4.1600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button @@ -45,7 +46,8 @@ When I click on the checkbox labeled "Edit user privileges" for the instrument l And I click on the button labeled "Save Changes" Then I should see "User "test_admin" was successfully edited" -#SETUP Check edit survey function in a record +#SETUP +#A.6.4.300.100 User's ability to edit survey responses Given I click the link labeled "Record Status Dashboard" And I click the bubble for the "Survey" longitudinal instrument on event "Event Three" for record "1" And I click on the button labeled "Survey options" And I select the option labeled "Open survey" From 60125e56fcbe425cfddc5790273448cf70e2d0df Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 20 Oct 2023 12:41:25 -0400 Subject: [PATCH 37/96] Rename A.6.4.300 - Edit Survey Responses.feature to A.6.4.300 - REDUNDANT Edit Survey Responses.feature Fix title --- ...eature => A.6.4.300 - REDUNDANT Edit Survey Responses.feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/A/Project Setup/{A.6.4.300 - Edit Survey Responses.feature => A.6.4.300 - REDUNDANT Edit Survey Responses.feature} (100%) diff --git a/Feature Tests/A/Project Setup/A.6.4.300 - Edit Survey Responses.feature b/Feature Tests/A/Project Setup/A.6.4.300 - REDUNDANT Edit Survey Responses.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.300 - Edit Survey Responses.feature rename to Feature Tests/A/Project Setup/A.6.4.300 - REDUNDANT Edit Survey Responses.feature From aae954273a64c9fcb8622cdb191add77446a24c7 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 20 Oct 2023 12:53:25 -0400 Subject: [PATCH 38/96] Rename A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature to A.6.4.1600 - Edit Survey Responses.feature Change title --- ...sponses.feature => A.6.4.1600 - Edit Survey Responses.feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/A/Project Setup/{A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature => A.6.4.1600 - Edit Survey Responses.feature} (100%) diff --git a/Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature b/Feature Tests/A/Project Setup/A.6.4.1600 - Edit Survey Responses.feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.1600 - Enable & Disable Editing of Survey Responses.feature rename to Feature Tests/A/Project Setup/A.6.4.1600 - Edit Survey Responses.feature From 35e543078527e5a5eb1edeec6fc5443f8274f1e6 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 20 Oct 2023 12:55:28 -0400 Subject: [PATCH 39/96] Rename A.6.4.1500 - Enable & Disable Survey.feature to A.6.4.1500 - Manage Survey User..feature --- ...le Survey.feature => A.6.4.1500 - Manage Survey User..feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/A/Project Setup/{A.6.4.1500 - Enable & Disable Survey.feature => A.6.4.1500 - Manage Survey User..feature} (100%) diff --git a/Feature Tests/A/Project Setup/A.6.4.1500 - Enable & Disable Survey.feature b/Feature Tests/A/Project Setup/A.6.4.1500 - Manage Survey User..feature similarity index 100% rename from Feature Tests/A/Project Setup/A.6.4.1500 - Enable & Disable Survey.feature rename to Feature Tests/A/Project Setup/A.6.4.1500 - Manage Survey User..feature From ef5ea5de5a47834062fed1a0a47ba8da81d80dbb Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 13:19:19 -0400 Subject: [PATCH 40/96] Update B.3.16.1200 - Data import overwrite.feature Lots of fixes! --- ....3.16.1200 - Data import overwrite.feature | 46 +++++++++++++++++-- 1 file changed, 41 insertions(+), 5 deletions(-) diff --git a/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature b/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature index 09519f66..5973adf5 100644 --- a/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature +++ b/Feature Tests/B/Data import/B.3.16.1200 - Data import overwrite.feature @@ -16,22 +16,49 @@ And I click on the button labeled "YES, Move to Production Status" in the dialog And I click on the button labeled "Ok" in the pop-up box Then I should see "Project Status: Production" +##Verify Data present +Given I see a table row containing the following values in the reports table: + | A | All data (all records and fields) | + When I click on the button labeled "View Report" + + Then I should see a table header and rows containing the following values in the report data table: + | Record ID | Event Name | Repeat Instrument | Repeat Instance | Data Access Group | Survey Identifier | Name | Email | + | 1 | Event 1 (Arm 1: Arm 1) | | | | | | email@test.edu | + #FUNCTIONAL REQUIREMENT -##ACTION: Error during import +##ACTION: Import new data, ignoring blank values When I click on the link labeled "Data Import Tool" And I click on the tab labeled "CVS import" Then I should see the button labeled "Choose File" When I click on the button labeled "Choose File" -And I select the file labeled "B3161200100_INACCURATE" +And I select the file labeled "B3161200100_ACCURATE" And I click on the button labeled "Upload File" + ##VERIFY -Then I should see "ERROR:" -And I click on the link labeled "RETURN TO PREVIOUS PAGE" +Then I should see "Your document was uploaded successfully" + +When I click on the button labeled "Import Data" +Then I should see "Import Successful!" + +##Verify Data present +Given I see a table row containing the following values in the reports table: + | A | All data (all records and fields) | + When I click on the button labeled "View Report" + + Then I should see a table header and rows containing the following values in the report data table: + | Record ID | Event Name | Repeat Instrument | Repeat Instance | Data Access Group | Survey Identifier | Name | Email | + | 1 | Event 1 (Arm 1: Arm 1) | | | | | | email@test.edu | #FUNCTIONAL REQUIREMENT -##ACTION: w DAGs +##ACTION: Import new data, overwrite blank values +When I click on the link labeled "Data Import Tool" +And I click on the tab labeled "CVS import" +Then I should see the button labeled "Choose File" + When I click on the button labeled "Choose File" +And I select "Yes, blank values in the file will overwrite existing values" on the dropdown field labeled "Allow blank values to overwrite existing saved values?" +Given I click on the button labeled "Yes, I understand" in the dialog box And I select the file labeled "B3161200100_ACCURATE" And I click on the button labeled "Upload File" @@ -40,3 +67,12 @@ Then I should see "Your document was uploaded successfully" When I click on the button labeled "Import Data" Then I should see "Import Successful!" + +##Verify Data was overwritten with a blank +Given I see a table row containing the following values in the reports table: + | A | All data (all records and fields) | + When I click on the button labeled "View Report" + + Then I should see a table header and rows containing the following values in the report data table: + | Record ID | Event Name | Repeat Instrument | Repeat Instance | Data Access Group | Survey Identifier | Name | Email | + | 1 | Event 1 (Arm 1: Arm 1) | | | | | | | From fc68bcf020ad5febc25f05ecb7b7d83d7d1a58b1 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 15:29:10 -0400 Subject: [PATCH 41/96] Update A.6.4.400 - Draft Mode.feature Lots of changes --- .../A.6.4.400 - Draft Mode.feature | 212 ++++++++++-------- 1 file changed, 115 insertions(+), 97 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature b/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature index 75fcdb75..a8f55783 100644 --- a/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature +++ b/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature @@ -5,9 +5,11 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Scenario: A.6.4.400.100 User's ability to approve draft changes without administrative approval +#SETUP Given I login to REDCap with the user "Test_Admin" And I create a new project named "A.6.4.400.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button +#SETUP_CONTROL_CENTER # BEGIN: STEPS FOR ATS # - EMAIL ADDRESS SET FOR REDCAP ADMIN - without it, project request behavior does not work properly Given I click on the link labeled "Control Center" @@ -19,6 +21,7 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Then I should see "Your system configuration values have now been changed" # END: STEPS FOR ATS ### +#SETUP_USER When I click on the link labeled "My Projects" And I click on the link labeled "A.6.4.400.100" @@ -29,18 +32,22 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings When I click on the button labeled exactly "Assign" on the role selector dropdown Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table +#SETUP_PRODUCTION Given I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status Then I should see Project status: "Production" +##VERIFY_LOG And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | | mm/dd/yyyy hh:mm | test_admin | Manage/Design | Move project to Production status | +#FUNCTIONAL REQUIREMENT +#SETUP_CONTROL_CENTER Never allow user to automatically approve changes When I click on the link labeled "Control Center" And I click on the link labeled "User Settings" Then I should see "System-level User Settings" @@ -49,12 +56,15 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Then I should see "Your system configuration values have now been changed!" Given I logout +#FUNCTIONAL REQUIREMENT +#User submit change request Given I login to REDCap with the user "Test_User1" When I click on the link labeled "My Projects" And I click on the link labeled "A.6.4.400.100" And I click on the link labeled "Designer" And I click on the button labeled "Enter Draft Mode" Then I should see "The project is now in Draft Mode" +##VERIFY_LOG And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: @@ -65,7 +75,8 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings When I click on the button labeled "Submit Changes for Review" And I click on the button labeled "Submit" in the dialog box Then I should see "Awaiting review of project changes" - And I click on the link labeled "Logging" +##VERIFY_LOG +And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | @@ -73,6 +84,8 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Given I logout +#FUNCTIONAL REQUIREMENT +#Admin rejects changes Given I login to REDCap with the user "Test_Admin" When I click on the link labeled "My Projects" And I click on the link labeled "A.6.4.400.100" @@ -85,10 +98,13 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Then I should see "Project Changes Rejected / User Notified" Given I logout +#FUNCTIONAL REQUIREMENT +#User submit change request Given I login to REDCap with the user "Test_User1" When I click on the link labeled "My Projects" And I click on the link labeled "A.6.4.400.100" - And I click on the link labeled "Logging" +##VERIFY_LOG +And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | @@ -102,7 +118,8 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings When I click on the button labeled "Submit Changes for Review" And I click on the button labeled "Submit" in the dialog box Then I should see "Awaiting review of project changes" - And I click on the link labeled "Logging" +##VERIFY_LOG +And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | @@ -110,6 +127,8 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Given I logout +#FUNCTIONAL REQUIREMENT +#Admin commits changes Given I login to REDCap with the user "Test_Admin" When I click on the link labeled "My Projects" And I click on the link labeled "A.6.4.400.100" @@ -125,7 +144,8 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Given I login to REDCap with the user "Test_User1" When I click on the link labeled "My Projects" And I click on the link labeled "A.6.4.400.100" - And I click on the link labeled "Logging" +##VERIFY_LOG +And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | @@ -134,27 +154,10 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings And I click on the link labeled "Designer" Then I should see "Enter Draft Mode" - - Scenario: A.6.4.400.200 User's ability to approve draft changes without administrative approval if no existing fields were modified - Given I login to REDCap with the user "Test_Admin" - And I create a new project named "A.6.4.400.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.200" - - And I click on the link labeled "User Rights" - And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" - And I click on the button labeled "Assign to role" - And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown - When I click on the button labeled exactly "Assign" on the role selector dropdown - Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table - - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Move project to production" - And I click on the radio labeled "Keep ALL data saved so far" in the dialog box - And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status - Then I should see Project status: "Production" - - When I click on the link labeled "Control Center" +##A.6.4.400.200 User's ability to approve draft changes without administrative approval if no existing fields were modified +##SETUP_CONTROL_CENTER Allow user to approve changes automatically + Given I login to REDCap with the user "Test_Admin" + And I click on the link labeled "Control Center" And I click on the link labeled "User Settings" Then I should see "System-level User Settings" When I select "Yes, if no existing fields were modified" on the dropdown field labeled "Allow production Draft Mode changes to be approved automatically under certain conditions?" @@ -162,24 +165,37 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Then I should see "Your system configuration values have now been changed!" Given I logout +#FUNCTIONAL REQUIREMENT +#User Modifies field and submit changes - request sent to admin Given I login to REDCap with the user "Test_User1" When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.200" + And I click on the link labeled "A.6.4.400.100" And I click on the link labeled "Designer" And I click on the button labeled "Enter Draft Mode" Then I should see "The project is now in Draft Mode" When I click on the link labeled "Data Types" - And I click on the Edit image for the field named "Radio Button Manual" + And I click on the Edit image for the field named "Radio" And I enter Choices of "102, Choice102" into the open "Edit Field" dialog box And I click on the button labeled "Save" And I click on the button labeled "Submit Changes for Review" And I click on the button labeled "Submit" in the dialog box + Then I should see "Awaiting review of project changes" + +##VERIFY_LOG +When I click on the link labeled "Logging" + + Then I should see a table header and rows containing the following values in the logging table: + | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | + | mm/dd/yyyy hh:mm | test_admin | Manage/Design | Request approval for production project modifications| + Given I logout +#FUNCTIONAL REQUIREMENT +#Admin remove changes Given I login to REDCap with the user "Test_Admin" When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.200" + And I click on the link labeled "A.6.4.400.100" And I click on the link labeled "Designer" Then I should see "REVIEW CHANGES?" @@ -187,17 +203,21 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings And I click on the button labeled "Remove All Drafted Changes" And I click on the button labeled "Remove All Drafted Changes" in the dialog box Then I should see "Project Changes Removed / User Notified" + + ##VERIFY_LOG +When I click on the link labeled "Logging" + + Then I should see a table header and rows containing the following values in the logging table: + | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | + | mm/dd/yyyy hh:mm | test_admin | Manage/Design | Remove production project modifications| + Given I logout +#FUNCTIONAL REQUIREMENT +#User modifies by adding field and submitting changes - changes automatically accepted Given I login to REDCap with the user "Test_User1" When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.200" - And I click on the link labeled "Logging" - - Then I should see a table header and rows containing the following values in the logging table: - | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | - | mm/dd/yyyy hh:mm | test_admin | Manage/Design | Remove production project modifications | - + And I click on the link labeled "A.6.4.400.100" And I click on the link labeled "Designer" And I click on the button labeled "Enter Draft Mode" Then I should see "The project is now in Draft Mode" @@ -212,41 +232,27 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings And I click on the button labeled "Close" in the dialog box And I click on the link labeled "Logging" + ##VERIFY_LOG Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | | mm/dd/yyyy hh:mm | test_user1 | Manage/Design | Approve production project modifications (automatic) | | mm/dd/yyyy hh:mm | test_user1 | Manage/Design | Create project field | - Scenario: A.6.4.400.300 User's ability to approve draft changes without administrative approval if no critical issues exist - Given I login to REDCap with the user "Test_Admin" - And I create a new project named "A.6.4.400.300" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.300" - And I click on the link labeled "User Rights" - - And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" - And I click on the button labeled "Assign to role" - And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown - When I click on the button labeled exactly "Assign" on the role selector dropdown - Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table - - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Move project to production" - And I click on the radio labeled "Keep ALL data saved so far" in the dialog box - And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status - Then I should see Project status: "Production" - +## A.6.4.400.300 User's ability to approve draft changes without administrative approval if no critical issues exist +##SETUP_CONTROL_CENTER Allow user to approve changes automatically if project has no records OR if has records and no critical issues exist + Given I login to REDCap with the user "Test_Admin" When I click on the link labeled "Control Center" And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "Yes, if project has no records OR if has records and no critical issues exist" on the dropdown field labeled "Allow production Draft Mode changes to be approved automatically under certain conditions?" + And I select "Yes, if project has no records OR if has records and no critical issues exist" on the dropdown field labeled "Allow production Draft Mode changes to be approved automatically under certain conditions?" And I click on the button labeled "Save Changes" Then I should see "Your system configuration values have now been changed!" Given I logout +#FUNCTIONAL REQUIREMENT +#User automatically submit changes with no change Given I login to REDCap with the user "Test_User1" When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.300" + And I click on the link labeled "A.6.4.400.100" And I click on the link labeled "Designer" And I click on the button labeled "Enter Draft Mode" Then I should see "The project is now in Draft Mode" @@ -255,33 +261,31 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings And I click on the button labeled "Submit" in the dialog box Then I should see "Changes Were Made Automatically" And I click on the button labeled "Close" in the dialog box - - And I click on the button labeled "Enter Draft Mode" - Then I should see "The project is now in Draft Mode" - - And I click on the link labeled "Logging" +##VERIFY_LOG + And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | - | mm/dd/yyyy hh:mm | test_user1 | Manage/Design | Approve production project modifications (automatic) | - - When I click on the link labeled "Designer" + | mm/dd/yyyy hh:mm | test_user1 | Manage/Design | Approve production project modifications (automatic) | - #We were already in DRAFT MODE. See line 231. - #And I click on the button labeled "Enter Draft Mode" - #Then I should see "The project is now in Draft Mode" - - When I click on the link labeled "Data Types" +#FUNCTIONAL REQUIREMENT +#User creates critical modification to field and request change +When I click on the link labeled "Designer" + And I click on the button labeled "Enter Draft Mode" + Then I should see "The project is now in Draft Mode" + +When I click on the link labeled "Data Types" And I click on the Edit image for the field named "Radio Button Manual" - #We are deleting the third option and renaming "100, Choice100" to "101, Choice100" in one step + #We are deleting the third option and renaming "100, Choice100" to "101, Choice100" in one step. This is a critical change And I clear field and enter Choices of "9..9, Choice99{enter}101, Choice100" into the open "Edit Field" dialog box And I click on the button labeled "Save" And I click on the button labeled "Submit Changes for Review" And I click on the button labeled "Submit" in the dialog box Then I should see "Awaiting review of project changes" - And I click on the link labeled "Logging" +##VERIFY_LOG +And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | @@ -289,9 +293,9 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Given I logout +#FUNCTIONAL REQUIREMENT +#Admin removes All Drafted Changes Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.300" And I click on the link labeled "Designer" Then I should see "REVIEW CHANGES?" @@ -300,17 +304,20 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings And I click on the button labeled "Remove All Drafted Changes" And I click on the button labeled "Remove All Drafted Changes" in the dialog box Then I should see "Project Changes Removed / User Notified" - Given I logout - - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.300" - And I click on the link labeled "Logging" + +##VERIFY_LOG +And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | | mm/dd/yyyy hh:mm | test_admin | Manage/Design | Remove production project modifications | + Given I logout + + +#FUNCTIONAL REQUIREMENT +#User creates critical modification to field and request change +Given I login to REDCap with the user "Test_User1" And I click on the link labeled "Designer" And I click on the button labeled "Enter Draft Mode" Then I should see "The project is now in Draft Mode" @@ -333,9 +340,9 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings Given I logout +#FUNCTIONAL REQUIREMENT +#Admin Commit Changes Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.300" And I click on the link labeled "Designer" Then I should see "REVIEW CHANGES?" @@ -344,27 +351,21 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings And I click on the button labeled "COMMIT CHANGES" And I click on the button labeled "COMMIT CHANGES" in the dialog box Then I should see "Project Changes Committed / User Notified" - Given I logout - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.400.300" +##VERIFY_LOG And I click on the link labeled "Logging" Then I should see a table header and rows containing the following values in the logging table: | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | | mm/dd/yyyy hh:mm | test_admin | Manage/Design | Approve production project modifications | - - And I click on the link labeled "Designer" - And I click on the button labeled "Enter Draft Mode" - Then I should see "The project is now in Draft Mode" - - When I click on the link labeled "Data Types" - And I click on the Edit image for the field named "Radio Button Manual" - Then I should see a dialog containing the following text: "Edit Field" - When I verify Choice of "101, Choice100" in the open "Edit Field" dialog box - Then I click on the button labeled "Cancel" in the dialog box - + +##VERIFY_CODEBOOK + And I click on the link labeled "Codebook" + Then I should see a table header and rows containing the following values in the logging table: + | # | Variable / Field Name | Field Label | Field Attributes (Field Type, Validation, Choices, Calculations, etc.) | + | 14 | [radio_button_manual] | Radio Button Manual |radio 9..9 Choice99 101 Choice100 | + + ##VERIFY_DE When I click on the link labeled "Data Exports, Reports, and Stats" Given I see a table rows containing the following values in the reports table: @@ -388,6 +389,16 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings When I click on the link labeled "Designer" + Given I logout + + +#FUNCTIONAL REQUIREMENT +#User creates non-critical modification to field and automatically committed +Given I login to REDCap with the user "Test_User1" + And I click on the link labeled "Designer" + And I click on the button labeled "Enter Draft Mode" + Then I should see "The project is now in Draft Mode" + When I click on the link labeled "Data Types" And I click on the Edit image for the field named "Radio Button Manual" @@ -399,3 +410,10 @@ Feature: A.6.4.400 Manage project creation, deletion, and settings And I click on the button labeled "Submit" in the dialog box Then I should see "Changes Were Made Automatically" And I click on the button labeled "Close" in the dialog box + +##VERIFY_LOG + And I click on the link labeled "Logging" + + Then I should see a table header and rows containing the following values in the logging table: + | Time / Date | Username | Action | List of Data ChangesOR Fields Exported | + | mm/dd/yyyy hh:mm | test_admin | Manage/Design | Approve production project modifications (automatic) | From da6f89ba79ec4f92e469d2ace745672a7df740a2 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 17:02:58 -0400 Subject: [PATCH 42/96] Update A.6.4.500 - Repeatable Instruments.feature Lots of fixes --- ...A.6.4.500 - Repeatable Instruments.feature | 408 ++++++++++-------- 1 file changed, 238 insertions(+), 170 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature b/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature index 7c064f3f..5f7a6265 100644 --- a/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature +++ b/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature @@ -1,194 +1,262 @@ -Feature: A.6.4.500 Manage project creation, deletion, and settings - - Manage project creation, deletion, and settings - Control Center: The system shall support the option to limit adding or modifying repeatable instruments while in production to administrators. - - Scenario: A.6.4.500.100 User's ability to add or modify repeatable instrument while in production mode - - Given I login to REDCap with the user "Test_Admin" - And I create a new project named "A.6.4.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.500.100" - And I click on the link labeled "User Rights" - And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" - And I click on the button labeled "Assign to role" - And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown - When I click on the button labeled exactly "Assign" on the role selector dropdown - Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table - - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Move project to production" - And I click on the radio labeled "Keep ALL data saved so far" in the dialog box - And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status - Then I should see Project status: "Production" - - When I click on the link labeled "Control Center" - And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "No, only Administrators can modify the repeating instance setup in production" on the dropdown field labeled "Allow normal users to modify the 'Repeating Instruments & Events' settings for projects while in production status?" - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout - - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.500.100" - And I click on the link labeled "Project Setup" - Then I should see that repeatable instruments are unchangeable - Given I logout - - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.500.100" - When I click on the link labeled "Control Center" - And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "Yes, normal users can modify the repeating instance setup in production" on the dropdown field labeled "Allow normal users to modify the 'Repeating Instruments & Events' settings for projects while in production status?" - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout - - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.500.100" - And I click on the link labeled "Project Setup" - Then I should see "Repeating instruments and events" - - When I open the dialog box for the Repeatable Instruments and Events module - And I close the popup - And I select "-- not repeating --" on the dropdown field labeled "Event 1 (Arm 1: Arm 1)" - And I select "Repeat Instruments (repeat independently of each other)" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" - And I check the checkbox labeled "Survey" - And I click on the button labeled "Save" - Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." - - Given I click on the button labeled "Close" in the dialog box - And I click on the link labeled "Logging" - Then I should see a table header and rows containing the following values in the logging table: +Feature: Control Center: The system shall support the option to limit adding or modifying repeatable instruments while in production to administrators + +As a REDCap end user +I want to see that repeatable function is functioning as expected + +Scenario: A.6.4.500.100 User's ability to add or modify repeatable instrument while in production mode +#SETUP_PROJECT +Given I login to REDCap with the user "Test_Admin" +And I create a new project named "A.6.4.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button +When I click on the link labeled "My Projects" +And I click on the link labeled "A.6.4.500.100" +#SETUP_USER +And I click on the link labeled "User Rights" +And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" +And I click on the button labeled "Assign to role" +And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown +And I click on the button labeled exactly "Assign" on the role selector dropdown + +Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table + +#SETUP_PRODUCTION +Given I click on the link labeled "Project Setup" +And I click on the button labeled "Move project to production" +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box +And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status + +Then I should see Project status: "Production" + +#FUNCTIONAL REQUIREMENT - Only admins can modify repeating instance setup in production +#SETUP_CONTROL_CENTER +When I click on the link labeled "Control Center" +And I click on the link labeled "User Settings" + +Then I should see "System-level User Settings" + +When I select "No, only Administrators can modify the repeating instance setup in production" on the dropdown field labeled "Allow normal users to modify the 'Repeating Instruments & Events' settings for projects while in production status?" +And I click on the button labeled "Save Changes" + +Then I should see "Your system configuration values have now been changed!" + +Given I logout + +#FUNCTIONAL REQUIREMENT +#User unable to see repeatable instruments +Given I login to REDCap with the user "Test_User1" +When I click on the link labeled "My Projects" +And I click on the link labeled "A.6.4.500.100" +And I click on the link labeled "Project Setup" + +Then I should see a button labeled "Modify" on the field labeled "Repeating instruments and events" + #And I should see that I am unable to click on Modify + +Given I logout + +#FUNCTIONAL REQUIREMENT - normal users can modify the repeating instance setup in production +#SETUP_CONTROL_CENTER +Given I login to REDCap with the user "Test_Admin" +When I click on the link labeled "My Projects" +And I click on the link labeled "A.6.4.500.100" +And I click on the link labeled "Control Center" +And I click on the link labeled "User Settings" + +Then I should see "System-level User Settings" + +When I select "Yes, normal users can modify the repeating instance setup in production" on the dropdown field labeled "Allow normal users to modify the 'Repeating Instruments & Events' settings for projects while in production status?" +And I click on the button labeled "Save Changes" + +Then I should see "Your system configuration values have now been changed!" + +Given I logout + +#FUNCTIONAL REQUIREMENT +#User modifies repeat instrument +Given I login to REDCap with the user "Test_User1" +When I click on the link labeled "My Projects" +And I click on the link labeled "A.6.4.500.100" +And I click on the link labeled "Project Setup" + +Then I should see "Repeating instruments and events" + +When I open the dialog box for the Repeatable Instruments and Events module +And I close the popup +And I click on the button labeled "Save" + +Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." + +Given I click on the button labeled "Close" in the dialog box + +##VERIFY_LOG +And I click on the link labeled "Logging" + +Then I should see a table header and rows containing the following values in the logging table: | Username | Action | List of Data ChangesOR Fields Exported | | test_user1 | Manage/Design | Set up repeating instruments/events | - Given I click on the link labeled "Add / Edit Records" - Given I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page - And I click the bubble to select a record for the "Survey" longitudinal instrument on event "Event Three" +#Verify record home page +When I click on the link labeled "Add / Edit Records" +And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page +And I click the bubble to select a record for the "Survey" longitudinal instrument on event "Event Three" +And I enter "MyName" into the data entry form field labeled "Name" +And I select the submit option labeled "Save & Add New Instance" on the Data Collection Instrument +And I enter "MyOtherName" into the data entry form field labeled "Name" +And I select the submit option labeled "Save & Exit Form" on the Data Collection Instrument + +##VERIFY_DE +Given I click on the link labeled "Data Exports, Reports, and Stats" + +Then I see a table row containing the following values in the reports table: + | A | All data (all records and fields) | + +When I click on the button labeled "View Report" + +Then I should see table rows containing the following values in the report data table: + | Record ID | Event Name | Repeat Instrument | Repeat Instance | name_survey | + | 1 | Event Three (Arm 1: Arm 1) | Survey | 1 | Name MyName | + | 1 | Event Three (Arm 1: Arm 1) | Survey | 2 | Name MyOtherName | +And I should NOT see "Data Types" - And I enter "MyName" into the data entry form field labeled "Name" - Given I select the submit option labeled "Save & Add New Instance" on the Data Collection Instrument - And I enter "MyOtherName" into the data entry form field labeled "Name" - Given I select the submit option labeled "Save & Exit Form" on the Data Collection Instrument +#FUNCTIONAL REQUIREMENT +#User deletes repeatable instance +Given I click on the link labeled "Add / Edit Records" +And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page +And I click the bubble to select a record for the "Survey" longitudinal instrument on event "Event Three" instance "2" +And I click on the button labeled "Delete data for THIS FORM only" - And I click the bubble to select a record for the "Survey" longitudinal instrument on event "Event Three" and click the repeating instrument bubble for the first instance - Then I see "Current instance:" +Then I should see a dialog containing the following text: "Delete all data on this form" - Given I click on the link labeled "Record ID 1" - And I click the bubble to select a record for the "Data Types" longitudinal instrument on event "Event 1" - Then I should NOT see "Current instance:" +Given I click on the button labeled "Delete data for THIS FORM only" in the dialog box - Given I click on the link labeled "Data Exports, Reports, and Stats" - When I see a dialog containing the following text: "Save your changes?" - Then I click on the button labeled "Leave without saving changes" in the dialog box +Then I should NOT see "(#2)" - Given I see a table row containing the following values in the reports table: - | A | All data (all records and fields) | - When I click on the button labeled "View Report" - - Then I should see table rows containing the following values in the report data table: - | Event Three (Arm 1: Arm 1) | Survey | 1 | Name MyName | - | Event Three (Arm 1: Arm 1) | Survey | 2 | Name MyOtherName | - And I should NOT see "Data Types" - - Given I click on the link labeled "Project Setup" - Then I should see "Repeating instruments and events" - - When I open the dialog box for the Repeatable Instruments and Events module - And I close the popup - And I select "Repeat Instruments (repeat independently of each other)" on the dropdown field labeled "Event 1 (Arm 1: Arm 1)" - And I check the checkbox labeled "Data Types" - And I select "-- not repeating --" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" - And I click on the button labeled "Save" - Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." - - Given I click on the button labeled "Close" in the dialog box - When I click on the link labeled "Logging" - Then I should see a table header and rows containing the following values in the logging table: +#FUNCTIONAL REQUIREMENT +#User modifies repeat instrument to capture orphaned data +Given I click on the link labeled "Project Setup" + +Then I should see "Repeating instruments and events" + +When I open the dialog box for the Repeatable Instruments and Events module +And I close the popup +And I select "Repeat Instruments (repeat independently of each other)" on the dropdown field labeled "Event 1 (Arm 1: Arm 1)" +And I check the checkbox labeled "Data Types" +And I select "-- not repeating --" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" +And I click on the button labeled "Save" + +Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." + +When I click on the button labeled "Close" in the dialog box + + ##VERIFY_LOG +When I click on the link labeled "Logging" + +Then I should see a table header and rows containing the following values in the logging table: | Username | Action | List of Data ChangesOR Fields Exported | | test_user1 | Manage/Design | Set up repeating instruments/events | - Given I click on the link labeled "Add / Edit Records" - And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page - And I click the bubble to select a record for the "Survey" longitudinal instrument on event "Event Three" - Then I should NOT see "Current instance:" - And I click on the button labeled "Cancel" - Then I see "data entry cancelled - not saved" - And I click the bubble to select a record for the "Data Types" longitudinal instrument on event "Event 1" - Then I see "Current instance:" +#Verify record home page +Given I click on the link labeled "Add / Edit Records" +And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page +And I click the bubble to select a record for the "Survey" longitudinal instrument on event "Event Three" + +Then I should NOT see "Current instance:" + +When I click on the button labeled "Cancel" +And I click on the button labeled "OK" in the dialog box + +Then I see "data entry cancelled - not saved" + +When I click the bubble to select a record for the "Data Types" longitudinal instrument on event "Event 1" + +Then I see "Current instance:" - Given I click on the link labeled "Data Exports, Reports, and Stats" - When I see a dialog containing the following text: "Save your changes?" - Then I click on the button labeled "Leave without saving changes" in the dialog box +##VERIFY_DE +Given I click on the link labeled "Data Exports, Reports, and Stats" - Given I see a table row containing the following values in the reports table: +Then I see a table row containing the following values in the reports table: | A | All data (all records and fields) | - When I click on the button labeled "View Report" - Then I should see a table row containing the following values in the report data table: +When I click on the button labeled "View Report" + +Then I should see a table row containing the following values in the report data table: | Event 2 (Arm 1: Arm 1) | | 1 | | | Name | email@test.edu | Unverified | - And I should NOT see "MyOtherName" - - When I click on the link labeled "Project Setup" - And I open the dialog box for the Repeatable Instruments and Events module - And I close the popup - And I select "-- not repeating --" on the dropdown field labeled "Event 2 (Arm 1: Arm 1)" - And I select "Repeat Entire Event (repeat all instruments together)" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" - And I click on the button labeled "Save" - Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." - - Given I click on the button labeled "Close" in the dialog box - And I click on the link labeled "Logging" - Then I should see a table header and rows containing the following values in the logging table: +And I should NOT see "MyOtherName" + +#FUNCTIONAL REQUIREMENT +#User modifies repeat event +When I click on the link labeled "Project Setup" +And I open the dialog box for the Repeatable Instruments and Events module +And I close the popup +And I select "-- not repeating --" on the dropdown field labeled "Event 2 (Arm 1: Arm 1)" +And I select "Repeat Entire Event (repeat all instruments together)" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" +And I click on the button labeled "Save" + +Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." + +Given I click on the button labeled "Close" in the dialog box + + ##VERIFY_LOG +And I click on the link labeled "Logging" + +Then I should see a table header and rows containing the following values in the logging table: | Username | Action | List of Data ChangesOR Fields Exported | | test_user1 | Manage/Design | Set up repeating instruments/events | - Given I click on the link labeled "Add / Edit Records" - And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page - Then I should NOT see "(#3)" - When I click on the button labeled "Add new" - And I click the bubble to add a record for the "Survey" longitudinal instrument on event "(#3)" - Then I should see "Editing existing Record ID 1" + #Verify record home page +Given I click on the link labeled "Add / Edit Records" +And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page + +Then I should NOT see "(#3)" + +When I click on the button labeled "Add new" +And I click the bubble to add a record for the "Survey" longitudinal instrument on event "(#3)" - When I clear field and enter "My repeat event name" into the data entry form field labeled "Name" - And I select the submit option labeled "Save & Exit Form" on the Data Collection Instrument - Then I should see "(#3)" +Then I should see "Editing existing Record ID 1" - And I click on the link labeled "Data Exports, Reports, and Stats" - Given I see a table row containing the following values in the reports table: +When I clear field and enter "My repeat event name" into the data entry form field labeled "Name" +And I select the submit option labeled "Save & Exit Form" on the Data Collection Instrument + +Then I should see "(#3)" + +##VERIFY_DE +When I click on the link labeled "Data Exports, Reports, and Stats" +And I see a table row containing the following values in the reports table: | A | All data (all records and fields) | - And I click on the button labeled "View Report" - And I should see a "1" within the "Event Three (Arm 1: Arm 1)" row of the column labeled "Repeat Instance" of the Reports table - And I should see "My repeat event name" - - When I click on the link labeled "Project Setup" - And I open the dialog box for the Repeatable Instruments and Events module - And I close the popup - And I select "-- not repeating --" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" - And I select "Repeat Entire Event (repeat all instruments together)" on the dropdown field labeled "Event 2 (Arm 1: Arm 1)" - And I click on the button labeled "Save" - Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." - - Given I click on the button labeled "Close" in the dialog box - When I click on the link labeled "Data Exports, Reports, and Stats" - Given I see a table row containing the following values in the reports table: +And I click on the button labeled "View Report" +And I should see a "1" within the "Event Three (Arm 1: Arm 1)" row of the column labeled "Repeat Instance" of the Reports table +And I should see "My repeat event name" + +#FUNCTIONAL REQUIREMENT +#User modifies repeat event to see orphaned event +When I click on the link labeled "Project Setup" +And I open the dialog box for the Repeatable Instruments and Events module +And I close the popup +And I select "Repeat Entire Event (repeat all instruments together)" on the dropdown field labeled "Event 2 (Arm 1: Arm 1)" +And I select "-- not repeating --" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" +And I click on the button labeled "Save" + +Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." + +Given I click on the button labeled "Close" in the dialog box + +##VERIFY_DE +When I click on the link labeled "Data Exports, Reports, and Stats" + +Then I see a table row containing the following values in the reports table: | A | All data (all records and fields) | - And I click on the button labeled "View Report" - And I should see a "1" within the "Event 2 (Arm 1: Arm 1)" row of the column labeled "Repeat Instance" of the Reports table - And I should see "" within the "Event Three (Arm 1: Arm 1)" row of the column labeled "Repeat Instance" of the Reports table - And I should NOT see "My repeat event name" - - Given I click on the link labeled "Add / Edit Records" - And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page - And I click the X to delete all data related to the event named "Event 2" - And I click on the button labeled "Delete this instance of this event" in the dialog box - Then I should see "successfully deleted entire event of data" - And I should NOT see "(#2)" - + +When I click on the button labeled "View Report" + +Then I should see a "1" within the "Event 2 (Arm 1: Arm 1)" row of the column labeled "Repeat Instance" of the Reports table +And I should see "" within the "Event Three (Arm 1: Arm 1)" row of the column labeled "Repeat Instance" of the Reports table +And I should NOT see "My repeat event name" + +#FUNCTIONAL REQUIREMENT +#User deletes repeatable event +Given I click on the link labeled "Add / Edit Records" +And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page +And I click the X to delete all data related to the event named "Event 2" +And I click on the button labeled "Delete this instance of this event" in the dialog box + +Then I should see "successfully deleted entire event of data" +And I should NOT see "(#2)" From 966c3f976d11c832cd2cf6ca704a2db8b3314cbf Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 17:26:08 -0400 Subject: [PATCH 43/96] Update A.6.4.500 - Repeatable Instruments.feature fix my fixes --- .../A.6.4.500 - Repeatable Instruments.feature | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature b/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature index 5f7a6265..8dea2869 100644 --- a/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature +++ b/Feature Tests/A/Project Setup/A.6.4.500 - Repeatable Instruments.feature @@ -80,6 +80,9 @@ Then I should see "Repeating instruments and events" When I open the dialog box for the Repeatable Instruments and Events module And I close the popup +And I select "-- not repeating --" on the dropdown field labeled "Event 1 (Arm 1: Arm 1)" +And I select "Repeat Instruments (repeat independently of each other)" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" +And I check the checkbox labeled "Survey" And I click on the button labeled "Save" Then I should see a dialog containing the following text: "Your settings for repeating instruments and/or events have been successfully saved." @@ -206,7 +209,7 @@ Then I should see a table header and rows containing the following values in the Given I click on the link labeled "Add / Edit Records" And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page -Then I should NOT see "(#3)" +Then I should NOT see "(#2)" When I click on the button labeled "Add new" And I click the bubble to add a record for the "Survey" longitudinal instrument on event "(#3)" @@ -216,15 +219,15 @@ Then I should see "Editing existing Record ID 1" When I clear field and enter "My repeat event name" into the data entry form field labeled "Name" And I select the submit option labeled "Save & Exit Form" on the Data Collection Instrument -Then I should see "(#3)" +Then I should see "(#2)" ##VERIFY_DE When I click on the link labeled "Data Exports, Reports, and Stats" And I see a table row containing the following values in the reports table: | A | All data (all records and fields) | And I click on the button labeled "View Report" -And I should see a "1" within the "Event Three (Arm 1: Arm 1)" row of the column labeled "Repeat Instance" of the Reports table -And I should see "My repeat event name" +Then I should see a table row containing the following values in the report data table: + | Event Three (Arm 1: Arm 1) | My repeat event name | #FUNCTIONAL REQUIREMENT #User modifies repeat event to see orphaned event From b9068e6e8e16e049d7a82e7e246ccf3dae7fe267 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 17:34:52 -0400 Subject: [PATCH 44/96] Update A.6.4.1600 - Edit Survey Responses.feature fix --- .../A/Project Setup/A.6.4.1600 - Edit Survey Responses.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.1600 - Edit Survey Responses.feature b/Feature Tests/A/Project Setup/A.6.4.1600 - Edit Survey Responses.feature index 4238bd9f..b8dd030f 100644 --- a/Feature Tests/A/Project Setup/A.6.4.1600 - Edit Survey Responses.feature +++ b/Feature Tests/A/Project Setup/A.6.4.1600 - Edit Survey Responses.feature @@ -52,7 +52,7 @@ Given I click the link labeled "Record Status Dashboard" And I click the bubble for the "Survey" longitudinal instrument on event "Event Three" for record "1" And I click on the button labeled "Survey options" And I select the option labeled "Open survey" And I enter "SURVEY RESPONSE" in the field labeled "Name" And I click on the button labeled "Submit" - Then I should see "Thank you for taking this survey" And I click on the button labeled "Close survey" + Then I should see "Thank you for taking the survey" And I click on the button labeled "Close survey" ##VERIFY_RSD Given I click on the button labeled "Leave without saving changes" From 4e3883cbb9cb60afaee306f4da75110621b64b11 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 19:31:03 -0400 Subject: [PATCH 45/96] Update A.6.4.600 - Events and Arms in Production.feature Consolidate --- ...00 - Events and Arms in Production.feature | 617 ++++++++---------- 1 file changed, 267 insertions(+), 350 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.600 - Events and Arms in Production.feature b/Feature Tests/A/Project Setup/A.6.4.600 - Events and Arms in Production.feature index 3ac84596..a5887d58 100644 --- a/Feature Tests/A/Project Setup/A.6.4.600 - Events and Arms in Production.feature +++ b/Feature Tests/A/Project Setup/A.6.4.600 - Events and Arms in Production.feature @@ -1,374 +1,291 @@ -Feature: A.6.4.600 Manage project creation, deletion, and settings - - Manage project creation, deletion, and settings - Control Center: The system shall support the option to limit adding or modifying events and arms while in production to administrators. Note: user can add instrument to event in production. - - Scenario: A.6.4.600.100 User's ability to add or modify events and arms while in production mode - - Given I login to REDCap with the user "Test_Admin" - And I create a new project named "A.6.4.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.600.100" - Then I should see Project status: "Development" - - When I click on the link labeled "User Rights" - And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" - And I click on the button labeled "Assign to role" - And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown - When I click on the button labeled exactly "Assign" on the role selector dropdown - Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table - Given I logout - - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.600.100" - And I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - - Given I should see a link labeled "Add New Arm" - When I click on the link labeled "Add New Arm" - And I enter "Arm 3" into the input field labeled "Arm name:" - And I click on the button labeled "Save" - Then I should see "Arm name: Arm 3" - - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: - | Username | Action | List of Data ChangesOR Fields Exported | - | test_user1 | Manage/Design | Create arm | - | test_user1 | Manage/Design | Arm 3: Arm 3 | +Feature: A.6.4.600 Manage project creation, deletion, and settings. Control Center: The system shall support the option to limit adding or modifying events and arms while in production to administrators. Note: user can add instrument to event in production. + +As a REDCap end user +I want to see that manage project is functioning as expected + +Scenario: A.6.4.600.100 User's ability to add or modify events and arms while in production mode +#SETUP_CONTROL_CENTER +Given I login to REDCap with the user "Test_Admin" +And I click on the link labeled "Control Center" +And I click on the link labeled "User Settings" +And I select "No, only Administrators can add/modify events in production" on the dropdown field labeled "Allow normal users to add or modify events and arms on the Define My Events page for longitudinal projects while in production status?" +And I click on the button labeled "Save Changes" +Then I should see "Your system configuration values have now been changed!" + +#SETUP_DEV +When I create a new project named "A.6.4.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - And I click on the link labeled "Arm 3" +#SETUP_USER +When I click on the link labeled "User Rights" +And I enter "Test_User1" into the field with the placeholder text of "Assign new user to role" +And I click on the button labeled "Assign to role" +And I select "1_FullRights" on the dropdown field labeled "Select Role" on the role selector dropdown +When I click on the button labeled exactly "Assign" on the role selector dropdown +Then I should see "Test User1" within the "1_FullRights" row of the column labeled "Username" of the User Rights table +Given I logout - Given I add an event named "Event 1" with offset of 0 days into the currently selected arm - Then I should see "Event 1" in the define events table +#FUNCTIONAL REQUIREMENT +##ACTION - User Adds new arm in Development mode +Given I login to REDCap with the user "Test_User1" +And I click on the link labeled "Project Setup" +And I click on the button labeled "Define My Events" - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: - | Username | Action | List of Data ChangesOR Fields Exported | - | test_user1 | Manage/Design | Create arm | - | test_user1 | Manage/Design | Arm 3: Arm 3 | - | test_user1 | Manage/Design | Create event | - | test_user1 | Manage/Design | Event: Event 1, Arm: Arm 3, Days Offset: 0, Offset Range: -0/+0 | +Then I should see a link labeled "Add New Arm" - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - And I click on the link labeled "Arm Two" - And I click on the link labeled "Rename Arm 2" - Then I should see a button labeled "Save" +When I click on the link labeled "Add New Arm" +And I enter "Arm 3" into the input field labeled "Arm name:" +And I click on the button labeled "Save" - Given I clear field and enter "Arm 2" into the input field labeled "Arm name" - And I click on the button labeled "Save" - Then I should see "Arm name: Arm 2" +Then I should see "Arm name: Arm 3" - When I click on the link labeled "Logging" +When I add an event named "Event 1" with offset of 0 days into the currently selected arm - Then I should see table header and rows containing the following values in the logging table: +Then I should see "Event 1" in the define events table + +##VERIFY_LOG +When I click on the link labeled "Logging" + +Then I should see table header and rows containing the following values in the logging table: | Username | Action | List of Data ChangesOR Fields Exported | - | test_user1 | Manage/Design | Edit arm name/number | - | test_user1 | Manage/Design | Arm 2: Arm 2 | + | test_user1 | Manage/Design | Create event (Event: Event 1, Arm: Arm 3, Days Offset: 0, Offset Range: -0/+0) | + | test_user1 | Manage/Design | Create arm (Arm 3: Arm 3) | + +#FUNCTIONAL REQUIREMENT +##ACTION - User Rename Arm in Development mode +When I click on the link labeled "Project Setup" +And I click on the button labeled "Define My Events" +And I click on the link labeled "Arm Two" +And I click on the link labeled "Rename Arm 2" +And I clear field and enter "Arm 2" into the input field labeled "Arm name" +And I click on the button labeled "Save" - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - And I click on the link labeled "Arm 2" - And I click on the Edit image for the event named "Event 1" +Then I should see "Arm name: Arm 2" - And I change the current Event Name from "Event 1" to "Event One" - And I click on the button labeled "Save" - Then I should see "Event One" +When I click on the Edit image for the event named "Event 1" +#And I change the current Event Name from "Event 1" to "Event One" +And I clear field and enter "Event One" into the input field labeled "1" +And I click on the button labeled "Save" - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: +Then I should see "Event One" + +##VERIFY_LOG +When I click on the link labeled "Logging" + +Then I should see table header and rows containing the following values in the logging table: | Username | Action | List of Data ChangesOR Fields Exported | - | test_user1 | Manage/Design | Edit event | - | test_user1 | Manage/Design | Event One, Arm: Arm 2 | - - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - And I click on the link labeled "Arm 1" - Then I should see a button labeled "Add new event" - - Given I add an event named "Event 4" with offset of 4 days into the currently selected arm - Then I should see "Event 4" in the define events table - - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: - | Username | Action | List of Data ChangesOR Fields Exported | - | test_user1 | Manage/Design | Create arm | - | test_user1 | Manage/Design | Arm 2: Arm 2 | - | test_user1 | Manage/Design | Create event | - | test_user1 | Manage/Design | Event: Event 4, Arm: Arm 1, Days Offset: 4, Offset Range: -0/+0 | - - When I click on the link labeled "Record Status Dashboard" - Then I should see "Arm 3: Arm 3" - And I should see "Arm 2: Arm 2" - - When I click on the link labeled "Arm 2" - Then I should see "Event One" - - When I click on the link labeled "Arm 1" - Then I should see "Event 4" - - Given I click on the link labeled "Project Setup" - When I click on the button labeled "Designate Instruments for My Events" - And I click on the link labeled "Arm 1" - And I click on the button labeled "Begin Editing" - And I disable the Data Collection Instrument named "Data Types" for the Event named "Event 1" - And I click on the button labeled "Save" on the Designate Instruments for My Events page - Then I verify the Data Collection Instrument named "Data Types" is disabled for the Event named "Event 1" - - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm 1" - Then I should see a Data Collection Instrument named "Consent" for the Event named "Event 1" - - - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: + | test_user1 | Manage/Design | Edit event (Event: Event One, Arm: Arm 1, Days Offset: 1, Offset Range: -0/+0 | + | test_user1 | Manage/Design | Edit arm name/number (Arm 2: Arm 2) | + +#FUNCTIONAL REQUIREMENT +##ACTION - User Adds event with days offset in development mode +Given I click on the link labeled "Project Setup" +And I click on the button labeled "Define My Events" +And I click on the link labeled "Arm 1" +And I add an event named "Event 4" with offset of 4 days into the currently selected arm +Then I should see "Event 4" in the define events table + +#VERIFY_RSD +When I click on the link labeled "Record Status Dashboard" +Then I should see "Arm 3: Arm 3" +And I should see "Arm 2: Arm 2" + +When I click on the link labeled "Arm 2" +Then I should see "Event One" + +When I click on the link labeled "Arm 1" +Then I should see "Event 4" + +#FUNCTIONAL REQUIREMENT +##ACTION - User designates instruments in development mode +Given I click on the link labeled "Project Setup" +When I click on the button labeled "Designate Instruments for My Events" +And I click on the link labeled "Arm 1" +And I click on the button labeled "Begin Editing" +And I disable the Data Collection Instrument named "Data Types" for the Event named "Event 1" +And I enable the Data Collection Instrument named "Consent" for the Event named "Event 2" +And I enable the Data Collection Instrument named "Text Validation" for the Event named "Event 4" +And I click on the button labeled "Save" on the Designate Instruments for My Events page + +Then I verify the Data Collection Instrument named "Data Types" is disabled for the Event named "Event 1" +And I verify the Data Collection Instrument named "Consent" is enabled for the Event named "Event 1" +And I verify the Data Collection Instrument named "Text Validation" is enabled for the Event named "Event 4" +And I click on the button labeled "Save" on the Designate Instruments for My Events page + +When I click on the link labeled "Arm 3" +And I click on the button labeled "Begin Editing" +And I enable the Data Collection Instrument named "Consent" for the Event named "Event 1" +And I click on the button labeled "Save" on the Designate Instruments for My Events page + +Then I verify the Data Collection Instrument named "Consent" is enabled for the Event named "Event 1" + +#VERIFY_RSD +When I click on the link labeled "Record Status Dashboard" +And I click on the link labeled "Arm 1" + +Then I should see a Data Collection Instrument named "Consent" for the Event named "Event 1" +And I should see a Data Collection Instrument named "Text Validation" for the Event named "Event 1" + +When I click on the link labeled "Arm 3" +Then I should see a Data Collection Instrument named "Consent" for the Event named "Event 1" + +##VERIFY_LOG +When I click on the link labeled "Logging" + +Then I should see table header and rows containing the following values in the logging table: | Username | Action | List of Data ChangesOR Fields Exported | | test_user1 | Manage/Design | Perform instrument-event mappings | - Given I click on the link labeled "Project Setup" - When I click on the button labeled "Designate Instruments for My Events" - And I click on the link labeled "Arm 1" - And I click on the button labeled "Begin Editing" - And I enable the Data Collection Instrument named "Consent" for the Event named "Event 2" - And I click on the button labeled "Save" on the Designate Instruments for My Events page - Then I verify the Data Collection Instrument named "Consent" is enabled for the Event named "Event 1" - - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm 1" - Then I should see a Data Collection Instrument named "Consent" for the Event named "Event 2" - - Given I click on the link labeled "Project Setup" - When I click on the button labeled "Designate Instruments for My Events" - And I click on the link labeled "Arm 1" - And I click on the button labeled "Begin Editing" - And I enable the Data Collection Instrument named "Text Validation" for the Event named "Event 4" - - And I click on the button labeled "Save" on the Designate Instruments for My Events page - Then I verify the Data Collection Instrument named "Text Validation" is enabled for the Event named "Event 4" - - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm 1" - Then I should see a Data Collection Instrument named "Text Validation" for the Event named "Event 4" - - Given I click on the link labeled "Project Setup" - When I click on the button labeled "Designate Instruments for My Events" - And I click on the link labeled "Arm 3" - When I click on the button labeled "Begin Editing" - And I enable the Data Collection Instrument named "Consent" for the Event named "Event 1" - And I click on the button labeled "Save" on the Designate Instruments for My Events page - Then I verify the Data Collection Instrument named "Consent" is enabled for the Event named "Event 1" - - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm 3" - Then I should see a Data Collection Instrument named "Consent" for the Event named "Event 1" - Given I logout - - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.600.100" - And I click on the link labeled "Project Setup" - And I click on the button labeled "Move project to production" - And I click on the radio labeled "Keep ALL data saved so far" in the dialog box - And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status - Then I should see Project status: "Production" - - When I click on the link labeled "Control Center" - And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "No, only Administrators can add/modify events in production" on the dropdown field labeled "Allow normal users to add or modify events and arms on the Define My Events page for longitudinal projects while in production status?" - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout - - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.600.100" - And I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - Then I should see "Events cannot be modified in production" - And I should NOT see a button labeled "Add new arm" - And I should NOT see a button labeled "Add new event" - - When I click on the button labeled "Upload or download arms/events" - Then I should see "Download arms (CSV)" - And I should see "Download events (CSV)" - But I should NOT see "Upload arms (CSV)" - And I should NOT see "Upload events (CSV)" - - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Designate Instruments for My Events" - And I should see "Events cannot be modified in production" - And I should NOT see a button labeled "Begin Editing" - - When I click on the button labeled "Upload or download instrument mappings" - Then I should see "Download instrument-event mappings (CSV)" - But I should NOT see "Upload instrument-event mappings (CSV)" - Given I logout - - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "Control Center" - And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "Yes, normal users can add/modify events in production" on the dropdown field labeled "Allow normal users to add or modify events and arms on the Define My Events page for longitudinal projects while in production status?" - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" - Given I logout - - Given I login to REDCap with the user "Test_User1" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.600.100" - And I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - - Given I should see a link labeled "Add New Arm" - When I click on the link labeled "Add New Arm" - And I enter "Arm 4" into the input field labeled "Arm name:" - And I click on the button labeled "Save" - Then I should see "Arm name: Arm 4" - And I click on the link labeled "Arm 4" - - Given I add an event named "Event 1" with offset of 0 days into the currently selected arm - Then I should see "Event 1" in the define events table - - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: - | Username | Action | List of Data ChangesOR Fields Exported | - | test_user1 | Manage/Design | Create arm | - | test_user1 | Manage/Design | Arm 4: Arm 4 | - | test_user1 | Manage/Design | Create event | - | test_user1 | Manage/Design | Event: Event 1, Arm: Arm 4, Days Offset: 0, Offset Range: -0/+0 | - - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - And I click on the link labeled "Arm 2" - And I click on the link labeled "Rename Arm 2" - Then I should see "Sorry, but arms can only be renamed by REDCap administrators" - And I click on the button labeled "Close" in the dialog box - Then I should see "Arm 2" - - When I click on the link labeled "Record Status Dashboard" - Then I should see a link labeled "Arm 2" - - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - And I click on the link labeled "Arm 1" - - When I click on the Edit image for the event named "Event 2" - Then I should see a dialog containing the following text: "Sorry, but events can only be renamed by REDCap administrators when a project is in production status" - And I click on the button labeled "Close" in the dialog box - - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm 1" - Then I should see "Event 2" - - Given I click on the link labeled "Project Setup" - When I click on the button labeled "Designate Instruments for My Events" - # NOTE: This is listed as Arm 1 in the manual test. "Event One" does not exist as an event in Arm 1 - so I used Arm 2. - And I click on the link labeled "Arm 2" - And I click on the button labeled "Begin Editing" - Then I should see "only REDCap administrators are allowed to uncheck any instruments that are already designated" - Then I verify the Data Collection Instrument named "Data Types" is unmodifiable for the Event named "Event One" - - When I click on the button labeled "Upload or download instrument mappings" - And I click on the link labeled "Upload instrument-event mappings (CSV)" - And I upload a "csv" format file located at "import_files/instrument_designation.csv", by clicking the button near "Select your CSV" to browse for the file, and clicking the button labeled "Upload" to upload the file - - Then I should see a dialog containing the following text: "ERROR" - And I click on the button labeled "Close" in the dialog box - - Given I click on the link labeled "Arm 1" - And I click on the button labeled "Begin Editing" - When I enable the Data Collection Instrument named "Data Types" for the Event named "Event 4" - And I click on the button labeled "Save" on the Designate Instruments for My Events page - Then I verify the Data Collection Instrument named "Data Types" is enabled for the Event named "Event 4" - - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm 1" - Then I should see a Data Collection Instrument named "Data Types" for the Event named "Event 4" - - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: - | Username | Action | List of Data ChangesOR Fields Exported | - | test_user1 | Manage/Design | Perform instrument-event mappings | +#SETUP_PRODUCTION +When I click on the link labeled "Project Setup" +And I click on the button labeled "Move project to production" +And I click on the radio labeled "Keep ALL data saved so far" in the dialog box +And I click on the button labeled "YES, Move to Production Status" in the dialog box to request a change in project status +Then I should see Project status: "Production" - Given I click on the link labeled "Project Setup" - When I click on the button labeled "Designate Instruments for My Events" - And I click on the link labeled "Arm 4" - And I click on the button labeled "Begin Editing" - And I enable the Data Collection Instrument named "Consent" for the Event named "Event 1" - And I click on the button labeled "Save" on the Designate Instruments for My Events page - Then I verify the Data Collection Instrument named "Consent" is enabled for the Event named "Event 1" - - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm 4" - Then I should see a Data Collection Instrument named "Consent" for the Event named "Event 1" - And I logout - - Given I login to REDCap with the user "Test_Admin" - When I click on the link labeled "My Projects" - And I click on the link labeled "A.6.4.600.100" - And I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - And I click on the link labeled "Arm 1" - Then I should see "Rename Arm 1" - - When I click on the link labeled "Rename Arm 1" - Then I should see a button labeled "Save" - - Given I clear field and enter "Arm One" into the input field labeled "Arm name" - And I click on the button labeled "Save" - Then I should see "Arm name: Arm One" - - When I click on the link labeled "Record Status Dashboard" - Then I should see "Arm 1: Arm One" - - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: - | Username | Action | List of Data ChangesOR Fields Exported | - | test_admin | Manage/Design | Edit arm name/number | - | test_admin | Manage/Design | Arm 1: Arm One | +#FUNCTIONAL REQUIREMENT +##ACTION - User verifies no ability to modify events +When I click on the link labeled "Project Setup" +And I click on the button labeled "Define My Events" + +Then I should see "Events cannot be modified in production" +And I should NOT see a button labeled "Add new arm" +And I should NOT see a button labeled "Add new event" + +When I click on the button labeled "Upload or download arms/events" + +Then I should see "Download arms (CSV)" +And I should see "Download events (CSV)" +And I should NOT see "Upload arms (CSV)" +And I should NOT see "Upload events (CSV)" + +When I click on the button labeled "Designate Instruments for My Events" + +Then I should see "Events cannot be modified in production" +And I should NOT see a button labeled "Begin Editing" + +When I click on the button labeled "Upload or download instrument mappings" + +Then I should see "Download instrument-event mappings (CSV)" +And I should NOT see "Upload instrument-event mappings (CSV)" + +Given I logout + +#SETUP_CONTROL_CENTER +Given I login to REDCap with the user "Test_Admin" +And I click on the link labeled "Control Center" +And I click on the link labeled "User Settings" +And I select "Yes, normal users can add/modify events in production" on the dropdown field labeled "Allow normal users to add or modify events and arms on the Define My Events page for longitudinal projects while in production status?" +And I click on the button labeled "Save Changes" + +Then I should see "Your system configuration values have now been changed!" + +Given I logout + +#FUNCTIONAL REQUIREMENT +##ACTION - User verifies has the ability to modify events + +Given I login to REDCap with the user "Test_User1" +When I click on the link labeled "My Projects" +And I click on the link labeled "A.6.4.600.100" +And I click on the link labeled "Project Setup" +And I click on the button labeled "Define My Events" + +Then I should see a link labeled "Add New Arm" +And I should see a link labeled "Add new event" - Given I click on the link labeled "Project Setup" - And I click on the button labeled "Define My Events" - And I click on the link labeled "Arm One" - And I click on the Edit image for the event named "Event 4" - And I change the current Event Name from "Event 4" to "Event Four" - And I click on the button labeled "Save" on the Designate Instruments for My Events page - Then I should see "Event Four" +When I click on the link labeled "Add New Arm" +And I enter "Arm 4" into the input field labeled "Arm name:" +And I click on the button labeled "Save" +And I add an event named "Event 1" with offset of 0 days into the currently selected arm - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm One" - Then I should see "Event Four" +Then I should see "Arm 4" +And I should see "Event 1" in the define events table - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: +##ACTION - User renames arms and events +When I click on the link labeled "Arm 2" +And I click on the link labeled "Rename Arm 2" + +Then I should see "Sorry, but arms can only be renamed by REDCap administrators" + +When I click on the button labeled "Close" in the dialog box + +Then I should see "Arm 2" + +When I click on the link labeled "Arm 2" +hen I click on the Edit image for the event named "Event 1" + +Then I should see a dialog containing the following text: "Sorry, but events can only be renamed by REDCap administrators when a project is in production status" + +When I click on the button labeled "Close" in the dialog box + +#VERIFY_RSD +When I click on the link labeled "Record Status Dashboard" +And I click on the link labeled "Arm 1" + +Then I should see a link labeled "Arm 1" +And I should see a link labeled "Event 2" +And I should see a link labeled "Arm 2" +And I should see a link labeled "Arm 4" + +##ACTION - User unable to undesignated events +When I click on the link labeled "Project Setup" +And I click on the button labeled "Define My Events" +And I click on the link labeled "Arm 1" +And I click on the button labeled "Begin Editing" + +Then I should see "only REDCap administrators are allowed to uncheck any instruments that are already designated" + +When I verify the Data Collection Instrument named "Data Types" is unmodifiable for the Event named "Event One" + +##ACTION - User unable to Upload designated instruments +When I click on the button labeled "Upload or download instrument mappings" +And I click on the link labeled "Upload instrument-event mappings (CSV)" +And I upload a "csv" format file located at "import_files/instrument_designation.csv", by clicking the button near "Select your CSV" to browse for the file, and clicking the button labeled "Upload" to upload the file + +Then I should see a dialog containing the following text: "ERROR" +And I click on the button labeled "Close" in the dialog box + + ##ACTION - User designates instruments in production mode +Given I click on the link labeled "Arm 1" +And I click on the button labeled "Begin Editing" +When I enable the Data Collection Instrument named "Data Types" for the Event named "Event 4" +And I click on the button labeled "Save" on the Designate Instruments for My Events page + +Then I verify the Data Collection Instrument named "Data Types" is enabled for the Event named "Event 4" + +##VERIFY_LOG +When I click on the link labeled "Logging" + +Then I should see table header and rows containing the following values in the logging table: | Username | Action | List of Data ChangesOR Fields Exported | - | test_admin | Manage/Design | Edit event | - | test_admin | Manage/Design | Event Four, Arm: Arm One | + | test_user1 | Manage/Design | Perform instrument-event mappings | + +Given I logout - Given I click on the link labeled "Project Setup" - When I click on the button labeled "Designate Instruments for My Events" - And I click on the link labeled "Arm 2" - And I click on the button labeled "Begin Editing" - And I disable the Data Collection Instrument named "Data Types" for the Event named "Event One" - And I click on the button labeled "Save" on the Designate Instruments for My Events page - Then I verify the Data Collection Instrument named "Data Types" is disabled for the Event named "Event One" +#FUNCTIONAL REQUIREMENT +##ACTION - Admin Renames arms and events +Given I login to REDCap with the user "Test_Admin" +And I click on the link labeled "Project Setup" +And I click on the button labeled "Define My Events" +And I click on the link labeled "Arm 1" +Then I should see "Rename Arm 1" - When I click on the link labeled "Record Status Dashboard" - And I click on the link labeled "Arm 2" - Then I should not see a Data Collection Instrument named "Data Types" for the Event named "Event One" +When I click on the link labeled "Rename Arm 1" +And I clear field and enter "Arm One" into the input field labeled "Arm name" +And I click on the button labeled "Save" +And I click on the Edit image for the event named "Event 4" +And I change the current Event Name from "Event 4" to "Event Four" +And I click on the button labeled "Save" on the Designate Instruments for My Events page - When I click on the link labeled "Logging" - Then I should see table header and rows containing the following values in the logging table: +Then I should see "Arm name: Arm One" +And I should see "Event Four" + +##VERIFY_LOG +When I click on the link labeled "Logging" + +Then I should see table header and rows containing the following values in the logging table: | Username | Action | List of Data ChangesOR Fields Exported | - | test_admin | Manage/Design | Perform instrument-event mappings | - - When I click on the link labeled "Control Center" - And I click on the link labeled "User Settings" - Then I should see "System-level User Settings" - When I select "No, only Administrators can add/modify events in production" on the dropdown field labeled "Allow normal users to add or modify events and arms on the Define My Events page for longitudinal projects while in production status?" - And I click on the button labeled "Save Changes" - Then I should see "Your system configuration values have now been changed!" + | test_admin | Manage/Design | Edit event | + | test_admin | Manage/Design | Event Four, Arm: Arm One | + | test_admin | Manage/Design | Edit arm name/number | + | test_admin | Manage/Design | Arm 1: Arm One | From 8164642555114258dd2b88ad68f0355bf9125c38 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 19:36:05 -0400 Subject: [PATCH 46/96] Update A.6.4.700 - Blank Slate Projects.feature fix heading --- .../Project Setup/A.6.4.700 - Blank Slate Projects.feature | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.700 - Blank Slate Projects.feature b/Feature Tests/A/Project Setup/A.6.4.700 - Blank Slate Projects.feature index 5e3be9b5..7f88c7ca 100644 --- a/Feature Tests/A/Project Setup/A.6.4.700 - Blank Slate Projects.feature +++ b/Feature Tests/A/Project Setup/A.6.4.700 - Blank Slate Projects.feature @@ -1,7 +1,7 @@ -Feature: A.6.4.700 Manage project creation, deletion, and settings +Feature: A.6.4.700 Manage project creation, deletion, and settings. User Interface General: The system shall support the ability to create new projects from a blank slate. - Manage project creation, deletion, and settings - User Interface General: The system shall support the ability to create new projects from a blank slate. +As a REDCap end user + I want to see that create project is functioning as expected Scenario: A.6.4.700.100 Create blank new project Given I login to REDCap with the user "Test_User1" From e699e8b41c6604c094afb86809d2ccbc4b658d40 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 19:36:50 -0400 Subject: [PATCH 47/96] Update A.6.4.400 - Draft Mode.feature --- .../A/Project Setup/A.6.4.400 - Draft Mode.feature | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature b/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature index a8f55783..ee11456f 100644 --- a/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature +++ b/Feature Tests/A/Project Setup/A.6.4.400 - Draft Mode.feature @@ -1,7 +1,7 @@ -Feature: A.6.4.400 Manage project creation, deletion, and settings +Feature: A.6.4.400 Manage project creation, deletion, and settings. Control Center: The system shall allow production Draft Mode changes to be approved automatically under certain conditions. - Manage project creation, deletion, and settings - Control Center: The system shall allow production Draft Mode changes to be approved automatically under certain conditions. +As a REDCap end user + I want to see that manage project functions is functioning as expected Scenario: A.6.4.400.100 User's ability to approve draft changes without administrative approval From 99e474d0cce9f47b7a69697459370ad59ee2cc57 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 3 Nov 2023 19:37:26 -0400 Subject: [PATCH 48/96] Update A.6.4.100 - User Create Projects.feature --- .../A.6.4.100 - User Create Projects.feature | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature b/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature index 15d6208f..0f504bbd 100644 --- a/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature +++ b/Feature Tests/A/Project Setup/A.6.4.100 - User Create Projects.feature @@ -1,8 +1,8 @@ -Feature: A.6.4.100 Manage project creation, deletion, and settings - - Manage project creation, deletion, and settings - Control Center: The system shall support the option to limit the creation of new projects to administrators. +Feature: A.6.4.100 Manage project creation, deletion, and settings. Control Center: The system shall support the option to limit the creation of new projects to administrators. +As a REDCap end user +I want to see that manage project functions is functioning as expected + Scenario: A.6.4.100.100 User's ability to create new projects #SETUP_CONTROL_CENTER Given I login to REDCap with the user "Test_Admin" From c44c6df1b2a1894a2b4edc11582129626feead9f Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Tue, 14 Nov 2023 12:07:58 -0500 Subject: [PATCH 49/96] Update A.2.2.400 - Delete.feature fix the duplicate line --- Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature index 03501789..ec811b7e 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature @@ -9,7 +9,6 @@ Feature: A.2.2.400 Add/Manage users Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Control Center" And I click on the link labeled "Browse Users" - And I click on the link labeled "Browse Users" Then I should see "User Search: Search for user by username, first name, last name, or primary email" ##ACTION_MANUAL_TESTING: Verify Delete_User is already created. If Delete_User is not created, skip to line 22. @@ -17,7 +16,7 @@ Then I should see "User Search: Search for user by username, first name, last na # And I click on the button labeled "Search" #Then I should see "Delete_User" -#Manual skip to Functional Requirement test (Line 40) +#Manual skip to Functional Requirement test (Line 40: ##ACTION Cancel delete user ) ##ACTION_AUTOMATED_TESTING: Create Delete_User When I click on the link labeled "Add Users (Table-based Only)" Then I should see "Create single user" From c8a7f4f850ebb73b5d00db433b26bb2c840e02f8 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Tue, 14 Nov 2023 12:11:52 -0500 Subject: [PATCH 50/96] Update A.2.2.400 - Delete.feature add instructions. --- Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature index ec811b7e..b337545a 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature @@ -11,7 +11,7 @@ Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Browse Users" Then I should see "User Search: Search for user by username, first name, last name, or primary email" -##ACTION_MANUAL_TESTING: Verify Delete_User is already created. If Delete_User is not created, skip to line 22. +##ACTION_MANUAL_TESTING: Verify Delete_User is already created. If Delete_User is not created, skip to Create Delete_User (Line 20). #When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" # And I click on the button labeled "Search" #Then I should see "Delete_User" From 46dace52a8be87b1022457ba33d9b7ca4b336031 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Tue, 14 Nov 2023 12:13:02 -0500 Subject: [PATCH 51/96] Update A.2.2.400 - Delete.feature --- .../A/Add Manage Users/A.2.2.400 - Delete.feature | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature index b337545a..7f0c4ad8 100644 --- a/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature +++ b/Feature Tests/A/Add Manage Users/A.2.2.400 - Delete.feature @@ -11,12 +11,13 @@ Given I login to REDCap with the user "Test_Admin" And I click on the link labeled "Browse Users" Then I should see "User Search: Search for user by username, first name, last name, or primary email" -##ACTION_MANUAL_TESTING: Verify Delete_User is already created. If Delete_User is not created, skip to Create Delete_User (Line 20). +##ACTION_MANUAL_TESTING: Verify Delete_User is already created. If Delete_User is not created, skip to Create Delete_User (Line 21). #When I enter "Delete_User" into the input field labeled "User Search: Search for user by username, first name, last name, or primary email" # And I click on the button labeled "Search" -#Then I should see "Delete_User" - -#Manual skip to Functional Requirement test (Line 40: ##ACTION Cancel delete user ) +#Then I should see "Delete_User" +# And I should see "Editable user attributes" + +#Manual skip to Functional Requirement test (Line 41: ##ACTION Cancel delete user ) ##ACTION_AUTOMATED_TESTING: Create Delete_User When I click on the link labeled "Add Users (Table-based Only)" Then I should see "Create single user" From f99189607aa93d5bacd99119022ea8ac8c510760 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 29 Nov 2023 19:21:45 -0500 Subject: [PATCH 52/96] Update B.2.6.100 - Basic Privileges.feature --- .../B/Assign User Rights/B.2.6.100 - Basic Privileges.feature | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature b/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature index 8fac6949..57be1745 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.100 - Basic Privileges.feature @@ -216,3 +216,5 @@ And I logout ##VERIFY: Verify User has no access to project Given I login to REDCap with the user "Test_User1" +Then I should see "My Projects" +And I should NOT see "B.2.6.100.100" From 559d49bb79085bdeb407e9926f686d949e17e9e5 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 6 Dec 2023 19:48:13 -0500 Subject: [PATCH 53/96] Update B.3.16.1000 - Access Restrictions.feature add logging --- .../B/Data Import/B.3.16.1000 - Access Restrictions.feature | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Feature Tests/B/Data Import/B.3.16.1000 - Access Restrictions.feature b/Feature Tests/B/Data Import/B.3.16.1000 - Access Restrictions.feature index 3aac9471..05b5aa47 100644 --- a/Feature Tests/B/Data Import/B.3.16.1000 - Access Restrictions.feature +++ b/Feature Tests/B/Data Import/B.3.16.1000 - Access Restrictions.feature @@ -62,3 +62,9 @@ When I click on the button labeled "View Report" Then I should see a table header and rows including the following values in the report data table: | Record ID| Email | | 5 | email@test.edu| + +#VERIFY_LOG +When I click on the button labeled "Logging" +Then I should see a table header and rows including the following values in the logging table: +| Username | Action | List of Data Changes OR Fields Exported | +| test_admin| Create record (import) | Create record (import) From 970744eca969b1a203016c9041a526c7eacc5500 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 6 Dec 2023 19:51:28 -0500 Subject: [PATCH 54/96] Update B.2.6.300 - Data Export Rights.feature Line 15 needs to be reworded; Line 147 - should say "Then I should not see the button labeled "Export Data" --- .../Assign User Rights/B.2.6.300 - Data Export Rights.feature | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature b/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature index be61d834..9e1a3ae4 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.300 - Data Export Rights.feature @@ -12,7 +12,7 @@ When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box -Then I see "Project status: Production" +Then I should see "Project status: Production" ##USER_RIGHTS When I click on the link labeled "User Rights" @@ -144,4 +144,4 @@ And I click on the link labeled "B.2.6.300.100" ##ACTION: And I click on the link labeled "Data Exports, Reports, and Stats" ##VERIFY -Then I should NOT see "Export Data" +Then I should not see the button labeled "Export Data" From 886f2714f33aa6a07ed6c8fd10996867d5a024b9 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 6 Dec 2023 20:25:23 -0500 Subject: [PATCH 55/96] Update B.6.4.900 - Project Purpose.feature --- .../B/Project Setup/B.6.4.900 - Project Purpose.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Feature Tests/B/Project Setup/B.6.4.900 - Project Purpose.feature b/Feature Tests/B/Project Setup/B.6.4.900 - Project Purpose.feature index 192db2c2..03a3823f 100644 --- a/Feature Tests/B/Project Setup/B.6.4.900 - Project Purpose.feature +++ b/Feature Tests/B/Project Setup/B.6.4.900 - Project Purpose.feature @@ -24,7 +24,7 @@ Then I should see a table header and rows including the following values in the | test_user1 | Manage/Design | Modify project settings | ##ACTION #CROSS-FEATURE B.2.23.100: Verify Logging Filter by event manage/design -When I select the dropdown option labeled "Manage/Design" from the dropdown field labeled "Filter by event:" with the placeholder text of ""All event types" +When I select the dropdown option labeled "Manage/Design" from the dropdown field labeled "Filter by event:" with the placeholder text of "All event types" ##VERIFY_LOG #CROSS-FEATURE: Verify Logging Filter by event manage/design Then I should see a table header and rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | From 7701abf293705c781057fae6e4eb2a7c6ea6c9f9 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 6 Dec 2023 20:45:04 -0500 Subject: [PATCH 56/96] Update B.3.14.100 - Create Record.feature --- .../B.3.14.100 - Create Record.feature | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create Record.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create Record.feature index 4ddb4d07..dc18bb96 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create Record.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.100 - Create Record.feature @@ -27,7 +27,7 @@ Then I should see "Test User1" ##ACTION: create record When I click the link labeled "Add/Edit Records" And I click the button labeled "Add new record for the arm selected above" -And I click the bubble labeled "Text Validation for event "Event 1" +And I click the bubble labeled "Text Validation" for event "Event 1" And I click the button labeled "Save and Exit Form" ##VERIFY Then I should see "Record ID 7 successfully added" @@ -66,8 +66,8 @@ Then I should NOT see the button labeled "Add new record for the arm selected ab ##VERIFY Can edit existing record When I click on the dropdown field with the placeholder text of "select record" And I select the dropdown option labeled "1" -And I click the bubble labeled "Text Validation for event "Event 1" -And I enter "Edit" on the field labeled "Name" +And I click the bubble labeled "Text Validation" for event "Event 1" +And I enter "EDIT" on the field labeled "Name" And I click on the button labeled "Save & Exit Form" Then I should see "Record ID 1 successfully edited" From 372a7de504cda6167bd5f052ee622f4a97c24720 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 6 Dec 2023 22:09:02 -0500 Subject: [PATCH 57/96] Update B.3.14.600 - Save Options.feature --- .../B.3.14.600 - Save Options.feature | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save Options.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save Options.feature index fb5d6a79..41b12465 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save Options.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.600 - Save Options.feature @@ -32,6 +32,11 @@ Then I should see "Record ID 7" data entry cancelled - not saved." ##VERIFY_LOG When I click on the link labeled "Logging" +Then I should NOT see table rows including the following values in the logging table: +| Username | Action | List of Data Changes +OR Fields Exported | +| test_user1 | Manage/Design | Move project to Production status | + Then I should NOT see table rows including the following values in the logging table: | Username | Action | | test_user1 | Create record 7 | @@ -105,6 +110,7 @@ Then I should see "Now displaying the next record: Record ID 11" When I click on the link labeled "Logging" Then I should see table rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | +| test_user1 | Update record 11 | name = 'NEXT RECORD '| | test_user1 | Update record 10 | name = 'SAVE & GO TO NEXT RECORD '| | test_user1 | Create record 9 | name = 'SAVE & EXIT RECORD' | | test_user1 | Create record 8 | name = 'SAVE & GO TO NEXT FORM' | @@ -122,3 +128,4 @@ Then I should see a table header and rows including the following values in the | 8 | Event 1 (Arm 1: Arm 1) | SAVE & GO TO NEXT FORM| | 9 | Event 1 (Arm 1: Arm 1) | SAVE AND EXIT RECORD| | 10 | Event 1 (Arm 1: Arm 1) | SAVE & GO TO NEXT RECORD| +| 11 | Event 1 (Arm 1: Arm 1) | NEXT RECORD| From 5606d37a4c732f6b0b842db453a8b8ade89a8392 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 6 Dec 2023 22:24:07 -0500 Subject: [PATCH 58/96] Update B.3.14.1100 - Delete Record Data.feature --- .../B.3.14.1100 - Delete Record Data.feature | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 - Delete Record Data.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 - Delete Record Data.feature index 95e52392..ca9c72f6 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 - Delete Record Data.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.1100 - Delete Record Data.feature @@ -40,8 +40,7 @@ When I click on the link labeled "Logging" Then I should see table rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported| | test_user1 | Update record 1 | calc_test = ''| -| test_user1 | Update record 1 |calculated_field = '' | -| test_user1 | Update record 1 |calculated_field_2 = ''| +| test_user1 | Update record 1 |consent_complete = '' | | test_user1 | Update record 1 |data_types_complete = '' | | test_user1 | Update record 1 |dob = '' | | test_user1 | Update record 1 |email = '' | @@ -55,5 +54,6 @@ Then I should see a table row containing the following values in the reports tab | A | All data (all records and fields) | When I click on the button labeled "View Report" -Then I should NOT see data for event "Event 1" for record "1" - +Then I should NOT see a table row including the following values in in the logging table: +| record_id | redcap_event_name | name | +| 1 | Event 1 (Arm 1: Arm 1) | Name | From e6ef17d0b5c9dcb5d47b7080e237e7c9570803d0 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 20 Dec 2023 12:40:44 -0500 Subject: [PATCH 59/96] Create B.6.7.1100 - Field Radio new --- .../Online Designer/B.6.7.1100 - Field Radio | 77 +++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 Feature Tests/B/Online Designer/B.6.7.1100 - Field Radio diff --git a/Feature Tests/B/Online Designer/B.6.7.1100 - Field Radio b/Feature Tests/B/Online Designer/B.6.7.1100 - Field Radio new file mode 100644 index 00000000..7a688105 --- /dev/null +++ b/Feature Tests/B/Online Designer/B.6.7.1100 - Field Radio @@ -0,0 +1,77 @@ +Feature: Field Creation: The system shall support the creation and manual coding for multiple choice radio buttons (single answer). + +As a REDCap end user +I want to see that Project Designer is functioning as expected + +Scenario: B.6.7.1100.100 Creation of multiple choice radio buttons (single answer) through the Online Designer + +#SETUP +Given I login to REDCap with the user "Test_Admin" +And I create a new project named "B.6.7.1100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button + +##SETUP_PRODUCTION +When I click on the link labeled "My Projects" +And I click on the link labeled "B.6.7.1100.100" +When I click on the button labeled "Project Setup" +And I click on the button labeled "Move project to production" +And I click on the radio button labeled "Keep ALL data saved so far" in the dialog box +And I click on the button labeled "YES, Move to Production Status" in the dialog box +Then I should see "Project Status: Production" + +When I click on the link labeled "Designer" +And I click on the button labeled "Enter Draft Mode" +Then I should see "The project is now in Draft Mode" + +#FUNCTIONAL_REQUIREMENT +##ACTION: Radio field creation +Given When I click on the instrument labeled "Form 1" +And I click on the button labeled "Add Field" at the bottom of the instrument +And I click on the dropdown field labeled "Select a Type of Field" +And I add a new Multiple Choice - Radio Buttons (Single Answer) field labeled "Radio Button Manual" with the variable name "radio_button_manual" +And I enter "9..9, Choice99" on the first row of the input field labeled "Choices (one choice per line)" +And I enter "100, Choice100" on the second row of the input field labeled "Choices (one choice per line)" +And I enter "101, Choice101" on the third row of the input field labeled "Choices (one choice per line)" +And I enter "Abc123, Choice Abc123" on the fourth row of the input field labeled "Choices (one choice per line)" +And I click on the button labeled "Save" +Then I should see the field labeled "Radio Button Manual" +And I should see the radio button options "Choice99","Choice100", "Choice101, Choice ABc123" + +##SETUP_PRODUCTION +When I click on the button labeled "Submit Changes for Review" +And I click on the button labeled "Submit" in the dialog box +Then I should see "Changes Were Made Automatically" +When I click on the button labeled "Close" in the dialog box + +##VERIFY_CODEBOOK +When I click on the link labeled "Codebook" +Then I should see a table row containing the following values in the codebook table: +| [radio_button_manual] | Radio Button Manual | radio | + +##VERIFY_LOG +When I click on the link labeled "Logging" +Then I should see a table header and rows including the following values in the logging table: +| Username | Action | List of Data Changes OR Fields Exported | +| test_admin | Manage/Design | Create project field | + +Scenario: B.6.7.1100.200 Creation of multiple choice radio buttons (single answer) through Data Dictionary upload (#CROSSFUNCTIONAL - B.6.7.100.100) + +#SETUP +Given I login to REDCap with the user "Test_Admin" +And I create a new project named "B.6.7.1100.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button + +#FUNCTIONAL_REQUIREMENT +##ACTION: Upload data dictionary +When I click on the link labeled "Dictionary" +And I click on the button labeled "Choose File" +And I select the file labeled "Project1xml_DataDictionary.csv" +And I click on the button labeled "Upload File" +Then I should see "Your document was uploaded successfully and awaits your confirmation below." + +When I click on the button labeled "Commit Changes" +Then I should see "Changes Made Successfully!" + +##VERIFY_CODEBOOK +When I click on the link labeled "Codebook" +Then I should see a table row containing the following values in the codebook table: +| [radio_button_manual] | Radio Button Manual | radio | + From 9678ae4efbef703f3ef6074cc1ac391883f69544 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 20 Dec 2023 12:41:07 -0500 Subject: [PATCH 60/96] Rename B.6.7.1100 - Field Radio to B.6.7.1100 - Field Radio.feature --- ...{B.6.7.1100 - Field Radio => B.6.7.1100 - Field Radio.feature} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Feature Tests/B/Online Designer/{B.6.7.1100 - Field Radio => B.6.7.1100 - Field Radio.feature} (100%) diff --git a/Feature Tests/B/Online Designer/B.6.7.1100 - Field Radio b/Feature Tests/B/Online Designer/B.6.7.1100 - Field Radio.feature similarity index 100% rename from Feature Tests/B/Online Designer/B.6.7.1100 - Field Radio rename to Feature Tests/B/Online Designer/B.6.7.1100 - Field Radio.feature From f581175040ee7eba64cd696edaa0eb8c5dcb2e72 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 27 Dec 2023 14:20:16 -0500 Subject: [PATCH 61/96] Update B.6.7.500 - Delete Instrument.feature --- .../B.6.7.500 - Delete Instrument.feature | 43 ------------------- 1 file changed, 43 deletions(-) diff --git a/Feature Tests/B/Online Designer/B.6.7.500 - Delete Instrument.feature b/Feature Tests/B/Online Designer/B.6.7.500 - Delete Instrument.feature index 1a4fbd03..fb7827b1 100644 --- a/Feature Tests/B/Online Designer/B.6.7.500 - Delete Instrument.feature +++ b/Feature Tests/B/Online Designer/B.6.7.500 - Delete Instrument.feature @@ -45,47 +45,4 @@ Then I should see a table header and rows including the following values in the Scenario: B.6.7.500.200 Delete instrument from Data Dictionary #REDUNDANT #B.6.7.100.100 -B.6.7.600 -Design forms Using Data Dictionary and Online Designer -Form Creation: The system shall support the ability to re-order data collection instruments. -As a REDCap end user -I want to see that Project Designer is functioning as expected - -Scenario: B.6.7.600.100 Reorder instrument from online designer - -#SETUP -Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.7.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - -When I click on the link labeled "My Projects" -And I click on the link labeled "B.6.7.600.100" - -##SETUP_PRODUCTION -When I click on the button labeled "Project Setup" -And I click on the button labeled "Move project to production" -And I click on the radio labeled "Keep ALL data saved so far" in the dialog box -And I click on the button labeled "YES, Move to Production Status" in the dialog box -Then I should see "Project Status: Production" - -When I click on the link labeled "Designer" -And I click on the button labeled "Enter Draft Mode" -Then I should see "The project is now in Draft Mode" - -#FUNCTIONAL_REQUIREMENT -##ACTION -When I drag on the instrument labeled "Data Types" to position 0 -#The item below always passes when Saved! is hidden -Then I should see "Saved!" -And I should see the instrument labeled "Data Types" in position 0 - -When I click on the button labeled "Submit Changes for Review" -And I click on the button labeled "Submit" in the dialog box -Then I should see "Changes Were Made Automatically" -And I click on the button labeled "Close" in the dialog box - -#VERIFY_LOG -When I click on the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin| Manage/Design | Reorder data collection instruments | From a63e67ad264f91cc8319f6208c04214e4cd6e85f Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 27 Dec 2023 14:34:16 -0500 Subject: [PATCH 62/96] Update B.6.7.1500 - Field Descriptive Text.feature Line 28 - Given --- .../Online Designer/B.6.7.1500 - Field Descriptive Text.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Feature Tests/B/Online Designer/B.6.7.1500 - Field Descriptive Text.feature b/Feature Tests/B/Online Designer/B.6.7.1500 - Field Descriptive Text.feature index 0ea2838c..54875693 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1500 - Field Descriptive Text.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1500 - Field Descriptive Text.feature @@ -25,7 +25,7 @@ Then I should see "The project is now in Draft Mode" #FUNCTIONAL_REQUIREMENT ##ACTION: Signature field creation -Given When I click on the instrument labeled "Form 1" +Given I click on the instrument labeled "Form 1" And I click on the button labeled "Add Field" at the bottom of the instrument When I click on the dropdown field labeled "Select a Type of Field" And I add a new Descriptive Text (with optional Image/Video/Audio/File Attachment) labeled "Descriptive Text with File" with the variable name "descriptive_text_file" From 1a1290989a0dcb3c9f3bc1e8433756bb0a4f809f Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 27 Dec 2023 14:34:44 -0500 Subject: [PATCH 63/96] Update B.6.7.1900 - Field Management.feature Line 136: Should say "including" not "containing" --- .../B/Online Designer/B.6.7.1900 - Field Management.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Feature Tests/B/Online Designer/B.6.7.1900 - Field Management.feature b/Feature Tests/B/Online Designer/B.6.7.1900 - Field Management.feature index c8674baa..31c47b87 100644 --- a/Feature Tests/B/Online Designer/B.6.7.1900 - Field Management.feature +++ b/Feature Tests/B/Online Designer/B.6.7.1900 - Field Management.feature @@ -133,7 +133,7 @@ Then I should see "Project Changes Committed/User Notified" ##VERIFY_CODEBOOK When I click on the link labeled "Codebook" -Then I should see a table row containing the following values in the codebook table: +Then I should see a table row including the following values in the codebook table: | Variable / Field Name |Field Label |Field Attributes (Field Type, Validation, Choices, Calculations, etc.) | | [add] | Add Field | text | | [radio_button_manual]| Radio Button Manual| Choice Abc123| From e60e45a3f04d01dc467664821e936c233dd4d8b5 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 27 Dec 2023 14:38:45 -0500 Subject: [PATCH 64/96] Update C.3.24.200 - eConsent footer.feature Add note about today --- .../C/e-Consent framework/C.3.24.200 - eConsent footer.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Feature Tests/C/e-Consent framework/C.3.24.200 - eConsent footer.feature b/Feature Tests/C/e-Consent framework/C.3.24.200 - eConsent footer.feature index abb0d72e..f13723e3 100644 --- a/Feature Tests/C/e-Consent framework/C.3.24.200 - eConsent footer.feature +++ b/Feature Tests/C/e-Consent framework/C.3.24.200 - eConsent footer.feature @@ -46,7 +46,7 @@ Then I should see "Consent" And I verify I see "Name" in the field labeled "1) Name" And I verify I see "Name" in the field labeled "2) Name" And I verify I see "email@test.edu" in the field labeled "3) Email" -And I verify I see "2023-09-03" in the field labeled "4) DOB" +And I verify I see "2023-12-18" in the field labeled "4) DOB" #Date will be today's date. And I enter a signature in the field labeled "5) Signature" And I verify I see "signature_consent_2" in the field labeled "6) Signature" And I verify I see "signature_consent_3" in the field labeled "7) Signature" From 6587606d4eebd420c4613fcb2f453a053b5094ca Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 27 Dec 2023 15:11:33 -0500 Subject: [PATCH 65/96] Update B.2.10.400 - User and Record Restrictions.feature B.2.10.400 --- ....2.10.400 - User and Record Restrictions.feature | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/Feature Tests/B/Data Access Groups/B.2.10.400 - User and Record Restrictions.feature b/Feature Tests/B/Data Access Groups/B.2.10.400 - User and Record Restrictions.feature index 7d94f94f..497ee3d8 100644 --- a/Feature Tests/B/Data Access Groups/B.2.10.400 - User and Record Restrictions.feature +++ b/Feature Tests/B/Data Access Groups/B.2.10.400 - User and Record Restrictions.feature @@ -5,7 +5,7 @@ I want to see that Data Access Groups is functioning as expected Scenario: B.2.10.400.100 User restriction for records in DAGs -#SETUP_NOTE: Will reference unique Group ID numbers located on DAG page. These numbers are specific the PID +#SETUP_NOTE: Will reference unique Group ID numbers located on DAG page. These numbers are specific to the PID #SETUP Given I login to REDCap with the user "Test_Admin" @@ -65,7 +65,7 @@ Then I should see a dialog containing the following text: "Editing existing user ##ACTION: Set user access to View & Edit + Edit survey responses When I set Data Viewing Rights to View & Edit for the instrument "Text Validation" And I set Data Viewing Rights to View & Edit with Edit survey responses checked for the instrument "Consent" - And I save changes within the context of User Rights +And I save changes within the context of User Rights #ASSIGN RECORDS TO SPECIFIC DAGs # -- Record ID 3 - TestGroup1 -- @@ -194,7 +194,8 @@ Then I should see a table header and rows containing the following values in the When I click on the link labeled "Record Status Dashboard" Then I should see a table header and rows containing the following values in the record status dashboard table: | Record ID | -| 3 TestGroup1 | +| 3 | +| 1-1 | ##VERIFY_FR: When I click on the link labeled "File Repository" @@ -262,12 +263,8 @@ Then I should see "Thank you for taking the survey." When I click on the button labeled "Close survey" Then I should see "You may now close this tab/window" -Given I am still logged in to REDCap with the user "Test_User4" -When I click on the link labeled "My Projects" -And I click on the link labeled "B.2.10.400.100" - ##VERIFY_RSD: -And I click on the link labeled "Record Status Dashboard" +When I click on the link labeled "Record Status Dashboard" Then I should see a table header and rows containing the following values in the record status dashboard table: | Record ID | | 2-1 TestGroup2 | From fef5ea0e337828802a893a8fe95cbea4f7bcedb7 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 27 Dec 2023 15:45:56 -0500 Subject: [PATCH 66/96] Update B.3.14.400 - Datetime Fields.feature B.3.14.400.100 - Add verification --- .../B.3.14.400 - Datetime Fields.feature | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Datetime Fields.feature b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Datetime Fields.feature index 5e7a011f..3d1f922b 100644 --- a/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Datetime Fields.feature +++ b/Feature Tests/B/Direct Data Entry - Data Collection Instrument/B.3.14.400 - Datetime Fields.feature @@ -38,4 +38,13 @@ When I click on the button labeled "Today" for the field labeled "date YMD" ##VERIFY Then I should see today's date in the field labeled "date YMD" +When I select the submit option labeled "Save & Exit Form" on the Data Collection Instrument +Then I should see "Adding new Record ID 7." +##VERIFY_LOG +When I click on the link labeled "Logging" +Then I should see a table header and rows including the following values in the logging table: +| Username | Action | List of Data Changes OR Fields Exported | +| test_admin | Create record 7 | date_ymd = '2023-12-27',| +| test_admin | Create record 7 | time_hhmmss = '15:33:55',| +| test_admin | Create record 7 | datetime_ymd_hmss = '2023-08-01 00:00:00',| From 3058e7eb7a070a756af4b869634e8fee0c9a5d74 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 13:13:46 -0500 Subject: [PATCH 67/96] Update B.2.10.600 - Unique DAGs.feature Scenario: B.2.10.600.100 Unique DAGs Contains ##REDUNDANT #B.2.10.500 Assign Records to a DAG --- .../B/Data Access Groups/B.2.10.600 - Unique DAGs.feature | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature b/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature index 8d50f309..ac87dc69 100644 --- a/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature +++ b/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature @@ -14,7 +14,8 @@ And I click on the link labeled "3" Then I should see the "Record Home Page" #FUNCTIONAL REQUIREMENT -##ACTION: Assign Record DAG_testgroup1 +##ACTION: Assign Record DAG_testgroup1 +##REDUNDANT #B.2.10.500 Assign Records to a DAG When I select the dropdown option labeled "Assign to Data Access Group" from the dropdown "Choose action for record" And I select the dropdown option labeled "TestGroup1" from the dropdown with the placeholder text of "[No Assignment]" in the dialog box And I click on the button labeled "Assign to Data Access Group" in the dialog box From 66cf549202429283d68d63cb66e6c9c9f63cd8dc Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 13:16:12 -0500 Subject: [PATCH 68/96] Update and rename B.2.10.500 - Assign Records to DAG.feature to B.2.10.500 - REDUNDANT.Assign Records to DAG.feature Scenario: B.2.10.500.100 Assign DAG to record This feature test is REDUNDANT and can be viewed in B.2.10.600. --- ...B.2.10.500 - Assign Records to DAG.feature | 28 ------------------- ... - REDUNDANT.Assign Records to DAG.feature | 3 ++ 2 files changed, 3 insertions(+), 28 deletions(-) delete mode 100644 Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature create mode 100644 Feature Tests/B/Data Access Groups/B.2.10.500 - REDUNDANT.Assign Records to DAG.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature b/Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature deleted file mode 100644 index 7494d464..00000000 --- a/Feature Tests/B/Data Access Groups/B.2.10.500 - Assign Records to DAG.feature +++ /dev/null @@ -1,28 +0,0 @@ -Feature: User Interface: The system shall provide the ability to assign records to a DAG from the Record Home page - -As a REDCap end user -I want to see that Data Access Groups is functioning as expected - -Scenario: B.2.10.500.100 Assign DAG to record -#SETUP -Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.10.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - -When I click on the link labeled "Record Status Dashboard" -And I click on the link labeled "2" -Then I should see the "Record Home Page" - -#FUNCTIONAL REQUIREMENT -##ACTION: Assign Record DAG -When I select the dropdown option labeled "Assign to Data Access Group" from the dropdown "Choose action for record" -And I select the dropdown option labeled "TestGroup1" from the dropdown with the placeholder text of "[No Assignment]" in the dialog box -And I click on the button labeled "Assign to Data Access Group" in the dialog box - -##VERIFY -Then I should see "Record ID 2 was successfully assigned to a Data Access Group!" -And I should see "Arm 1: Arm 1 - TestGroup1" -##VERIFY_LOG -When I click on the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin | Update record 2 | Assign record to Data Access Group (redcap_data_access_group = 'testgroup1') | diff --git a/Feature Tests/B/Data Access Groups/B.2.10.500 - REDUNDANT.Assign Records to DAG.feature b/Feature Tests/B/Data Access Groups/B.2.10.500 - REDUNDANT.Assign Records to DAG.feature new file mode 100644 index 00000000..e4b29a96 --- /dev/null +++ b/Feature Tests/B/Data Access Groups/B.2.10.500 - REDUNDANT.Assign Records to DAG.feature @@ -0,0 +1,3 @@ +Feature: User Interface: The system shall provide the ability to assign records to a DAG from the Record Home page +Scenario: B.2.10.500.100 Assign DAG to record +This feature test is REDUNDANT and can be viewed in B.2.10.600. From 3f07ec8745e9435cd7097a07d1695d1c042b059e Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 13:54:57 -0500 Subject: [PATCH 69/96] Update C.3.24.600 - eConsent edit.feature C.3.24.600.100 Enable/disable edit ability for e-Consent framework --- .../e-Consent framework/C.3.24.600 - eConsent edit.feature | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/Feature Tests/C/e-Consent framework/C.3.24.600 - eConsent edit.feature b/Feature Tests/C/e-Consent framework/C.3.24.600 - eConsent edit.feature index 0c7ef28b..916d3967 100644 --- a/Feature Tests/C/e-Consent framework/C.3.24.600 - eConsent edit.feature +++ b/Feature Tests/C/e-Consent framework/C.3.24.600 - eConsent edit.feature @@ -7,7 +7,7 @@ Scenario: C.3.24.600.100 Enable/disable edit ability for e-Consent framework #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named " C.3.24.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button +And I create a new project named "C.3.24.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button #SETUP_PRODUCTION When I click on the button labeled "Project Setup" @@ -55,7 +55,7 @@ Then I should see "1 File" for the field labeled "PDF Survey Archive" When I click on the link labeled "PDF Survey Archive" And I click on the link on the PDF link for record "5" Then I should have a pdf file with the following values in the report: "1) Name" is "Consent Name" -#M: Close document +#Manual: Close document ##ACTION: edit survey response When I click on the link labeled "Record Status Dashboard" @@ -80,7 +80,7 @@ Then I should see "1 File" for the field labeled "PDF Survey Archive" When I click on the link labeled "PDF Survey Archive" And I click on the link on the PDF link for record "5" Then I should have a pdf file with the following values in the report: I should NOT see "1) Name" is "Consent 2 Name" -#M: Close document +#Manual: Close document ##ACTION: disable e-consent survey settings - auto-archive and e-consent When I click on the link labeled "Designer" @@ -99,4 +99,3 @@ When I click on the link labeled "Logging" Then I should see a table header and rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | | test_admin | Manage/Design | Modify survey info | - From ebb1b5d0dce97beb8750f233d3e30eee85d9b120 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 13:56:55 -0500 Subject: [PATCH 70/96] Rename C.3.24.700 - eConsent.feature to C.3.24.700 - REDUNDANT.feature This feature test is REDUNDANT and can be viewed in C.3.24.200.100 --- ...24.700 - eConsent.feature => C.3.24.700 - REDUNDANT.feature} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename Feature Tests/C/e-Consent framework/{C.3.24.700 - eConsent.feature => C.3.24.700 - REDUNDANT.feature} (98%) diff --git a/Feature Tests/C/e-Consent framework/C.3.24.700 - eConsent.feature b/Feature Tests/C/e-Consent framework/C.3.24.700 - REDUNDANT.feature similarity index 98% rename from Feature Tests/C/e-Consent framework/C.3.24.700 - eConsent.feature rename to Feature Tests/C/e-Consent framework/C.3.24.700 - REDUNDANT.feature index 6b93a586..dc853d97 100644 --- a/Feature Tests/C/e-Consent framework/C.3.24.700 - eConsent.feature +++ b/Feature Tests/C/e-Consent framework/C.3.24.700 - REDUNDANT.feature @@ -1,3 +1,3 @@ Feature: User Interface: The e-Consent framework shall support a certification page at the end of the survey that displays an in-line PDF copy of their survey responses. -This feature test is REDUNDANT and can be viewed in C.3.24.200.100 \ No newline at end of file +This feature test is REDUNDANT and can be viewed in C.3.24.200.100 From f593d2000eb2a65922b31f48814c86c0734db81e Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 14:10:04 -0500 Subject: [PATCH 71/96] Update and rename B.4.27.500 - Longitudinal Arms & Events.feature to B.4.27.500 - REDUNDANT.feature B.4.27.500.100 Create unique event schedules for multiple arms #REDUNDANT #A.6.4.600 This feature test is REDUNDANT and can be viewed in A.6.4.600 --- ...7.500 - Longitudinal Arms & Events.feature | 79 ------------------- .../B.4.27.500 - REDUNDANT.feature | 5 ++ 2 files changed, 5 insertions(+), 79 deletions(-) delete mode 100644 Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - Longitudinal Arms & Events.feature create mode 100644 Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - REDUNDANT.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - Longitudinal Arms & Events.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - Longitudinal Arms & Events.feature deleted file mode 100644 index 1ff08706..00000000 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - Longitudinal Arms & Events.feature +++ /dev/null @@ -1,79 +0,0 @@ -Feature: User Interface: Longitudinal Project Settings: The system shall support multiple study arms and the ability to define unique event schedules for each arm. - -As a REDCap end user -I want to see that Project Setup is functioning as expected - -Scenario: B.4.27.500.100 Create unique event schedules for multiple arms -#A.6.4.600 -##SETUP_DEV -Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.4.27.500.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - -When I click on the link labeled "Project Setup" -And I click on the button labeled "Define My Events" -Then I should see a link labeled "Add New Arm" - -#FUNCTIONAL_REQUIREMENT -##ACTION ADDING NEW ARM -When I click on the link labeled "Add New Arm" -And I enter "Arm 3" in the field labeled "Arm name: " -And I click on the button labeled "Save" -#VERIFY -Then I should see "Arm 3: Arm 3" - -##ACTION ADD NEW EVENT TO NEW ARM -When I enter "Event 1" into the input field labeled "Event Label" -And I enter "1" in the input field labeled "Days Offset" -And I click on the button labeled "Add new event" -Then I should see "Event 1" - -#VERIFY_LOG -When I click on the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin| Manage/Design | Create event| -| test_admin| Manage/Design | Create arm | - -#FUNCTIONAL_REQUIREMENT -##ACTION ADD NEW EVENT TO EXISTING ARM -Given I click on the link labeled "Project Setup" -And I click on the button labeled "Define My Events" -And I click on the link labeled "Arm 1" -Then I should see the button labeled "Add new event" - -When I enter "Event 4" into the input field labeled "Event Label" -And I enter "4" in the input field labeled "Days Offset" -And I click on the button labeled "Add new event" -##VERIFY Then I should see "Event 4" - -##VERIFY_LOG -When I click on the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin| Manage/Design | Create event| - -#FUNCTIONAL_REQUIREMENT -##ACTION DESIGNATE INSTRUMENTS - #REDUNDANT #A.6.4.600 -Given I click on the link labeled "Project Setup" -When I click on the button labeled "Designate Instruments for My Events" -And I click on the link labeled "Arm 1" -#VERIFY -Then I should see the Data Collection Instrument named "Data Types" enabled for the Event named "Event 1" -And I should see the Data Collection Instrument named "Data Types" enabled for the Event named "Event 2" -And I should NOT see the Data Collection Instrument named "Data Types" enabled for the Event named "Event Three" - -##ACTION: DESIGNATE INSTRUMENTS different arm- #REDUNDANT #A.6.4.600 -When I click on the link labeled "Arm 2" -##VERIFY -Then I should see the Data Collection Instrument named "Data Types" enabled for the Event named "Event 1" - -##VERIFY_RSD -When I click on the link labeled "Record Status Dashboard" -And I click on the link labeled "Arm 1" -Then I should see Data Collection Instrument named "Data Types" for the Event named "Event 1" -And I should see Data Collection Instrument named "Data Types" for the Event named "Event 2" -And I should NOT see Data Collection Instrument named "Data Types" for the Event named "Event Three" - -When I click on the link labeled "Arm 2" -Then I should see Data Collection Instrument named "Data Types" for the Event named "Event 1" - diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - REDUNDANT.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - REDUNDANT.feature new file mode 100644 index 00000000..54cbbb37 --- /dev/null +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.500 - REDUNDANT.feature @@ -0,0 +1,5 @@ +Feature: User Interface: Longitudinal Project Settings: The system shall support multiple study arms and the ability to define unique event schedules for each arm. +Scenario: B.4.27.500.100 Create unique event schedules for multiple arms +#REDUNDANT +#A.6.4.600 +This feature test is REDUNDANT and can be viewed in A.6.4.600 From 46063889a5f841b83db0b5fe2cc9fd9a14f151a4 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 14:14:01 -0500 Subject: [PATCH 72/96] Update and rename B.4.27.600 - Repeating Events and Instruments.feature to B.4.27.600 - REDUNDANT.feature Scenario: B.4.27.600.100 Repeat instrument and event #A.6.4.500.100 This feature test is REDUNDANT and can be viewed in A.6.4.500.100 --- .../B.4.27.600 - REDUNDANT.feature | 4 + ...- Repeating Events and Instruments.feature | 171 ------------------ 2 files changed, 4 insertions(+), 171 deletions(-) create mode 100644 Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - REDUNDANT.feature delete mode 100644 Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - Repeating Events and Instruments.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - REDUNDANT.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - REDUNDANT.feature new file mode 100644 index 00000000..2be3be32 --- /dev/null +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - REDUNDANT.feature @@ -0,0 +1,4 @@ +Feature: User Interface: Longitudinal Project Settings: The system shall support the ability to create repeating events and instruments within events. +Scenario: B.4.27.600.100 Repeat instrument and event +#A.6.4.500.100 +This feature test is REDUNDANT and can be viewed in A.6.4.500.100 diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - Repeating Events and Instruments.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - Repeating Events and Instruments.feature deleted file mode 100644 index 23ac939f..00000000 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.600 - Repeating Events and Instruments.feature +++ /dev/null @@ -1,171 +0,0 @@ -Feature: User Interface: Longitudinal Project Settings: The system shall support the ability to create repeating events and instruments within events. - -As a REDCap end user -I want to see that Manage project user access is functioning as expected - -Scenario: B.4.27.600.100 Repeat instrument and event -#A.6.4.500.100 -##SETUP_DEV -Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.4.27.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - -When I click on the link labeled "Project Setup" -Then I should see "Repeating instruments and events" - -#FUNCTIONAL_REQUIREMENT -##ACTION Repeat Instruments -When I click on the button labeled "Modify" for the field labeled "Repeatable Instruments and events" -And I select "not repeating" on the dropdown field labeled "Event 1 (Arm 1: Arm 1)" in the dialog box -And I select "Repeat Instruments (repeat independently of each other)" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" in the dialog box -And I check the checkbox labeled "Survey" for the event labeled "Event Three (Arm 1: Arm 1)" in the dialog box -And I click on the button labeled "Save" in the dialog box -#VERIFY -Then I should see "Successfully saved" -And I click on the button labeled "Close" in the dialog box - -#VERIFY_LOG -When I click on the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin | Manage/Design | Set up repeating instruments/events | - -##ACTION Verify repeat instrument function in record -Given I click on the link labeled "Add/Edit Records" -And I select "1" on the dropdown field labeled "Choose an existing Record ID" -And I click the bubble to select a record for the "Survey" longitudinal instrument on event "Event Three" -And I enter "MyName" in the field labeled "Name" -And I click the button labeled "Save & Add New Instance" -And I enter "MyOtherName" in the field labeled "Name" -And I click the button labeled "Save & Exit Record" -Then I should see "Record ID 1 successfully edited" - -When I click on the link labeled "Record Status Dashboard" -And I click the bubble for the "Survey" longitudinal instrument on event "Event Three" for record "1" -And I click the bubble for instance "1" -#VERIFY -Then I should see "Current instance: " - -When I click on the link labeled "Record Status Dashboard" -And I click the bubble for the "Data Types" longitudinal instrument on event "Event 1" for record "1" -Then I should NOT see "Current instance:" - -##VERIFY_DE -When I click on the link labeled "Data Export, Reports, and Stats" -Then I should see "A All data (records and fields)" -And I click the button labeled "View Report" -Then I should NOT see repeat instrument "Data Types" for "Event 1 (Arm 1: Arm 1)" -And I should see repeat instrument "Survey" for "Event Three (Arm 1: Arm 1)" -And I should see "MyOtherName" - -#FUNCTIONAL_REQUIREMENT -##ACTION Not repeating instrument -When I click on the link labeled "Project Setup" -Then I should see "Repeating instruments and events" - -When I open the dialog box for the Repeatable Instruments and Events module -And I select "Repeat Instruments (repeat independently of each other)" on the dropdown field labeled "Event 1 (Arm 1: Arm 1)" -And I check the checkbox labeled "Data Types" -And I select "not repeating" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" -And I click on the button labeled "Save" -#VERIFY -Then I see "Successfully saved!" -And I click on the button labeled "Close" in the dialog box - -#VERIFY_LOG -When I click on the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin| Manage/Design | Set up repeating instruments/events | - -##ACTION Verify no repeat instance in record -Given I click on the link labeled "Add/Edit Records" -And I select "1" on the dropdown field labeled "Choose an existing Record ID" -And I click the bubble to select a record for the "Survey" longitudinal instrument on event "Event Three" -Then I should NOT see "Current instance:" -#VERIFY -When I click the button labeled "Cancel" -Then I should see "data entry cancelled - not saved" - -When I click the bubble for the "Data Types" longitudinal instrument on event "Event 1" -Then I should see "Current instance:" - -##VERIFY_DE -When I click on the link labeled "Data Export, Reports, and Stats" -Then I should see "A All data (records and fields)" - -When I click the button labeled "View Report" -Then I should see repeat instrument instance for instrument "Data Types" for "Event 1 (Arm 1: Arm 1)" -And I should NOT see repeat instrument instance for instrument "Survey" for "Event Three (Arm 1: Arm 1)" -And I should NOT see "MyOtherName" -And I should see repeat event instance for event "Event 2 (Arm 1: Arm 1)" -And I should NOT see repeat event instance for event "Event Three (Arm 1: Arm 1)" - -#FUNCTIONAL_REQUIREMENT -##ACTION Repeat event -When I click on the link labeled "Project Setup" -And I open the dialog box for the Repeatable Instruments and Events module -And I select "Not repeating" on the dropdown field labeled "Event 2 (Arm 1: Arm 1)" -And I select "Repeat Entire Event" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" -And I click on the button labeled "Save" -#VERIFY -Then I see "Successfully saved!" -And I click on the button labeled "Close" in the dialog box - -#VERIFY_LOG -When I click on the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin| Manage/Design | Set up repeating instruments/events | - -##ACTION Verify repeat event function in record -Given I click on the link labeled "Add/Edit Records" -And I select "1" on the dropdown field labeled "Choose an existing Record ID" -Then I should see "(#2)" - -When I click on "Add new" -And I click the bubble for the "Survey" longitudinal instrument on event "Event Three" instance "2" -And I enter "My repeat event name" in the field labeled "Name" -And I click the button "Save & Exit Form" -Then I should see "(#2)" - -##VERIFY_DE -And I click on the link labeled "Data Export, Reports, and Stats" -Then I should see "A All data (records and fields)" -And I click the button labeled "View Report" -Then I should NOT see repeat event instance for event "Event 2 (Arm 1: Arm 1)" -And I should see repeat event instance for event "Event Three (Arm 1: Arm 1)" -And I should see "My repeat event name" - -#FUNCTIONAL_REQUIREMENT -##ACTION No Repeat event -When I click on the link labeled "Project Setup" -And I open the dialog box for the Repeatable Instruments and Events module -And I select "Repeat Entire Event" on the dropdown field labeled "Event 2 (Arm 1: Arm 1)" -And I select "Not repeating" on the dropdown field labeled "Event Three (Arm 1: Arm 1)" -And I click on the button labeled "Save" -##VERIFY -Then I should see "Successfully saved" - -##VERIFY_DE -When I click on the link labeled "Data Export, Reports, and Stats" -Then I should see "A All data (records and fields) -And I click the button labeled "View Report" -Then I should see repeat event instance for event "Event 2 (Arm 1: Arm 1)" -And I should see repeat event instance for event "Event Three (Arm 1: Arm 1)" -And I should NOT see "My repeat event name" - -#FUNCTIONAL_REQUIREMENT -##ACTION Delete repeat event -Given I click on the link labeled "Add/Edit Records" -And I select "1" on the dropdown field labeled "Choose an existing Record ID" -And I click the X to delete all data related to the event named "Event 2 (Arm 1: Arm 1)" instance "2" -And I click on the button labeled "Delete this instance of this event" in the dialog box -##VERIFY -Then I should NOT see "(#2)" - -#VERIFY_LOG -When I click on the link labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | -| test_admin| Update record 1 (Event 2 (Arm 1: Arm 1)) | - From 5982202f6f867c5c84cfe4e7b74c73a09baaf794 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 14:16:51 -0500 Subject: [PATCH 73/96] Update and rename B.4.27.700 - Longitudinal Administrative Controls.feature to B.4.27.700 - REDUNDANT.feature B.4.27.700.100 Admin delete events and arm in Define My Events This feature test is REDUNDANT and can be viewed in A.6.4.500 --- ...ngitudinal Administrative Controls.feature | 57 ------------------- .../B.4.27.700 - REDUNDANT.feature | 3 + 2 files changed, 3 insertions(+), 57 deletions(-) delete mode 100644 Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Administrative Controls.feature create mode 100644 Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - REDUNDANT.feature diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Administrative Controls.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Administrative Controls.feature deleted file mode 100644 index f20d1e51..00000000 --- a/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - Longitudinal Administrative Controls.feature +++ /dev/null @@ -1,57 +0,0 @@ -Feature: User Interface: Longitudinal Project Settings: The system shall require administrators to delete events for longitudinal projects while in production - -As a REDCap end user -I want to see that Manage project user access is functioning as expected - -Scenario: B.4.27.700.100 Admin delete events and arm in Define My Events -#SETUP -Given I login to REDCap with the user "Test_User1" -And I create a new project named "B.4.27.700.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - -#SETUP_PRODUCTION -When I click on the button labeled "Move project to production" -And I click on the radio labeled "Keep ALL data saved so far" in the dialog box -And I click on the button labeled "YES, Move to Production Status" in the dialog box -Then I see "Project status: Production" - -#FUNCTIONALREQUIREMENT -##ACTION User unable to delete event -When I click on the link labeled "Project Setup" -And I click on the button labeled "Define My Events" -##VERIFY -Then I should see "Events cannot be modified in production" -And I should NOT see the delete icon for the event labeled "1" -And I logout - -#SETUP -Given I login to REDCap with the user "Test_Admin" -When I click on the link labeled "Project Setup" -And I click on the button labeled "Define My Events" -Then I should see the delete icon for the event labeled "Event 2" for arm "Arm 1: Arm 1" with a unique event ID - -#FUNCTIONALREQUIREMENT -##ACTION Admin deletes event -When I click on the delete icon for the event labeled "Event 1" for arm "Arm 1: Arm 1" -And I click on the button labeled "OK" in the pop-up box -And I click on the button labeled "OK" in the pop-up box -Then I should NOT see the event labeled "Event 1" for arm "Arm 1: Arm 1" - -#VERIFY_LOG -When I click on the button labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin| Manage/design | Delete event (Event: Event 1, Arm: Arm 1) | - -##ACTION Delete Arm -Given I click on the link labeled "Project Setup" -And I click on the button labeled "Define My Events" -And I click on the link labeled "Delete Arm 1" -And I click on the button labeled "OK" in the pop-up box -#VERIFY -Then I should NOT see "Arm 1" - -#VERIFY_LOG -When I click on the button labeled "Logging" -Then I should see a table header and rows including the following values in the logging table: -| Username | Action | List of Data Changes OR Fields Exported | -| test_admin| Manage/design | Delete arm (Arm 1: Arm 1) diff --git a/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - REDUNDANT.feature b/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - REDUNDANT.feature new file mode 100644 index 00000000..a2fc868f --- /dev/null +++ b/Feature Tests/B/Longitudinal Project Setup/B.4.27.700 - REDUNDANT.feature @@ -0,0 +1,3 @@ +Feature: User Interface: Longitudinal Project Settings: The system shall require administrators to delete events for longitudinal projects while in production +Scenario: B.4.27.700.100 Admin delete events and arm in Define My Events +This feature test is REDUNDANT and can be viewed in A.6.4.500 From cfc163d8826851f8dc32cd9b56216d3becbf796b Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 14:42:52 -0500 Subject: [PATCH 74/96] Update and rename B.2.10.600 - Unique DAGs.feature to B.2.10.600 - REDUNDANT.feature Scenario: B.2.10.600.100 Unique DAGs This feature test is REDUNDANT and can be viewed in B.2.10.600.100 Unique DAGs --- .../B.2.10.600 - REDUNDANT.feature | 3 ++ .../B.2.10.600 - Unique DAGs.feature | 50 ------------------- 2 files changed, 3 insertions(+), 50 deletions(-) create mode 100644 Feature Tests/B/Data Access Groups/B.2.10.600 - REDUNDANT.feature delete mode 100644 Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.600 - REDUNDANT.feature b/Feature Tests/B/Data Access Groups/B.2.10.600 - REDUNDANT.feature new file mode 100644 index 00000000..7e503bb6 --- /dev/null +++ b/Feature Tests/B/Data Access Groups/B.2.10.600 - REDUNDANT.feature @@ -0,0 +1,3 @@ +Feature: User Interface: The system shall provide the DAG unique group names in the data export raw CSV file and the label in the CSV labels data file. +Scenario: B.2.10.600.100 Unique DAGs +This feature test is REDUNDANT and can be viewed in B.2.10.600.100 Unique DAGs diff --git a/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature b/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature deleted file mode 100644 index ac87dc69..00000000 --- a/Feature Tests/B/Data Access Groups/B.2.10.600 - Unique DAGs.feature +++ /dev/null @@ -1,50 +0,0 @@ -Feature: User Interface: The system shall provide the DAG unique group names in the data export raw CSV file and the label in the CSV labels data file. - -As a REDCap end user -I want to see that Data Access Groups is functioning as expected - -Scenario: B.2.10.600.100 Unique DAGs - -#SETUP -Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.2.10.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button - -When I click on the link labeled "Record Status Dashboard" -And I click on the link labeled "3" -Then I should see the "Record Home Page" - -#FUNCTIONAL REQUIREMENT -##ACTION: Assign Record DAG_testgroup1 -##REDUNDANT #B.2.10.500 Assign Records to a DAG -When I select the dropdown option labeled "Assign to Data Access Group" from the dropdown "Choose action for record" -And I select the dropdown option labeled "TestGroup1" from the dropdown with the placeholder text of "[No Assignment]" in the dialog box -And I click on the button labeled "Assign to Data Access Group" in the dialog box - -##VERIFY -Then I should see "Record ID 3 was successfully assigned to a Data Access Group!" -And I should see "Arm 1: Arm 1 - TestGroup1" - -When I click on the link labeled "Record Status Dashboard" -And I click on the link labeled "4" -Then I should see the "Record Home Page" - -#FUNCTIONAL REQUIREMENT -##ACTION: Assign Record DAG_testgroup2 -When I select the dropdown option labeled "Assign to Data Access Group" from the dropdown "Choose action for record" -And I select the dropdown option labeled "TestGroup2" from the dropdown with the placeholder text of "[No Assignment]" in the dialog box -And I click on the button labeled "Assign to Data Access Group" in the dialog box - -##VERIFY -Then I should see "Record ID 4 was successfully assigned to a Data Access Group!" -And I should see "Arm 1: Arm 1 - TestGroup2" - -##VERIFY_DE -When I click on the link labeled "Data Exports, Reports, and Stats" -Then I should see a table row containing the following values in the reports table: -| A | All data (all records and fields) | - -When I click on the button labeled "View Report" -Then I should see a table header and rows including the following values in the report data table: -| Record ID| Data Access Group | -| 3 | TestGroup1 | -| 4 | TestGroup2 | From dcddc2f001f245a2cb9414132c22f5805121e6cd Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 14:44:06 -0500 Subject: [PATCH 75/96] Update and rename B.2.10.600 - REDUNDANT.feature to B.2.10.600 - B.2.10.600 - Unique DAGs.feature B.2.10.600.100 Unique DAGs --- ....10.600 - B.2.10.600 - Unique DAGs.feature | 50 +++++++++++++++++++ .../B.2.10.600 - REDUNDANT.feature | 3 -- 2 files changed, 50 insertions(+), 3 deletions(-) create mode 100644 Feature Tests/B/Data Access Groups/B.2.10.600 - B.2.10.600 - Unique DAGs.feature delete mode 100644 Feature Tests/B/Data Access Groups/B.2.10.600 - REDUNDANT.feature diff --git a/Feature Tests/B/Data Access Groups/B.2.10.600 - B.2.10.600 - Unique DAGs.feature b/Feature Tests/B/Data Access Groups/B.2.10.600 - B.2.10.600 - Unique DAGs.feature new file mode 100644 index 00000000..ac87dc69 --- /dev/null +++ b/Feature Tests/B/Data Access Groups/B.2.10.600 - B.2.10.600 - Unique DAGs.feature @@ -0,0 +1,50 @@ +Feature: User Interface: The system shall provide the DAG unique group names in the data export raw CSV file and the label in the CSV labels data file. + +As a REDCap end user +I want to see that Data Access Groups is functioning as expected + +Scenario: B.2.10.600.100 Unique DAGs + +#SETUP +Given I login to REDCap with the user "Test_Admin" +And I create a new project named "B.2.10.600.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button + +When I click on the link labeled "Record Status Dashboard" +And I click on the link labeled "3" +Then I should see the "Record Home Page" + +#FUNCTIONAL REQUIREMENT +##ACTION: Assign Record DAG_testgroup1 +##REDUNDANT #B.2.10.500 Assign Records to a DAG +When I select the dropdown option labeled "Assign to Data Access Group" from the dropdown "Choose action for record" +And I select the dropdown option labeled "TestGroup1" from the dropdown with the placeholder text of "[No Assignment]" in the dialog box +And I click on the button labeled "Assign to Data Access Group" in the dialog box + +##VERIFY +Then I should see "Record ID 3 was successfully assigned to a Data Access Group!" +And I should see "Arm 1: Arm 1 - TestGroup1" + +When I click on the link labeled "Record Status Dashboard" +And I click on the link labeled "4" +Then I should see the "Record Home Page" + +#FUNCTIONAL REQUIREMENT +##ACTION: Assign Record DAG_testgroup2 +When I select the dropdown option labeled "Assign to Data Access Group" from the dropdown "Choose action for record" +And I select the dropdown option labeled "TestGroup2" from the dropdown with the placeholder text of "[No Assignment]" in the dialog box +And I click on the button labeled "Assign to Data Access Group" in the dialog box + +##VERIFY +Then I should see "Record ID 4 was successfully assigned to a Data Access Group!" +And I should see "Arm 1: Arm 1 - TestGroup2" + +##VERIFY_DE +When I click on the link labeled "Data Exports, Reports, and Stats" +Then I should see a table row containing the following values in the reports table: +| A | All data (all records and fields) | + +When I click on the button labeled "View Report" +Then I should see a table header and rows including the following values in the report data table: +| Record ID| Data Access Group | +| 3 | TestGroup1 | +| 4 | TestGroup2 | diff --git a/Feature Tests/B/Data Access Groups/B.2.10.600 - REDUNDANT.feature b/Feature Tests/B/Data Access Groups/B.2.10.600 - REDUNDANT.feature deleted file mode 100644 index 7e503bb6..00000000 --- a/Feature Tests/B/Data Access Groups/B.2.10.600 - REDUNDANT.feature +++ /dev/null @@ -1,3 +0,0 @@ -Feature: User Interface: The system shall provide the DAG unique group names in the data export raw CSV file and the label in the CSV labels data file. -Scenario: B.2.10.600.100 Unique DAGs -This feature test is REDUNDANT and can be viewed in B.2.10.600.100 Unique DAGs From 916b680a725913ff5b4f6f540ad9538f51c8b55e Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 15:10:59 -0500 Subject: [PATCH 76/96] Update B.3.15.1100 - Survey Response Tracking.feature Changed actions --- ....3.15.1100 - Survey Response Tracking.feature | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey Response Tracking.feature b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey Response Tracking.feature index 4d67127b..18749cf7 100644 --- a/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey Response Tracking.feature +++ b/Feature Tests/B/Direct Data Entry - Survey/B.3.15.1100 - Survey Response Tracking.feature @@ -5,7 +5,6 @@ I want to see that Survey Feature is functioning as expected Scenario: B.3.15.1100.100 Tracking survey responders - #SETUP Given I login to REDCap with the user "Test_User1" And I create a new project named "B.3.15.1100.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing file "Project_1.xml", and clicking the "Create Project" button @@ -29,12 +28,13 @@ And I should see a grey bubble for the column labeled "Responded?" for record "2 #FUNCTIONAL_REQUIREMENT ##ACTION When I click the link icon for record "1" -And I click on the button labeled "Survey Options" -And I click on the dropdown option labeled "Open survey" -And I click on the button labeled "Submit" -And I click on the button labeled "Close survey" -And I click on the button labeled "Leave without saving changes" in the dialog box -And I click on the link labeled "Survey Invitation Log" +Then I should see "Survey" +And I should see "Name" + +When I click on the button labeled "Submit" +Then I should see "Close survey" + +When I click on the link labeled "Survey Distribution Tools" And I click on the button labeled "Participant List" And I select "Survey" from the dropdown labeled "Participant List belonging to" -Then I should see a green checkmark for the column labeled "Responded?" for record "1" +Then green checkmark for the column labeled "Responded?" for record "1" From 22631d4f7274bfe3d4d6014847afd5dcd03ea381 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 15:26:13 -0500 Subject: [PATCH 77/96] Update B.4.9.100 - Branching Logic.feature updated test --- .../B.4.9.100 - Branching Logic.feature | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/Feature Tests/B/Branching Logic/B.4.9.100 - Branching Logic.feature b/Feature Tests/B/Branching Logic/B.4.9.100 - Branching Logic.feature index b84af7c6..14e838ba 100644 --- a/Feature Tests/B/Branching Logic/B.4.9.100 - Branching Logic.feature +++ b/Feature Tests/B/Branching Logic/B.4.9.100 - Branching Logic.feature @@ -17,7 +17,6 @@ And I verify I see "Branching logic: [record_id] = '999'" on the field labeled " And I verify I see "Branching logic: [record_id] = '999'" on the field labeled "Text2" And I verify I see "Branching logic: [record_id] = '999'" on the field labeled "Notes Box" - #FUNCTIONAL_REQUIREMENT: survey mode When I click on the link labeled "Survey Distribution Tools" And I click on the button labeled "Open public survey" @@ -28,7 +27,7 @@ And I should NOT see the field labeled "Notes box" And I should see the field labeled "Calculated Field" And I should see the field labeled "Multiple Choice dropdown Auto" And I should see the field labeled "Multiple Choice dropdown Manual" -#M: Close the survey page +#Manual: Close the survey page #FUNCTIONAL_REQUIREMENT: data entry mode When I click the link labeled "Add/Edit Records" @@ -46,18 +45,18 @@ And I should see the field labeled "Calculated Field" And I should see the field labeled "Multiple Choice dropdown Auto" And I should see the field labeled "Multiple Choice dropdown Manual" -##ACTION: change branching logic +##ACTION: change branching logic for one When I click on the link labeled "Designer" And I click on the button labeled "Leave without saving changes" in the dialog box And I click on the instrument labeled "Data Types" And I click on the Branching Logic icon for the field labeled "Name" -And I enter " [record_id] <> '999'" in the field labeled "Advanced Branching Logic Syntax" +And I enter "[record_id] <> '999'" in the field labeled "Advanced Branching Logic Syntax" And I click on the button labeled "Update & Close Editor" And I click on the button labeled "Save" And I click on the button labeled "No" in the dialog box Then I should see "Branching logic: [record_id] <> '999'" on the field labeled "Name" -##ACTION: change branching logic +##ACTION: change branching logic for all When I click on the Branching Logic icon for the field labeled "Text2" And I enter " [record_id] <> '999'" in the field labeled "Advanced Branching Logic Syntax" And I click on the button labeled "Update & Close Editor" @@ -75,7 +74,7 @@ And I should see the field labeled "Notes box" And I should see the field labeled "Calculated Field" And I should see the field labeled "Multiple Choice dropdown Auto" And I should see the field labeled "Multiple Choice dropdown Manual" -#M: Close tab +#Manual: Close tab #FUNCTIONAL_REQUIREMENT: data entry mode When I click the link labeled "Add/Edit Records" @@ -90,6 +89,7 @@ And I should see the field labeled "Multiple Choice dropdown Auto" And I should see the field labeled "Multiple Choice dropdown Manual" ##ACTION +#FUNCTIONAL_REQUIREMENT: Radio logic When I click on the link labeled "Designer" And I click on the button labeled "Leave without saving changes" in the dialog box And I click on the instrument labeled "Data Types" @@ -99,6 +99,7 @@ And I drag the field choice labeled "radio_button_manual = Choice101 (101)" to t And I click on the button labeled "Save" Then I should see "Branching logic: [radio_button_manual] = '101'" on the field labeled "Descriptive Text with File" +#FUNCTIONAL_REQUIREMENT: Checkbox logic When I click on the Branching Logic icon for the field labeled "Required" And I click on the radio labeled "Drag-N-Drop Logic Builder" And I drag the field choice labeled "checkbox = Checkbox (3)" to the box labeled "Show the field only if" @@ -119,7 +120,7 @@ Then I should see the field labeled "Required" When I deselect the multi-select option labeled "Checkbox3" on the field labeled "Checkbox" Then I should NOT see the field labeled "Required" -#M: Close the survey page +#Manual: Close the survey page ##VERIFY_LOG When I click on the link labeled "Logging" From ef7a829020c68bb9543d41ccbc36f001fceb9320 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 15:40:47 -0500 Subject: [PATCH 78/96] Update B.5.21.100 - Export PHI.feature --- .../B.5.21.100 - Export PHI.feature | 51 ++++++++++--------- 1 file changed, 26 insertions(+), 25 deletions(-) diff --git a/Feature Tests/B/Export Data/B.5.21.100 - Export PHI.feature b/Feature Tests/B/Export Data/B.5.21.100 - Export PHI.feature index 50cdfa1d..3361e5c4 100644 --- a/Feature Tests/B/Export Data/B.5.21.100 - Export PHI.feature +++ b/Feature Tests/B/Export Data/B.5.21.100 - Export PHI.feature @@ -14,47 +14,47 @@ And I enter "Test_User1" into the field with the placeholder text of "Assign new And I click on the button labeled "Assign to role" And I select "4_NoAccess_Noexport" on the dropdown field labeled "Select Role" on the role selector dropdown And I click on the button labeled exactly "Assign" on the role selector dropdown -Then I should see "Test User1" within the "3_ReadOnly_Deidentified" row of the column labeled "Username" of the User Rights table +Then I should see a table header and rows including the following values in the logging table: +| Role name | Username | +| 4_NoAccess_Noexport | test_user1 | ##VERIFY_CODEBOOK When I click on the link labeled "Codebook" Then I should see a table header and rows containing the following values in the codebook table: | Variable/Field Name | Field Label| Field Attributes (Field/Type, Validation, Choices, Calculations, etc. | -| [identifier] | Identifier |text, Identifier | -| [identifier_2] | Identifier 2 |text, Identifier | -| [ptname] | Name |text | -| [radio ] | radio | radio, Identifier | - +| [identifier] | Identifier |text, Identifier | +| [identifier_2] | Identifier 2 |text, Identifier | +| [ptname] | Name |text | +| [radio ] | radio | radio, Identifier | ##ACTION: change identifier status When I click on the link labeled "Project Setup" And I click on the link labeled "Check for identifiers" Then I should see a table header and rows containing the following values in the codebook table: | Variable Name | Field Label| Identifier?| -| identifier | Identifier |check icon | -| identifier_2 | Identifier 2|check icon | -| ptname | Name | | -| radio | radio | check icon| +| identifier | Identifier | select checkbox | +| identifier_2 | Identifier 2|select checkbox | +| ptname | Name | deselect checkbox | +| radio | radio | select checkbox| When I deselect the checkbox labeled "Identifier?" for the variable labeled "identifier_2" And I select the checkbox labeled "Identifier?" for the variable labeled "ptname" And I click on the button labeled "Update Identifiers" Then I should see a table header and rows containing the following values in the codebook table: | Variable Name | Field Label| Identifier?| -| identifier | Identifier |check icon | -| identifier_2 | Identifier 2 | | -| ptname | Name | check icon| -| radio | radio | check icon| +| identifier | Identifier | select checkbox | +| identifier_2 | Identifier 2| deselect checkbox | +| ptname | Name | select checkbox | +| radio | radio | select checkbox| ##VERIFY_CODEBOOK When I click on the link labeled "Codebook" Then I should see a table header and rows containing the following values in the codebook table: | Variable/Field Name | Field Label| Field Attributes (Field/Type, Validation, Choices, Calculations, etc. | -| [identifier] | Identifier |text, Identifier | -| [identifier_2] | Identifier 2 |text | -| [ptname] | Name | text, Identifier | -| [radio ] | radio | radio, Identifier | - +| [identifier] | Identifier |text, Identifier | +| [identifier_2] | Identifier 2 |text | +| [ptname] | Name | text, Identifier | +| [radio ] | radio | radio, Identifier | ##VERIFY_DE When I click on the link labeled "Data Exports, Reports, and Stats" @@ -72,7 +72,7 @@ Given I click on the download icons to receive the files for the "CSV / Microsof ##VERIFY: User can see all variables, including identifier, identifier_2 and name, survey_timestamp, radio button Then I should have a "csv" file that contains the headings below | record_id | redcap_repeat_instrument | redcap_repeat_instance | redcap_data_access_group | redcap_survey_identifier | data_types_timestamp | pt_name | textbox | radio | notesbox | identifier | identifier_2 | date_ymd | datetime_ymd_hmss | date_types_complete | -#M: Close the report +#Manual: Close the report And I click on the button labeled "Close" in the dialog box @@ -91,7 +91,7 @@ Given I click on the download icons to receive the files for the "CSV / Microsof Then I should have a "csv" file that contains the headings below | record_id | redcap_repeat_instrument | redcap_repeat_instance | redcap_data_access_group | data_types_timestamp | textbox | notesbox | identifier_2 | date_ymd | datetime_ymd_hmss | date_types_complete | -#M: Close the report & refresh page +#Manual: Close the report & refresh page And I click on the button labeled "Close" in the dialog box @@ -111,7 +111,7 @@ Given I click on the download icons to receive the files for the "CSV / Microsof Then I should have a "csv" file that contains the headings below | record_id | redcap_repeat_instrument | redcap_repeat_instance | redcap_data_access_group | redcap_survey_identifier | data_types_timestamp | radio | date_ymd | datetime_ymd_hmss | date_types_complete | -#M: Close the report & refresh page +#Manual: Close the report & refresh page And I click on the button labeled "Close" in the dialog box @@ -128,7 +128,7 @@ Given I click on the download icons to receive the files for the "CSV / Microsof Then I should have a "csv" file that contains the headings below | record_id | redcap_repeat_instrument | redcap_repeat_instance | redcap_data_access_group | redcap_survey_identifier | data_types_timestamp | pt_name | textbox | radio | notesbox | identifier | identifier_2 | date_types_complete | -#M: Close the report & refresh page +#Manual: Close the report & refresh page And I click on the button labeled "Close" in the dialog box @@ -148,6 +148,7 @@ And I click on the button labeled "Close Survey" And I click on the button labeled "Leave without saving changes" in the dialog box Then I should see "Record Home Page" And I should see a Completed Survey Response Icon for the field the instrument labeled "Data Types" + FUNCTIONAL_REQUIREMENT ##ACTION: shift all dates Given I click on the link labeled "Data Exports, Reports, and Stats" @@ -161,14 +162,14 @@ And I should see "All dates within your data have been DATE SHIFTED to an unknow Given I click on the download icons to receive the files for the "CSV / Microsoft Excel (raw data)" format in the dialog box ##VERIFY: -#MUser can see all variables with dates shifted ([date_ymd]=! 2023-08-22) AND ([date_ymd_hmss]=! 2023-08-23 11:48:01) +#Manual User can see all variables with dates shifted ([date_ymd]=! 2023-08-22) AND ([date_ymd_hmss]=! 2023-08-23 11:48:01) Then I should have a "csv" file And I verify that the timestamp in the column labeled "data_types_timestamp" for record 5 has shifted And I verify that the date in the column labeled "date_ymd" for record 5 has shifted And I verify that the datetime in the column labeled "date_ymd_hmss" for record 5 has shifted -#M: Close the report & refresh page +#Manual: Close the report & refresh page And I click on the button labeled "Close" in the dialog box And I logout From 106c9b7dbfdf8361e192853f3f4fe9cbc51630e4 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 15:51:11 -0500 Subject: [PATCH 79/96] Update C.4.18.1400 - Data Quality support user rights.feature From dc469c2486b20bce7e8256e078f02ca91918ec16 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 16:00:36 -0500 Subject: [PATCH 80/96] Update C.3.26.200 - View Access & User Rights.feature --- ...26.200 - View Access & User Rights.feature | 38 ++++++++++--------- 1 file changed, 21 insertions(+), 17 deletions(-) diff --git a/Feature Tests/C/File Repository/C.3.26.200 - View Access & User Rights.feature b/Feature Tests/C/File Repository/C.3.26.200 - View Access & User Rights.feature index 6b066ce7..7520863b 100644 --- a/Feature Tests/C/File Repository/C.3.26.200 - View Access & User Rights.feature +++ b/Feature Tests/C/File Repository/C.3.26.200 - View Access & User Rights.feature @@ -50,16 +50,16 @@ Then I should see a dialog containing the following text: "SUCCESS!" And I close the popup And I should see a table header and rows including the following values in the table: -|Role name | Username | -| | test_admin | -| | test_user1 | -| | test_user2 | -| | test_user3 | -| | test_user4 | -| 1_FullRights | | | -| 2_Edit_RemoveID| | | -| 3_ReadOnly_Deidentified | | -| 4_NoAccess_Noexport | | +|Role name | Username | +| | test_admin | +| | test_user1 | +| | test_user2 | +| | test_user3 | +| | test_user4 | +| 1_FullRights | | +| 2_Edit_RemoveID| | +| 3_ReadOnly_Deidentified | | +| 4_NoAccess_Noexport | | ##SETUP Assign to roles When I click on the link labeled "Test_User1" @@ -85,6 +85,15 @@ And I click on the button labeled "Assign to role" And I should see the dropdown field labeled "Select Role" with the option "3_ReadOnly_Deidentified" selected And I click on the button labeled "Assign" Then I should see "Test_User4" user assigned "3_ReadOnly_Deidentified" role +And I should see a table header and rows including the following values in the table: +|Role name | Username | +| | test_admin | +| 1_FullRights | test_user1 | +| 1_FullRights | test_user2 | +| 2_Edit_RemoveID| | +| 3_ReadOnly_Deidentified | test_user3 | +| 3_ReadOnly_Deidentified | test_user4 | +| 4_NoAccess_Noexport | | ##SETUP DAG: Assign User to DAG When I select "Test_User1" from "Assign User" dropdown @@ -93,7 +102,8 @@ And I click on the button labeled "Assign" Then I should see "Test_User1" assigned to "TestGroup1" When I select "Test_User2" from "Assign User" dropdown -And I select "TestGroup2" from "DAG" dropdown +And I select "TestGroup2" from "DAG" dropdown +And I click on the button labeled "Assign" Then I should see "Test_User2" assigned to "TestGroup2" When I select "Test_User3" from "Assign User" dropdown @@ -112,7 +122,6 @@ And I click on the button labeled "Add new record for the arm selected above" And I click on the bubble labeled "Consent" for event "Event 1" Then I should see "Adding new Record ID" - When I click on the button labeled "Save & Stay" And I select the dropdown option labeled "Open survey" from the dropdown button with the placeholder text of "Survey options" And I click on the button labeled "Next Page" @@ -135,7 +144,6 @@ Then I should see "user list for project 1.csv" And I should see "Role1_Folder" And I should see "TestGroup1_Folder" - ##ACTION Upload to top tier file repo (all users will see file) - using the Select files to upload button When I click on the link labeled "File Repository" When I upload a "csv" format file located at "import_files/testusers_bulk_upload.csv", by clicking the button near "Select files to upload" to browse for the file, and clicking the button labeled "Open" to upload the file @@ -143,7 +151,6 @@ When I upload a "csv" format file located at "import_files/testusers_bulk_upload ##VERIFY_FiRe file uploaded in folder Then I should see "testusers_bulk_upload.csv" - #FUNCTIONAL_REQUIREMENT ##ACTION Upload to DAG folder When I click on the link labeled "TestGroup1_Folder" @@ -194,7 +201,6 @@ And I click on the button labeled "Leave without saving changes" in the dialog b Then I should see a Completed Survey Response icon for the Data Collection Instrument labeled "Consent" for event "Event 1" And I should see "TestGroup2" - #FUNCTIONAL_REQUIREMENT When I click on the link labeled "File Repository" ##ACTION Unable to access DAG folder @@ -234,7 +240,6 @@ Name | Record | And I logout - #FUNCTIONAL_REQUIREMENT Given I login to REDCap with the user "Test_User3" When I click on the link labeled "File Repository" @@ -273,7 +278,6 @@ Name | Record | And I logout - #FUNCTIONAL_REQUIREMENT ##ACTION Download to top tier file Given I login to REDCap with the user "Test_User4" From 23833938be075ee208df5ab94b81022f575ee6ee Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 16:21:10 -0500 Subject: [PATCH 81/96] Update C.4.18.1000 - Data Quality realtime.feature C.4.18.1000.100 Real-time rule execution --- .../C.4.18.1000 - Data Quality realtime.feature | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature b/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature index 41a865dd..ea17ae2a 100644 --- a/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature +++ b/Feature Tests/C/Data Quality/C.4.18.1000 - Data Quality realtime.feature @@ -23,11 +23,11 @@ Then I should see "Data Quality Rules" When I enter "Integer" for the field labeled "Rule Name" And I enter "[integer]<>'1999'" for the field labeled "Logic Editor" And I click on the button labeled "Update & Close Editor" in the dialog box -And I click on the button labeled "Execute in real time on data entry forms" button +And I select the checkbox labeled "Execute in real time on data entry forms" And I click on the button labeled "Add" Then I should see a table header and rows containing the following values in the Data Quality Rules table: -| Rule # | Rule Name | Rule Logic (Show discrepancy only if...) | -| 3 | Integer | [integer]<>'1999' | +| Rule # | Rule Name | Rule Logic (Show discrepancy only if...) | Real-time execution | +| 3 | Integer | [integer]<>'1999' | Enabled | #FUNCTIONAL_REQUIREMENT ##ACTION: System shall support the ability to run custom data quality rules real time @@ -35,7 +35,9 @@ When I click the link labeled "Add/Edit Records" And I click on the button labeled "Add new record for the arm selected above" And I click the bubble labeled "Data Types" for event "Event 1" And I enter "2000" in the field labeled "Integer" -And I click on the button labeled "Close" in the dialog box +Then I should see "The value you provided is outside the suggested range" + +When I click on the button labeled "Close" in the dialog box And I click the button labeled "Save and Exit Form" Then I should see "WARNING: Data Quality rules were violated!" And I click on the button labeled "Close" in the dialog box From 09a5afd1b40b2623fc5cee451548140685c89195 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 16:27:26 -0500 Subject: [PATCH 82/96] Update C.4.18.700 - Data Quality edit rules.feature C.4.18.700.100 Edit rule --- .../Data Quality/C.4.18.700 - Data Quality edit rules.feature | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature b/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature index 8672cccb..ed540831 100644 --- a/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature +++ b/Feature Tests/C/Data Quality/C.4.18.700 - Data Quality edit rules.feature @@ -14,6 +14,7 @@ When I click on the link labeled "Project Setup" And I click on the button labeled "Move project to production" And I click on the radio labeled "Keep ALL data saved so far" in the dialog box And I click on the button labeled "YES, Move to Production Status" in the dialog box + #USER_RIGHTS When I click on the link labeled "User Rights" And I click on the link labeled "Test_User1" @@ -35,7 +36,7 @@ And I click on the button labeled "Add" ##VERIFY Then I should see a table header and rows including the following values in the Data Quality Rules table: | Rule # | Rule Name | Rule Logic (Show discrepancy only if...) | -| 3 | Integer | [integer]='1' | +| 3 | Integer | [integer]='1' | #FUNCTIONAL_REQUIREMENT ##ACTION executing rule @@ -64,7 +65,6 @@ And I deselect the checkbox labeled "Create & edit rules" for the field labeled And I click on the button labeled "Save Changes" Then I should see "User "test_user1" was successfully edited" - #FUNCTIONAL_REQUIREMENT ##ACTION: cannot add rule and can execute rules When I click on the link labeled "Data Quality" From 0e81b6a90eddf14d9e0ed07b99248b5831572ea9 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 16:36:09 -0500 Subject: [PATCH 83/96] Update B.6.7.800 - Field Notes.feature --- .../Online Designer/B.6.7.800 - Field Notes.feature | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/Feature Tests/B/Online Designer/B.6.7.800 - Field Notes.feature b/Feature Tests/B/Online Designer/B.6.7.800 - Field Notes.feature index cb2939a8..9b423b2d 100644 --- a/Feature Tests/B/Online Designer/B.6.7.800 - Field Notes.feature +++ b/Feature Tests/B/Online Designer/B.6.7.800 - Field Notes.feature @@ -7,7 +7,7 @@ Scenario: B.6.7.800.100 Note box field creation in Online Designer #SETUP Given I login to REDCap with the user "Test_Admin" -And I create a new project named " B.6.7.800.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button +And I create a new project named "B.6.7.800.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button ##SETUP_PRODUCTION When I click on the link labeled "My Projects" @@ -48,10 +48,10 @@ Then I should see a table header and rows including the following values in the | Username | Action | List of Data Changes OR Fields Exported | | test_admin | Manage/Design | Create project field | -Scenario: B.6.7.800.200 Note box field creation in Data Dictionary +#Scenario: B.6.7.800.200 Note box field creation in Data Dictionary #SETUP -Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.7.700.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button +#Given I login to REDCap with the user "Test_Admin" +#And I create a new project named "B.6.7.700.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button #FUNCTIONAL_REQUIREMENT ##ACTION: Upload data dictionary @@ -67,4 +67,8 @@ Then I should see "Changes Made Successfully!" ##VERIFY_CODEBOOK When I click on the link labeled "Codebook" Then I should see a table row containing the following values in the codebook table: +| Variable / Field Name | Field Label | Field Attributes (Field Type, Validation, Choices, Calculations, etc.) | +| [notesbox] | Notes box | notes | | [notesbox2] | Notes box 2 | notes | + + From 5186e1343313af920037040682e2bc5d8714f238 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 28 Dec 2023 16:45:46 -0500 Subject: [PATCH 84/96] Update B.6.7.900 - Field Calculated.feature --- .../B.6.7.900 - Field Calculated.feature | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/Feature Tests/B/Online Designer/B.6.7.900 - Field Calculated.feature b/Feature Tests/B/Online Designer/B.6.7.900 - Field Calculated.feature index 8de26eba..e7b50d3f 100644 --- a/Feature Tests/B/Online Designer/B.6.7.900 - Field Calculated.feature +++ b/Feature Tests/B/Online Designer/B.6.7.900 - Field Calculated.feature @@ -9,8 +9,6 @@ Given I login to REDCap with the user "Test_Admin" And I create a new project named "B.6.7.900.100" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button ##SETUP_PRODUCTION -When I click on the link labeled "My Projects" -And I click on the link labeled "B.6.7.900.100" When I click on the button labeled "Project Setup" And I click on the button labeled "Move project to production" And I click on the radio labeled "Keep ALL data saved so far" in the dialog box @@ -42,6 +40,7 @@ When I click on the button labeled "Close" in the dialog box ##VERIFY_CODEBOOK When I click on the link labeled "Codebook" Then I should see a table row containing the following values in the codebook table: +| Variable / Field Name | Field Label | Field Attributes (Field Type, Validation, Choices, Calculations, etc.) | | [calculated_field] | Calculated Field | calc | ##VERIFY_LOG @@ -50,17 +49,17 @@ Then I should see a table header and rows including the following values in the | Username | Action | List of Data Changes OR Fields Exported | | test_user1 | Manage/Design | Create project field | -. Scenario: B.6.7.900.200 Creation of calculated field through Data Dictionary upload +#Scenario: B.6.7.900.200 Creation of calculated field through Data Dictionary upload #SETUP -Given I login to REDCap with the user "Test_Admin" -And I create a new project named "B.6.7.900.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button +#Given I login to REDCap with the user "Test_Admin" +#And I create a new project named "B.6.7.900.200" by clicking on "New Project" in the menu bar, selecting "Practice / Just for fun" from the dropdown, choosing "Empty project", and clicking the "Create Project" button #FUNCTIONAL_REQUIREMENT ##ACTION: Upload data dictionary When I click on the link labeled "Dictionary" And I click on the button labeled "Choose File" -And I select the file labeled "Project1xml_DataDictionary.csv" +And I select the file labeled "B67900_DataDictionary.csv" And I click on the button labeled "Upload File" Then I should see "Your document was uploaded successfully and awaits your confirmation below." @@ -70,10 +69,12 @@ Then I should see "Changes Made Successfully!" ##VERIFY_CODEBOOK When I click on the link labeled "Codebook" Then I should see a table row containing the following values in the codebook table: +| Variable / Field Name | Field Label | Field Attributes (Field Type, Validation, Choices, Calculations, etc.) | | [calculated_field] | Calculated Field | calc | +| [calculated_field2]| Calculated Field 2 | calc | ##VERIFY_LOG When I click on the link labeled "Logging" Then I should see a table header and rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | -| test_admin | Manage/Design | Create project field | +| test_admin | Manage/Design | Upload data dictionary | From 1ffc28f3eace9b2ff0e9f870ee52195ab2d1132b Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 29 Dec 2023 12:10:25 -0500 Subject: [PATCH 85/96] Update C.5.22.100 - Report Access.feature Update C.5.22.100 - Report Access.feature --- .../C/Reporting/C.5.22.100 - Report Access.feature | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Feature Tests/C/Reporting/C.5.22.100 - Report Access.feature b/Feature Tests/C/Reporting/C.5.22.100 - Report Access.feature index 97c4db74..6864d1d5 100644 --- a/Feature Tests/C/Reporting/C.5.22.100 - Report Access.feature +++ b/Feature Tests/C/Reporting/C.5.22.100 - Report Access.feature @@ -24,13 +24,13 @@ And I select the dropdown option labeled "TestGroup1" from the dropdown button w And I click on the button labeled "Assign to Data Access Group" in the dialog box Then I should see "Record ID 1 was successfully assigned to a Data Access Group1" -#SETUP: Assign record 1 to DAG1 +#SETUP: Assign record 2 to DAG2 When I click on the link labeled "Record Status Dashboard" And I click on record "2" And I select the dropdown option labeled "Assign to Data Access Group" from the dropdown button with the placeholder text of "Choose action for record" -And I select the dropdown option labeled "TestGroup1" from the dropdown button with the placeholder text of "[No Assignment]" in the dialog box +And I select the dropdown option labeled "TestGroup2" from the dropdown button with the placeholder text of "[No Assignment]" in the dialog box And I click on the button labeled "Assign to Data Access Group" in the dialog box -Then I should see "Record ID 2 was successfully assigned to a Data Access Group1" +Then I should see "Record ID 2 was successfully assigned to a Data Access Group2" #USER_RIGHTS When I click on the link labeled "User Rights" @@ -207,4 +207,4 @@ And I should NOT see record "3" And I should NOT see record "4" ##VERIFY: Edit Report button And I should see a button labeled "Edit Report" -And I logout \ No newline at end of file +And I logout From cb38723d6b4816219f74ac4159c9ca0074ebebfe Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 29 Dec 2023 12:25:33 -0500 Subject: [PATCH 86/96] Update B.2.6.200 - Data Entry Form Access.feature B.2.6.200.100 Data Viewing Rights - fix syntax --- ...B.2.6.200 - Data Entry Form Access.feature | 41 +++++++++++-------- 1 file changed, 24 insertions(+), 17 deletions(-) diff --git a/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature b/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature index 0b823de3..a2e0a35e 100644 --- a/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature +++ b/Feature Tests/B/Assign User Rights/B.2.6.200 - Data Entry Form Access.feature @@ -18,8 +18,9 @@ Then I should see "Project status: Production" When I click on the link labeled "User Rights" And I click on the button labeled "Upload or download users, roles, and assignments" Then I should see "Upload users (CSV)" -Then I should see a dialog containing the following text: "Upload users (CSV)" +When I click on the button labeled "Upload users (CSV)" +Then I should see a dialog containing the following text: "Upload users (CSV)" Given I upload a "csv" format file located at "import_files/user list for project 1.csv", by clicking the button near "Select your CSV" to browse for the file, and clicking the button labeled "Upload" to upload the file Then I should see a dialog containing the following text: "Upload users (CSV) - Confirm" @@ -35,16 +36,16 @@ Then I should see a dialog containing the following text: "SUCCESS!" And I close the popup And I should see a table header and rows including the following values in the table: -|Role name | Username | -| | test_admin | -| | test_user1 | -| | test_user2 | -| | test_user3 | -| | test_user4 | -| 1_FullRights | | | -| 2_Edit_RemoveID| | | -| 3_ReadOnly_Deidentified | | -| 4_NoAccess_Noexport | | +|Role name | Username | +| | test_admin | +| | test_user1 | +| | test_user2 | +| | test_user3 | +| | test_user4 | +| 1_FullRights | | +| 2_Edit_RemoveID | | +| 3_ReadOnly_Deidentified | | +| 4_NoAccess_Noexport | | When I click on the link labeled "test_user1" And I click on the button labeled "Edit user privileges" @@ -59,15 +60,22 @@ And I save changes within the context of User Rights And I click on the button labeled "Logging" Then I should see a table header and rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | -| test_admin | Add user | user = 'test_user1' | - +| test_admin | Update user | user = 'test_user1' | +| test_admin | Add user | user = 'test_user1' | ##ACTION #CROSS-FEATURE B.2.23.100: Verify Logging Filter by user name When I select the "test_admin" option from the Filter by username dropdown field ##VERIFY_LOG #CROSS-FEATURE: Verify Logging Filter by user name Then I should see a table header and rows including the following values in the logging table: | Username | Action | List of Data Changes OR Fields Exported | -| test_admin | Update user | user = 'test_user1' | +| test_admin | Update user | user = 'test_user1' | +| test_admin | Add user | user = 'test_user1' | + +##ACTION #CROSS-FEATURE B.2.23.100: Verify Logging Filter by user name +When I select the "test_user1" option from the Filter by username dropdown field +##VERIFY_LOG #CROSS-FEATURE: Verify Logging Filter by user name +Then I should see "No logged events to display" + And I logout Given I login to REDCap with the user "Test_User1" @@ -86,7 +94,7 @@ Then I should see a dialog containing the following text: "Editing existing user When I set Data Viewing Rights to Read Only for the instrument "Text Validation" And I save changes within the context of User Rights -Then I should see " User "test_user1" was successfully edited" +Then I should see "successfully edited" Given I click on the link labeled "Add / Edit Records" And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page @@ -108,7 +116,7 @@ When I set Data Viewing Rights to View & Edit for the instrument "Text Validatio When I select Data Viewing Rights to View & Edit for the instrument "Text Validation" And I verify Data Viewing Rights to View & Edit with Edit survey responses is checked for the instrument "Survey" And I save changes within the context of User Rights -Then I should see "User "test_user1" was successfully edited" +Then I should see "successfully edited" Given I click on the link labeled "Add / Edit Records" And I select record ID "1" from arm name "Arm 1: Arm 1" on the Add / Edit record page @@ -124,7 +132,6 @@ Then I should see "Record Home Page" ##VERIFY: Edit survey responses for the instrument When I click the bubble for the "Survey" longitudinal instrument on event "Event 3" -And I click on the button labeled "Save & Stay" And I select the dropdown option labeled "Open survey" And I click on the button labeled "Submit" And I click on the button labeled "Close survey" From 7810408ca2b9e1da5d9311cc38ddc837945f5978 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 31 Jan 2024 13:01:42 -0500 Subject: [PATCH 87/96] Create .keep (#7) --- Files/.keep | 1 + 1 file changed, 1 insertion(+) create mode 100644 Files/.keep diff --git a/Files/.keep b/Files/.keep new file mode 100644 index 00000000..8b137891 --- /dev/null +++ b/Files/.keep @@ -0,0 +1 @@ + From cfc884d7ded2ccc2d20760906824f71d32a82f78 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 31 Jan 2024 13:49:00 -0500 Subject: [PATCH 88/96] Create .keep (#8) --- Files/cdisc/.keep | 1 + 1 file changed, 1 insertion(+) create mode 100644 Files/cdisc/.keep diff --git a/Files/cdisc/.keep b/Files/cdisc/.keep new file mode 100644 index 00000000..8b137891 --- /dev/null +++ b/Files/cdisc/.keep @@ -0,0 +1 @@ + From 6bc75efab2c8c79e94ae1d3464f3b31e5cfc50fe Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 31 Jan 2024 13:50:45 -0500 Subject: [PATCH 89/96] Create .keep (#9) --- Files/dictionaries/.keep | 1 + 1 file changed, 1 insertion(+) create mode 100644 Files/dictionaries/.keep diff --git a/Files/dictionaries/.keep b/Files/dictionaries/.keep new file mode 100644 index 00000000..8b137891 --- /dev/null +++ b/Files/dictionaries/.keep @@ -0,0 +1 @@ + From 0524c082fa90b5ebe4fa9677d3cf43d25d2e28f5 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 31 Jan 2024 13:56:19 -0500 Subject: [PATCH 90/96] Create .keep (#10) --- Files/import/.keep | 1 + 1 file changed, 1 insertion(+) create mode 100644 Files/import/.keep diff --git a/Files/import/.keep b/Files/import/.keep new file mode 100644 index 00000000..8b137891 --- /dev/null +++ b/Files/import/.keep @@ -0,0 +1 @@ + From 49e6dee92fd23a12b8dd3386ba5f38e80190a752 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 2 Feb 2024 13:22:36 -0500 Subject: [PATCH 91/96] Add files via upload --- Files/cdisc/Consent.xml | 152 ++++ Files/cdisc/Project418.xml | 1480 ++++++++++++++++++++++++++++++++++ Files/cdisc/Project_1.xml | 919 +++++++++++++++++++++ Files/cdisc/Project_3.14.xml | 629 +++++++++++++++ Files/cdisc/Project_3.16.xml | 256 ++++++ Files/cdisc/Project_4.8.xml | 857 ++++++++++++++++++++ Files/cdisc/Project_4.9.xml | 869 ++++++++++++++++++++ Files/cdisc/Project_5.21.xml | 315 ++++++++ 8 files changed, 5477 insertions(+) create mode 100644 Files/cdisc/Consent.xml create mode 100644 Files/cdisc/Project418.xml create mode 100644 Files/cdisc/Project_1.xml create mode 100644 Files/cdisc/Project_3.14.xml create mode 100644 Files/cdisc/Project_3.16.xml create mode 100644 Files/cdisc/Project_4.8.xml create mode 100644 Files/cdisc/Project_4.9.xml create mode 100644 Files/cdisc/Project_5.21.xml diff --git a/Files/cdisc/Consent.xml b/Files/cdisc/Consent.xml new file mode 100644 index 00000000..f2afd98f --- /dev/null +++ b/Files/cdisc/Consent.xml @@ -0,0 +1,152 @@ + + + + + Consent + This file contains the metadata, events, and data for REDCap project "Consent". + Consent + 1 + [user-dag-label] + + 1 + 1 + email + 1 + 0 + 0 + 1 + + 0 + 0 + + + + 0 + REDCap Secure Messaging + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Data Access Group + + + Survey Identifier + + + Survey Timestamp + + + Survey Timestamp + + + Name + + + Name + + + Email + + + DOB + + + Signature + + + Signature + + + Signature + + + Signature + + + Signature + + + Complete? + + + + Incomplete + Unverified + Complete + + + + + + \ No newline at end of file diff --git a/Files/cdisc/Project418.xml b/Files/cdisc/Project418.xml new file mode 100644 index 00000000..b8998969 --- /dev/null +++ b/Files/cdisc/Project418.xml @@ -0,0 +1,1480 @@ + + + + + project_4.18.xml + This file contains the metadata, events, and data for REDCap project "project_4.18.xml". + project_4.18.xml + 1 + [user-dag-label] + + 1 + 1 + email + 1 + 0 + 0 + 1 + + 0 + 0 + + + NI, No information + 0 + REDCap Secure Messaging + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Data Access Group + + + Survey Identifier + + + Name + + + Email + + + Complete? + + + + Name + + + Text box + + + Text2 + + + radio + + + + Notes box + + + Multiple Choice Dropdown Manual + + + + Multiple Choice dropdown Auto + + + + Radio Button Auto + + + + Radio Button Manual + + + + Branching + + + Checkbox + + + + Checkbox + + + + Checkbox + + + + Calc Test + + + Calculated Field + + + Signature + + + File Upload + + + Descriptive Text with File + + + Descriptive Text + + + Required + + + Identifier + + + Identifier + + + Edit Field + + + date YMD + + + date MDY + + + date DMY + + + time HH:MM:SS + + + time HH:M + + + time MM:SS + + + datetime YMD HMSS + + + datetime YMD HM + + 2023-08-01 01:01 + The value you provided is outside the suggested range (2023-08-01 01:01 - 2023-08-31 01:59). This value is admissible, but you may wish to double check it. + + + 2023-08-31 01:59 + The value you provided is outside the suggested range (2023-08-01 01:01 - 2023-08-31 01:59). This value is admissible, but you may wish to double check it. + + + + datetime MDY HMSS + + + datetime DMY HMSS + + + Integer + + 0 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + 2 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + + Numbers + + 0 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + 2 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + + Numbers 1 decimal place - period as decimal + + 0.0 + The value you provided is outside the suggested range (0.0 - 3.0). This value is admissible, but you may wish to double check it. + + + 3.0 + The value you provided is outside the suggested range (0.0 - 3.0). This value is admissible, but you may wish to double check it. + + + + Numbers 1 decimal place - comma as decimal + + 0,0 + The value you provided is outside the suggested range (0,0 - 3,0). This value is admissible, but you may wish to double check it. + + + 3,0 + The value you provided is outside the suggested range (0,0 - 3,0). This value is admissible, but you may wish to double check it. + + + + Letters only + + + MRN (10 Digits) + + + MRN (generic) + + + Social Security Number (US) + + + Phone (North America) + + + Phone (Australia) + + + Phone (UK) + + + Zipcode (US) + + + Postal code 5 (France) + + + Postal Code (Australia) + + + Postal Code (Canada) + + + Complete? + + + + Survey Timestamp + + + Name + + + Email + + + Complete? + + + + Survey Timestamp + + + Name + + + Email + + + DOB + + + Signature + + + Complete? + + + + Testing dd upload + + + Complete? + + + + Incomplete + Unverified + Complete + + + Choice99 + Choice100 + Choice101 + + + DDChoice5 + DDChoice6 + DDChoice7 + + + DDChoice1 + DDChoice2 + DDChoice3 + + + Choice1 + Choice2 + Choice.3 + + + Choice99 + Choice100 + Choice101 + + + Checked + Unchecked + + + Checked + Unchecked + + + Checked + Unchecked + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Files/cdisc/Project_1.xml b/Files/cdisc/Project_1.xml new file mode 100644 index 00000000..fb5f7119 --- /dev/null +++ b/Files/cdisc/Project_1.xml @@ -0,0 +1,919 @@ + + + + + project_1.xml + This file contains the metadata, events, and data for REDCap project "project_1.xml". + project_1.xml + 1 + [user-dag-label] + + 1 + 1 + email + 1 + 0 + 0 + 1 + + 0 + 0 + + + + 0 + REDCap Secure Messaging + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Data Access Group + + + Survey Identifier + + + Name + + + Email + + + Complete? + + + + Name + + + Text box + + + Text2 + + + radio + + + + Notes box + + + Multiple Choice Dropdown Manual + + + + Multiple Choice dropdown Auto + + + + Radio Button Auto + + + + Radio Button Manual + + + + Checkbox + + + + Checkbox + + + + Checkbox + + + + Calc Test + + + Calculated Field + + + Signature + + + File Upload + + + Descriptive Text with File + + + Descriptive Text + + + Required + + + Identifier + + + Identifier + + + Edit Field + + + date YMD + + + date MDY + + + date DMY + + + time HH:MM:SS + + + time HH:M + + + time MM:SS + + + datetime YMD HMSS + + + datetime YMD HM + + 2023-08-01 01:01 + The value you provided is outside the suggested range (2023-08-01 01:01 - 2023-08-31 01:59). This value is admissible, but you may wish to double check it. + + + 2023-08-31 01:59 + The value you provided is outside the suggested range (2023-08-01 01:01 - 2023-08-31 01:59). This value is admissible, but you may wish to double check it. + + + + datetime MDY HMSS + + + datetime DMY HMSS + + + Integer + + 0 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + 2 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + + Numbers + + 0 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + 2 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + + Numbers 1 decimal place - period as decimal + + 0.0 + The value you provided is outside the suggested range (0.0 - 3.0). This value is admissible, but you may wish to double check it. + + + 3.0 + The value you provided is outside the suggested range (0.0 - 3.0). This value is admissible, but you may wish to double check it. + + + + Numbers 1 decimal place - comma as decimal + + 0,0 + The value you provided is outside the suggested range (0,0 - 3,0). This value is admissible, but you may wish to double check it. + + + 3,0 + The value you provided is outside the suggested range (0,0 - 3,0). This value is admissible, but you may wish to double check it. + + + + Letters only + + + MRN (10 Digits) + + + MRN (generic) + + + Social Security Number (US) + + + Phone (North America) + + + Phone (Australia) + + + Phone (UK) + + + Zipcode (US) + + + Postal code 5 (France) + + + Postal Code (Australia) + + + Postal Code (Canada) + + + Complete? + + + + Survey Timestamp + + + Name + + + Email + + + Complete? + + + + Survey Timestamp + + + Name + + + Email + + + DOB + + + Signature + + + Complete? + + + + Incomplete + Unverified + Complete + + + Choice99 + Choice100 + Choice101 + + + DDChoice5 + DDChoice6 + DDChoice7 + + + DDChoice1 + DDChoice2 + DDChoice3 + + + Choice1 + Choice2 + Choice.3 + + + Choice99 + Choice100 + Choice101 + + + Checked + Unchecked + + + Checked + Unchecked + + + Checked + Unchecked + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Files/cdisc/Project_3.14.xml b/Files/cdisc/Project_3.14.xml new file mode 100644 index 00000000..3a7aa31f --- /dev/null +++ b/Files/cdisc/Project_3.14.xml @@ -0,0 +1,629 @@ + + + + + 3.14 XML UPDATE + This file contains the metadata, events, and data for REDCap project "3.14 XML UPDATE". + 3.14 XML UPDATE + 1 + [user-dag-label] + + 1 + 1 + email + 1 + 0 + 0 + 1 + + 0 + 0 + + + + 0 + REDCap Secure Messaging + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Data Access Group + + + Name + + + Email + + + Complete? + + + + radio + + + + Multiple Choice Dropdown Manual + + + + Notes box 2 + + + Checkbox + + + + Checkbox + + + + Checkbox + + + + Signature + + + File Upload + + + True/False + + + + Yes/No + + + + Slider + + + Required + + + Calc Test + + + date YMD + + + time HH:MM:SS + + + datetime YMD HMSS + + + Complete? + + + + Name + + + Email + + + Complete? + + + + Name + + + Email + + + DOB + + + Signature + + + Complete? + + + + Testing dd upload + + + Complete? + + + + Name + + + Email + + + Complete? + + + + Incomplete + Unverified + Complete + + + Choice99 + Choice100 + Choice101 + + + DDChoice5 + DDChoice7 + DDChoice6 + + + Checked + Unchecked + + + Checked + Unchecked + + + Checked + Unchecked + + + True + False + + + Yes + No + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Files/cdisc/Project_3.16.xml b/Files/cdisc/Project_3.16.xml new file mode 100644 index 00000000..606a4f28 --- /dev/null +++ b/Files/cdisc/Project_3.16.xml @@ -0,0 +1,256 @@ + + + + + 16 Data Import PM Temp + This file contains the metadata, events, and data for REDCap project "16 Data Import PM Temp". + 16 Data Import PM Temp + 1 + + + 0 + 0 + email + 0 + + + + 0 + + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Name + + + Email + + + Complete? + + + + Name + + + Date of birth + + + Role + + + Notes + + + Calculated Field + + + Multiple Choice dropdown Auto + + + + Multiple Choice Dropdown Manual + + + + Radio Button Auto + + + + Radio Button Manual + + + + Checkbox + + + + Checkbox + + + + Checkbox + + + + Signature + + + File Upload + + + Descriptive Text with File + + + + Descriptive Text + + + Required Integer + + + Identifier SSN + + + Phone Number + + + Slider + + 10 + The value you provided is outside the suggested range (no limit - 10). This value is admissible, but you may wish to double check it. + + + + Date Time hh:mm + + + Date Time hh:mm:ss + + + Complete? + + + + Form with descriptive text field and no data. + + + Complete? + + + + Phone (UK) + + + Complete? + + + + Incomplete + Unverified + Complete + + + DDChoice1 + DDChoice2 + DDChoice3 + + + DDChoice5 + DDChoice6 + DDChoice7 + + + Choice1 + Choice2 + Choice.3 + + + Choice99 + Choice100 + Choice101 + + + Checked + Unchecked + + + Checked + Unchecked + + + Checked + Unchecked + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + + \ No newline at end of file diff --git a/Files/cdisc/Project_4.8.xml b/Files/cdisc/Project_4.8.xml new file mode 100644 index 00000000..2af5af5f --- /dev/null +++ b/Files/cdisc/Project_4.8.xml @@ -0,0 +1,857 @@ + + + + + B.4.8.200_CREATE_NEW_XML + This file contains the metadata, events, and data for REDCap project "B.4.8.200_CREATE_NEW_XML". + B.4.8.200_CREATE_NEW_XML + 1 + [user-dag-label] + + 1 + 1 + email + 1 + 0 + 0 + 1 + + 0 + 0 + + + + 0 + REDCap Secure Messaging + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Data Access Group + + + Survey Identifier + + + Name + + + Email + + + Complete? + + + + radio + + + + Multiple Choice Dropdown Manual + + + + Calc Test + + + Calculated Field + + + Notes box 2 + + + Text BoxNotes Bbox + + + Name + + + Text2 + + + Text box + + + Notes box + + + Calculated Field + + + Multiple Choice dropdown Auto + + + + Multiple Choice Dropdown Manual + + + + Radio Button Auto + + + + Radio Button Manual + + + + Checkbox + + + + Checkbox + + + + Checkbox + + + + Signature + + + File Upload + + + Descriptive Text with File + + + Descriptive Text + + + Required + + + Identifier + + + Identifier + + + Edit Field + + + date YMD + + 2023-08-01 + The value you provided is outside the suggested range (2023-08-01 - 2023-08-31). This value is admissible, but you may wish to double check it. + + + 2023-08-31 + The value you provided is outside the suggested range (2023-08-01 - 2023-08-31). This value is admissible, but you may wish to double check it. + + + + Datetime + + 2023-09-01 01:01 + The value you provided is outside the suggested range (2023-09-01 01:01 - 2023-09-30 01:59). This value is admissible, but you may wish to double check it. + + + 2023-09-30 01:59 + The value you provided is outside the suggested range (2023-09-01 01:01 - 2023-09-30 01:59). This value is admissible, but you may wish to double check it. + + + + Datetime YMD HMSS + + 2023-09-01 11:01:01 + The value you provided is outside the suggested range (2023-09-01 11:01:01 - 2023-09-30 11:01:01). This value is admissible, but you may wish to double check it. + + + 2023-09-30 11:01:01 + The value you provided is outside the suggested range (2023-09-01 11:01:01 - 2023-09-30 11:01:01). This value is admissible, but you may wish to double check it. + + + + Integer + + 1 + The value you provided is outside the suggested range (1 - 100). This value is admissible, but you may wish to double check it. + + + 100 + The value you provided is outside the suggested range (1 - 100). This value is admissible, but you may wish to double check it. + + + + Number + + 1 + The value you provided is outside the suggested range (1 - 5). This value is admissible, but you may wish to double check it. + + + 5 + The value you provided is outside the suggested range (1 - 5). This value is admissible, but you may wish to double check it. + + + + Number Decimal + + 1.0 + The value you provided is outside the suggested range (1.0 - 5.0). This value is admissible, but you may wish to double check it. + + + 5.0 + The value you provided is outside the suggested range (1.0 - 5.0). This value is admissible, but you may wish to double check it. + + + + Number Comma + + 1,0 + The value you provided is outside the suggested range (1,0 - 2,0). This value is admissible, but you may wish to double check it. + + + 2,0 + The value you provided is outside the suggested range (1,0 - 2,0). This value is admissible, but you may wish to double check it. + + + + Time HH:MM + + 08:05 + The value you provided is outside the suggested range (08:05 - 23:00). This value is admissible, but you may wish to double check it. + + + 23:00 + The value you provided is outside the suggested range (08:05 - 23:00). This value is admissible, but you may wish to double check it. + + + + Time MM:SS + + 02:01 + The value you provided is outside the suggested range (02:01 - 59:00). This value is admissible, but you may wish to double check it. + + + 59:00 + The value you provided is outside the suggested range (02:01 - 59:00). This value is admissible, but you may wish to double check it. + + + + Time HH:MM:SS + + 08:01:01 + The value you provided is outside the suggested range (08:01:01 - 23:00:00). This value is admissible, but you may wish to double check it. + + + 23:00:00 + The value you provided is outside the suggested range (08:01:01 - 23:00:00). This value is admissible, but you may wish to double check it. + + + + Complete? + + + + Survey Timestamp + + + Name + + + Email + + + Complete? + + + + Survey Timestamp + + + Name + + + Email + + + DOB + + + Signature + + + Complete? + + + + Testing dd upload + + + Complete? + + + + Name + + + Email + + + Complete? + + + + Incomplete + Unverified + Complete + + + Choice99 + Choice100 + Choice101 + + + DDChoice5 + DDChoice7 + DDChoice6 + + + DDChoice1 + DDChoice2 + DDChoice3 + + + DDChoice5 + DDChoice6 + DDChoice7 + + + Choice1 + Choice2 + Choice.3 + + + Choice99 + Choice100 + Choice101 + + + Checked + Unchecked + + + Checked + Unchecked + + + Checked + Unchecked + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Files/cdisc/Project_4.9.xml b/Files/cdisc/Project_4.9.xml new file mode 100644 index 00000000..40cf6244 --- /dev/null +++ b/Files/cdisc/Project_4.9.xml @@ -0,0 +1,869 @@ + + + + + B.4.9.100.100 + This file contains the metadata, events, and data for REDCap project "B.4.9.100.100". + B.4.9.100.100 + 1 + [user-dag-label] + + 1 + 1 + email + 1 + 0 + 0 + 1 + + 0 + 0 + + + + 0 + REDCap Secure Messaging + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Data Access Group + + + Survey Identifier + + + Survey Timestamp + + + Survey Timestamp + + + Name + + + Text box + + + Text2 + + + radio + + + + Notes box + + + Multiple Choice Dropdown Manual + + + + Multiple Choice dropdown Auto + + + + Radio Button Auto + + + + Radio Button Manual + + + + Checkbox + + + + Checkbox + + + + Checkbox + + + + Calc Test + + + Calculated Field + + + Signature + + + File Upload + + + Descriptive Text with File + + + Descriptive Text + + + Required + + + Identifier + + + Identifier + + + Edit Field + + + date YMD + + + date MDY + + + date DMY + + + time HH:MM:SS + + + time HH:M + + + time MM:SS + + + datetime YMD HMSS + + + datetime YMD HM + + 2023-08-01 01:01 + The value you provided is outside the suggested range (2023-08-01 01:01 - 2023-08-31 01:59). This value is admissible, but you may wish to double check it. + + + 2023-08-31 01:59 + The value you provided is outside the suggested range (2023-08-01 01:01 - 2023-08-31 01:59). This value is admissible, but you may wish to double check it. + + + + datetime MDY HMSS + + + datetime DMY HMSS + + + Integer + + 0 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + 2 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + + Numbers + + 0 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + 2 + The value you provided is outside the suggested range (0 - 2). This value is admissible, but you may wish to double check it. + + + + Numbers 1 decimal place - period as decimal + + 0.0 + The value you provided is outside the suggested range (0.0 - 3.0). This value is admissible, but you may wish to double check it. + + + 3.0 + The value you provided is outside the suggested range (0.0 - 3.0). This value is admissible, but you may wish to double check it. + + + + Numbers 1 decimal place - comma as decimal + + 0,0 + The value you provided is outside the suggested range (0,0 - 3,0). This value is admissible, but you may wish to double check it. + + + 3,0 + The value you provided is outside the suggested range (0,0 - 3,0). This value is admissible, but you may wish to double check it. + + + + Letters only + + + MRN (10 Digits) + + + MRN (generic) + + + Social Security Number (US) + + + Phone (North America) + + + Phone (Australia) + + + Phone (UK) + + + Zipcode (US) + + + Postal code 5 (France) + + + Postal Code (Australia) + + + Postal Code (Canada) + + + Complete? + + + + Survey Timestamp + + + Name + + + Email + + + Complete? + + + + Survey Timestamp + + + Name + + + Email + + + DOB + + + Signature + + + Complete? + + + + Choice99 + Choice100 + Choice101 + + + DDChoice5 + DDChoice6 + DDChoice7 + + + DDChoice1 + DDChoice2 + DDChoice3 + + + Choice1 + Choice2 + Choice.3 + + + Choice99 + Choice100 + Choice101 + + + Checked + Unchecked + + + Checked + Unchecked + + + Checked + Unchecked + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + Incomplete + Unverified + Complete + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Files/cdisc/Project_5.21.xml b/Files/cdisc/Project_5.21.xml new file mode 100644 index 00000000..8fe017c0 --- /dev/null +++ b/Files/cdisc/Project_5.21.xml @@ -0,0 +1,315 @@ + + + + + Project_5.21 + This file contains the metadata, events, and data for REDCap project "Project_5.21". + Project_5.21 + 1 + + + 0 + 1 + + 1 + 0 + 0 + 1 + + 0 + 0 + + + + 0 + + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Data Access Group + + + Survey Identifier + + + Survey Timestamp + + + Survey Timestamp + + + Name + + + Text box + + + radio + + + + Notes box + + + Identifier + + + Identifier 2 + + + date YMD + + + datetime YMD HMSS + + + Complete? + + + + Choice99 + Choice100 + Choice101 + + + Incomplete + Unverified + Complete + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file From 4328dd512d5bd864c7985c1d84cd80603fe178ef Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 2 Feb 2024 13:23:01 -0500 Subject: [PATCH 92/96] Add files via upload --- Files/cdisc/B.3.16.600Project.xml | 263 ++++++++++++++++++++++++++++++ 1 file changed, 263 insertions(+) create mode 100644 Files/cdisc/B.3.16.600Project.xml diff --git a/Files/cdisc/B.3.16.600Project.xml b/Files/cdisc/B.3.16.600Project.xml new file mode 100644 index 00000000..3e3980cd --- /dev/null +++ b/Files/cdisc/B.3.16.600Project.xml @@ -0,0 +1,263 @@ + + + + + P3 600 test + This file contains the metadata, events, and data for REDCap project "P3 600 test". + P3 600 test + 1 + [user-dag-label] + + 1 + 1 + email + 1 + 0 + 0 + 1 + + 0 + 0 + + + + 0 + REDCap Secure Messaging + ALL + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Record ID + + + Survey Identifier + + + Survey Timestamp + + + Survey Timestamp + + + Name + + + Text box + + + radio + + + + Notes box + + + Identifier + + + Identifier 2 + + + date YMD + + + datetime YMD HMSS + + + Complete? + + + + Choice99 + Choice100 + Choice101 + + + Incomplete + Unverified + Complete + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file From aa2cf93b3d6ef35ad763eec08645d174120de893 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 2 Feb 2024 13:23:56 -0500 Subject: [PATCH 93/96] Add files via upload --- .../dictionaries/B67800200_DataDictionary.csv | 4 ++ Files/dictionaries/B67900_DataDictionary.csv | 4 ++ .../Project1xml_DataDictionary.csv | 55 +++++++++++++++++++ 3 files changed, 63 insertions(+) create mode 100644 Files/dictionaries/B67800200_DataDictionary.csv create mode 100644 Files/dictionaries/B67900_DataDictionary.csv create mode 100644 Files/dictionaries/Project1xml_DataDictionary.csv diff --git a/Files/dictionaries/B67800200_DataDictionary.csv b/Files/dictionaries/B67800200_DataDictionary.csv new file mode 100644 index 00000000..15c86c9b --- /dev/null +++ b/Files/dictionaries/B67800200_DataDictionary.csv @@ -0,0 +1,4 @@ +Variable / Field Name,Form Name,Section Header,Field Type,Field Label,"Choices, Calculations, OR Slider Labels",Field Note,Text Validation Type OR Show Slider Number,Text Validation Min,Text Validation Max,Identifier?,Branching Logic (Show field only if...),Required Field?,Custom Alignment,Question Number (surveys only),Matrix Group Name,Matrix Ranking?,Field Annotation +record_id,form_1,,text,Record ID,,,,,,,,,,,,, +notesbox,form_1,,notes,Notes Box,,,,,,,,,,,,, +notesbox2,form_1,,notes,Notes box 2,,,,,,,,,,,,, diff --git a/Files/dictionaries/B67900_DataDictionary.csv b/Files/dictionaries/B67900_DataDictionary.csv new file mode 100644 index 00000000..d943d5d9 --- /dev/null +++ b/Files/dictionaries/B67900_DataDictionary.csv @@ -0,0 +1,4 @@ +Variable / Field Name,Form Name,Section Header,Field Type,Field Label,"Choices, Calculations, OR Slider Labels",Field Note,Text Validation Type OR Show Slider Number,Text Validation Min,Text Validation Max,Identifier?,Branching Logic (Show field only if...),Required Field?,Custom Alignment,Question Number (surveys only),Matrix Group Name,Matrix Ranking?,Field Annotation +record_id,form_1,,text,Record ID,,,,,,,,,,,,, +calculated_field,form_1,,calc,Calculated Field,3*2,,,,,,,,,,,, +calculated_field2,form_1,,calc,Calculated Field 2,4*5,,,,,,,,,,,, diff --git a/Files/dictionaries/Project1xml_DataDictionary.csv b/Files/dictionaries/Project1xml_DataDictionary.csv new file mode 100644 index 00000000..c2d47ccb --- /dev/null +++ b/Files/dictionaries/Project1xml_DataDictionary.csv @@ -0,0 +1,55 @@ +"Variable / Field Name","Form Name","Section Header","Field Type","Field Label","Choices, Calculations, OR Slider Labels","Field Note","Text Validation Type OR Show Slider Number","Text Validation Min","Text Validation Max",Identifier?,"Branching Logic (Show field only if...)","Required Field?","Custom Alignment","Question Number (surveys only)","Matrix Group Name","Matrix Ranking?","Field Annotation" +record_id,text_validation,,text,"Record ID",,,,,,,,,,,,, +name,text_validation,,text,Name,,,,,,,,,,,,," @DEFAULT=""Name """ +email,text_validation,,text,Email,,,email,,,,,,,,,," @DEFAULT=""email@test.edu""" +ptname,data_types,,text,Name,,,,,,,,,,,,," @DEFAULT=""[name]""" +textbox,data_types,,text,"Text box",,,,,,,,,,,,," @DEFAULT=""text box""" +text2,data_types,,text,Text2,,,,,,,,,,,,," @DEFAULT=""text2""" +radio,data_types,,radio,radio,"9..9, Choice99 | 100, Choice100 | 101, Choice101",,,,,,,,,,,, +notesbox,data_types,,notes,"Notes box",,,,,,,,,,,,," @DEFAULT=""note box""" +multiple_dropdown_manual,data_types,,dropdown,"Multiple Choice Dropdown Manual","5, DDChoice5 | 7, DDChoice6 | 6, DDChoice7",,,,,,,,,,,," @DEFAULT=""5""" +multiple_dropdown_auto,data_types,,dropdown,"Multiple Choice dropdown Auto","1, DDChoice1 | 2, DDChoice2 | 3, DDChoice3",,,,,,,,,,,," @DEFAULT=""1""" +multiple_radio_auto,data_types,,radio,"Radio Button Auto","1, Choice1 | 2, Choice2 | 3, Choice.3",,,,,,,,,,,," @DEFAULT=""1""" +radio_button_manual,data_types,,radio,"Radio Button Manual","9..9, Choice99 | 100, Choice100 | 101, Choice101",,,,,,,,,,,," @DEFAULT=""100""" +checkbox,data_types,,checkbox,Checkbox,"1, Checkbox1 | 2, Checkbox2 | 3, Checkbox3",,,,,,,,,,,," @DEFAULT=""1""" +calc_test,data_types,,calc,"Calc Test",3*2,,,,,,,,,,,, +calculated_field,data_types,,calc,"Calculated Field",3*2,,,,,,,,,,,, +signature,data_types,,file,Signature,,,signature,,,,,,,,,, +file_upload,data_types,,file,"File Upload",,,,,,,,,,,,, +descriptive_text_file,data_types," ",descriptive,"Descriptive Text with File",,,,,,,,,,,,, +descriptive_text,data_types,,descriptive,"Descriptive Text",,,,,,,,,,,,, +required,data_types,,text,Required,,,,,,,,y,,,,," @DEFAULT=""required""" +identifier,data_types,,text,Identifier,,,,,,y,,,,,,," @DEFAULT=""PHI""" +identifier_2,data_types,,text,Identifier,,,,,,y,,,,,,," @DEFAULT=""PHI2""" +edit_field,data_types,,text,"Edit Field",,,,,,,,,,,,," @DEFAULT=""Edit Field""" +date_ymd,data_types,Date,text,"date YMD",,,date_ymd,,,,,,,,,," @TODAY" +date_mdy,data_types,,text,"date MDY",,,date_mdy,,,,,,,,,," @TODAY" +date_dmy,data_types,,text,"date DMY",,,date_dmy,,,,,,,,,," @TODAY" +time_hhmmss,data_types,Time,text,"time HH:MM:SS",,,time_hh_mm_ss,,,,,,,,,," @NOW" +time_hhmm,data_types,,text,"time HH:M",,,time,,,,,,,,,," @NOW" +time_mmss,data_types,,text,"time MM:SS",,,time_mm_ss,,,,,,,,,," @NOW" +datetime_ymd_hmss,data_types,DateTime,text,"datetime YMD HMSS",,,datetime_seconds_ymd,,,,,,,,,," @NOW" +datetime_ymd_hm,data_types,,text,"datetime YMD HM",,,datetime_ymd,"2023-08-01 01:01","2023-08-31 01:59",,,,,,,," @DEFAULT='2023-08-01 01:02'" +datetime_mdy_hmss,data_types,,text,"datetime MDY HMSS",,,datetime_seconds_mdy,,,,,,,,,," @NOW" +datetime_dmy_hmss,data_types,,text,"datetime DMY HMSS",,,datetime_seconds_dmy,,,,,,,,,," @NOW" +integer,data_types,"Integer, number, and letters",text,"Integer ",,,integer,0,2,,,,,,,," @DEFAULT='1'" +number,data_types,,text,Numbers,,,number,0,2,,,,,,,," @DEFAULT='1'" +number_1_period,data_types,,text,"Numbers 1 decimal place - period as decimal ",,,number_1dp,0.0,3.0,,,,,,,," @DEFAULT='2.2'" +number_1_comma,data_types,,text,"Numbers 1 decimal place - comma as decimal ",,,number_1dp_comma_decimal,"0,0","3,0",,,,,,,," @DEFAULT='2,0'" +letters,data_types,,text,"Letters only",,,alpha_only,,,,,,,,,," @DEFAULT='ABCxyz'" +mrn_10_digits,data_types,,text,"MRN (10 Digits)",,,mrn_10d,,,,,,,,,," @DEFAULT='1234567890'" +mrn,data_types,,text,"MRN (generic)",,,mrn_generic,,,,,,,,,," @DEFAULT='A123456789'" +ssn,data_types,,text,"Social Security Number (US)",,,ssn,,,,,,,,,," @DEFAULT='123-12-1234'" +phone_north_america,data_types,Phone,text,"Phone (North America)",,,phone,,,,,,,,,," @DEFAULT='555-867-5309'" +phone_australia,data_types,,text,"Phone (Australia)",,,phone_australia,,,,,,,,,," @DEFAULT='(02) 1234 5678'" +phone_uk,data_types,,text,"Phone (UK)",,,phone_uk,,,,,,,,,," @DEFAULT='+44 7911 123456'" +zipcode_us,data_types,"Postal codes",text,"Zipcode (US)",,,zipcode,,,,,,,,,," @DEFAULT='90210'" +postal_5,data_types,,text,"Postal code 5 (France)",,,postalcode_french,,,,,,,,,," @DEFAULT='69008'" +postal_code_australia,data_types,,text,"Postal Code (Australia)",,,postalcode_australia,,,,,,,,,," @DEFAULT='5000'" +postal_code_canada,data_types,,text,"Postal Code (Canada)",,,postalcode_canada,,,,,,,,,," @DEFAULT='A0A 0A0'" +name_survey,survey,,text,Name,,,,,,,,,,,,," @DEFAULT=""Name """ +email_survey,survey,,text,Email,,,email,,,,,,,,,," @DEFAULT=""email@test.edu""" +name_consent,consent,,text,Name,,,,,,,,,,,,," @DEFAULT=""Name """ +email_consent,consent,,text,Email,,,email,,,,,,,,,," @DEFAULT=""email@test.edu""" +dob,consent,,text,DOB,,,date_ymd,,,,,,,,,," @TODAY" +signature_consent,consent,,file,"Signature ",,,signature,,,,,,,,,, From 483162ce71c7f72b8b4002e4de480c7547f0e007 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Fri, 2 Feb 2024 13:24:52 -0500 Subject: [PATCH 94/96] Add files via upload --- Files/import/B.3.16.1000_New Record.csv | 16 ++++++++++++ Files/import/B.3.16.1300_DataImport_Dag.csv | 4 +++ Files/import/B.3.16.1300_DataImport_Rows.csv | 4 +++ .../import/B.3.16.400_DataImport_Rows Bad.csv | 4 +++ .../B.3.16.400_DataImport_Rows Corrected.csv | 4 +++ .../import/B.3.16.500_DataImport_Rows Bad.csv | 4 +++ .../B.3.16.500_DataImport_Rows Corrected.csv | 4 +++ Files/import/B.3.16.500_DataImport_Rows.csv | 4 +++ Files/import/B.3.16.600_DataImport.csv | 7 +++++ .../B.3.16.900.100_ImportChangedLocked.csv | 2 ++ .../B.3.16.900.100_ImportChangedUnlocked.csv | 2 ++ Files/import/B3161200100_ACCURATE.csv | 6 +++++ ...B316200100_ImportTemplate_ImportRecord.csv | 2 ++ ...100_ImportTemplate_ImportRecord_Column.csv | 26 +++++++++++++++++++ Files/import/B316800100_WOUT_REPEATS.csv | 2 ++ Files/import/B316800100_W_REPEATS.csv | 3 +++ Files/import/instrument designation.csv | 14 ++++++++++ Files/import/testusers_bulk_upload.csv | 5 ++++ Files/import/user list for project 1.csv | 6 +++++ 19 files changed, 119 insertions(+) create mode 100644 Files/import/B.3.16.1000_New Record.csv create mode 100644 Files/import/B.3.16.1300_DataImport_Dag.csv create mode 100644 Files/import/B.3.16.1300_DataImport_Rows.csv create mode 100644 Files/import/B.3.16.400_DataImport_Rows Bad.csv create mode 100644 Files/import/B.3.16.400_DataImport_Rows Corrected.csv create mode 100644 Files/import/B.3.16.500_DataImport_Rows Bad.csv create mode 100644 Files/import/B.3.16.500_DataImport_Rows Corrected.csv create mode 100644 Files/import/B.3.16.500_DataImport_Rows.csv create mode 100644 Files/import/B.3.16.600_DataImport.csv create mode 100644 Files/import/B.3.16.900.100_ImportChangedLocked.csv create mode 100644 Files/import/B.3.16.900.100_ImportChangedUnlocked.csv create mode 100644 Files/import/B3161200100_ACCURATE.csv create mode 100644 Files/import/B316200100_ImportTemplate_ImportRecord.csv create mode 100644 Files/import/B316200100_ImportTemplate_ImportRecord_Column.csv create mode 100644 Files/import/B316800100_WOUT_REPEATS.csv create mode 100644 Files/import/B316800100_W_REPEATS.csv create mode 100644 Files/import/instrument designation.csv create mode 100644 Files/import/testusers_bulk_upload.csv create mode 100644 Files/import/user list for project 1.csv diff --git a/Files/import/B.3.16.1000_New Record.csv b/Files/import/B.3.16.1000_New Record.csv new file mode 100644 index 00000000..3981191b --- /dev/null +++ b/Files/import/B.3.16.1000_New Record.csv @@ -0,0 +1,16 @@ +record_id,redcap_event_name,redcap_repeat_instrument,redcap_repeat_instance,redcap_data_access_group,redcap_survey_identifier,name,email,text_validation_complete,ptname,textbox,text2,radio,notesbox,multiple_dropdown_manual,multiple_dropdown_auto,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,calc_test,calculated_field,signature,file_upload,required,identifier,identifier_2,edit_field,date_ymd,date_mdy,date_dmy,time_hhmmss,time_hhmm,time_mmss,datetime_ymd_hmss,datetime_ymd_hm,datetime_mdy_hmss,datetime_dmy_hmss,integer,number,number_1_period,number_1_comma,letters,mrn_10_digits,mrn,ssn,phone_north_america,phone_australia,phone_uk,zipcode_us,postal_5,postal_code_australia,postal_code_canada,data_types_complete,survey_timestamp,name_survey,email_survey,survey_complete,consent_timestamp,name_consent,email_consent,dob,signature_consent,consent_complete +5,event_1_arm_1,,,,,,email@test.edu,0,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,Name ,email@test.edu,4/14/23,,2 +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, +,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, \ No newline at end of file diff --git a/Files/import/B.3.16.1300_DataImport_Dag.csv b/Files/import/B.3.16.1300_DataImport_Dag.csv new file mode 100644 index 00000000..ec0c4c2a --- /dev/null +++ b/Files/import/B.3.16.1300_DataImport_Dag.csv @@ -0,0 +1,4 @@ +record_id,redcap_data_access_group,name,email,text_validation_complete,ptname,bdate,role,notesbox,multiple_dropdown_auto,multiple_dropdown_manual,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,required,identifier_ssn,identifier_phone,slider,data_types_complete,data_dictionary_form_complete,phone,demo_branching_complete +100,test_group1,Rob,rob@noreply.edu,1,,,,,,,,,,,,,,,,,,, +200,test_group1,Brenda,brenda@noreply.edu,2,George,2/25/43,,,,,,,,,,,,,,,,, +300,test_group1,Paul,paul@noreply.edu,2,Ringo,7/7/40,drummer,The Beatles were an English rock band formed in Liverpool in 1960.,1,7,3,100,1,1,1,8675309,123-45-6789,555-555-5555,5,2,0,, \ No newline at end of file diff --git a/Files/import/B.3.16.1300_DataImport_Rows.csv b/Files/import/B.3.16.1300_DataImport_Rows.csv new file mode 100644 index 00000000..0dc293e5 --- /dev/null +++ b/Files/import/B.3.16.1300_DataImport_Rows.csv @@ -0,0 +1,4 @@ +record_id,name,email,text_validation_complete,ptname,bdate,role,notesbox,multiple_dropdown_auto,multiple_dropdown_manual,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,required,identifier_ssn,identifier_phone,slider,data_types_complete,data_dictionary_form_complete,phone,demo_branching_complete +100,Rob,rob@noreply.edu,1,,,,,,,,,,,,,,,,,,, +200,Brenda,brenda@noreply.edu,2,George,02/25/1943,,,,,,,,,,,,,,,,, +300,Paul,paul@noreply.edu,2,Ringo,07/07/1940,drummer,The Beatles were an English rock band formed in Liverpool in 1960.,1,7,3,100,1,1,1,8675309,123-45-6789,555-555-5555,5,2,0,, diff --git a/Files/import/B.3.16.400_DataImport_Rows Bad.csv b/Files/import/B.3.16.400_DataImport_Rows Bad.csv new file mode 100644 index 00000000..78133472 --- /dev/null +++ b/Files/import/B.3.16.400_DataImport_Rows Bad.csv @@ -0,0 +1,4 @@ +record_id,name,email,text_validation_complete,ptname,bdate,role,notesbox,multiple_dropdown_auto,multiple_dropdown_manual,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,required,identifier_ssn,identifier_phone,slider,data_types_complete,data_dictionary_form_complete,phone,demo_branching_complete +100,Rob,rob@noreply.edu,1,,,,,,,,,,,,,,,,,,, +200,Brenda,brenda@noreply.edu,2,George,2/25/43,,,,,,,,,,,,,,,,, +300,Paul,ringo@noreply,2,Ringo,40/7/7,drummer,,1,7,99,100,1,1,1,8675309,123-45-6789,555-555-5555,5,2,0,, \ No newline at end of file diff --git a/Files/import/B.3.16.400_DataImport_Rows Corrected.csv b/Files/import/B.3.16.400_DataImport_Rows Corrected.csv new file mode 100644 index 00000000..be74e39e --- /dev/null +++ b/Files/import/B.3.16.400_DataImport_Rows Corrected.csv @@ -0,0 +1,4 @@ +record_id,name,email,text_validation_complete,ptname,bdate,role,notesbox,multiple_dropdown_auto,multiple_dropdown_manual,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,required,identifier_ssn,identifier_phone,slider,data_types_complete,data_dictionary_form_complete,phone,demo_branching_complete +100,Rob,rob@noreply.edu,1,,,,,,,,,,,,,,,,,,, +200,Brenda,brenda@noreply.edu,2,George,2/25/43,,,,,,,,,,,,,,,,, +300,Paul,ringo@noreply.edu,2,Ringo,7/7/40,drummer,,1,7,2,100,1,1,1,8675309,123-45-6789,555-555-5555,5,2,0,, \ No newline at end of file diff --git a/Files/import/B.3.16.500_DataImport_Rows Bad.csv b/Files/import/B.3.16.500_DataImport_Rows Bad.csv new file mode 100644 index 00000000..80012106 --- /dev/null +++ b/Files/import/B.3.16.500_DataImport_Rows Bad.csv @@ -0,0 +1,4 @@ +record_id,name,email,text_validation_complete,ptname,bdate,role,notesbox,multiple_dropdown_auto,multiple_dropdown_manual,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,required,identifier_ssn,identifier_phone,slider,data_types_complete,data_dictionary_form_complete,phone,demo_branching_complete +100,Rob,rob@noreply.edu,1,,,,,,,,,,,,,,,,,,, +200,Brenda,brenda@noreply.edu,2,George,2/25/43,,,,,,,,,,,,,,,,, +300,Paul,paul@noreply.edu,2,Ringo,7/7/40,drummer,The Beatles were an English rock band formed in Liverpool in 1960.,99,99,99,222,99,1,1,8675309,123-45-6789,555-555-5555,5,2,0,, \ No newline at end of file diff --git a/Files/import/B.3.16.500_DataImport_Rows Corrected.csv b/Files/import/B.3.16.500_DataImport_Rows Corrected.csv new file mode 100644 index 00000000..9b314368 --- /dev/null +++ b/Files/import/B.3.16.500_DataImport_Rows Corrected.csv @@ -0,0 +1,4 @@ +record_id,name,email,text_validation_complete,ptname,bdate,role,notesbox,multiple_dropdown_auto,multiple_dropdown_manual,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,required,identifier_ssn,identifier_phone,slider,data_types_complete,data_dictionary_form_complete,phone,demo_branching_complete +100,Rob,rob@noreply.edu,1,,,,,,,,,,,,,,,,,,, +200,Brenda,brenda@noreply.edu,2,George,2/25/43,,,,,,,,,,,,,,,,, +300,Paul,paul@noreply.edu,2,Ringo,7/7/40,drummer,The Beatles were an English rock band formed in Liverpool in 1960.,3,5,2,101,0,1,1,8675309,123-45-6789,555-555-5555,5,2,0,, \ No newline at end of file diff --git a/Files/import/B.3.16.500_DataImport_Rows.csv b/Files/import/B.3.16.500_DataImport_Rows.csv new file mode 100644 index 00000000..8f005905 --- /dev/null +++ b/Files/import/B.3.16.500_DataImport_Rows.csv @@ -0,0 +1,4 @@ +record_id,name,email,text_validation_complete,ptname,bdate,role,notesbox,multiple_dropdown_auto,multiple_dropdown_manual,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,required,identifier_ssn,identifier_phone,slider,data_types_complete,data_dictionary_form_complete,phone,demo_branching_complete +100,Rob,rob@noreply.edu,1,,,,,,,,,,,,,,,,,,, +200,Brenda,brenda@noreply.edu,2,George,2/25/1943,,,,,,,,,,,,,,,,, +300,Paul,paul@noreply.edu,2,Ringo,7/7/1940,drummer,The Beatles were an English rock band formed in Liverpool in 1960.,1,7,3,100,1,1,1,8675309,123-45-6789,555-555-5555,5,2,0,, diff --git a/Files/import/B.3.16.600_DataImport.csv b/Files/import/B.3.16.600_DataImport.csv new file mode 100644 index 00000000..65aac821 --- /dev/null +++ b/Files/import/B.3.16.600_DataImport.csv @@ -0,0 +1,7 @@ +record_id,redcap_survey_identifier,data_types_timestamp,ptname,textbox,radio,notesbox,identifier,identifier_2,date_ymd,datetime_ymd_hmss,data_types_complete +1,,8/18/23 12:53,My Name,text box1,99,note box1,PHI,PHI2,8/18/23,8/18/23 12:53,2 +2,,8/18/23 12:54,Your Name,text box2,100,note box2,PHI,PHI2,8/18/23,8/18/23 12:53,2 +3,,8/18/23 12:54,That name,text box3,101,note box3,PHI,PHI2,8/18/23,8/18/23 12:54,2 +4,Joe,8/18/23 12:53,My Name,text box1,99,note box1,PHI,PHI2,8/18/23,8/18/23 12:53,2 +5,Jane,8/18/23 12:54,Your Name,text box2,100,note box2,PHI,PHI2,8/18/23,8/18/23 12:53,2 +6,John,8/18/23 12:54,That name,text box3,101,note box3,PHI,PHI2,8/18/23,8/18/23 12:54,2 \ No newline at end of file diff --git a/Files/import/B.3.16.900.100_ImportChangedLocked.csv b/Files/import/B.3.16.900.100_ImportChangedLocked.csv new file mode 100644 index 00000000..14cfc32a --- /dev/null +++ b/Files/import/B.3.16.900.100_ImportChangedLocked.csv @@ -0,0 +1,2 @@ +record_id,redcap_event_name,name,email,text_validation_complete,ptname +1,event_1_arm_1,Name Locked,email@test.edu,, \ No newline at end of file diff --git a/Files/import/B.3.16.900.100_ImportChangedUnlocked.csv b/Files/import/B.3.16.900.100_ImportChangedUnlocked.csv new file mode 100644 index 00000000..18c1c493 --- /dev/null +++ b/Files/import/B.3.16.900.100_ImportChangedUnlocked.csv @@ -0,0 +1,2 @@ +record_id,redcap_event_name,name,email,text_validation_complete,ptname +1,event_1_arm_1,Name,email@test.edu,, \ No newline at end of file diff --git a/Files/import/B3161200100_ACCURATE.csv b/Files/import/B3161200100_ACCURATE.csv new file mode 100644 index 00000000..18eb5999 --- /dev/null +++ b/Files/import/B3161200100_ACCURATE.csv @@ -0,0 +1,6 @@ +record_id,redcap_event_name,redcap_repeat_instrument,redcap_repeat_instance,redcap_data_access_group,redcap_survey_identifier,name,email,text_validation_complete +1,event_1_arm_1,,,,,,,0 +1,event_three_arm_1,,,,,,, +2,event_1_arm_1,,,,,,,2 +3,event_1_arm_1,,,,,,,0 +4,event_1_arm_1,,,,,New Name,,0 diff --git a/Files/import/B316200100_ImportTemplate_ImportRecord.csv b/Files/import/B316200100_ImportTemplate_ImportRecord.csv new file mode 100644 index 00000000..dcf69d6c --- /dev/null +++ b/Files/import/B316200100_ImportTemplate_ImportRecord.csv @@ -0,0 +1,2 @@ +record_id,name,email,text_validation_complete,ptname,bdate,role,notesbox,multiple_dropdown_auto,multiple_dropdown_manual,multiple_radio_auto,radio_button_manual,checkbox___1,checkbox___2,checkbox___3,required,identifier_ssn,identifier_phone,slider,date_time_hh_mm,date_time_hh_mm_ss,data_types_complete,data_dictionary_form_complete,phone,demo_branching_complete +1,Joe,joe@test.edu,,,,,,,,,,,,,,,,,,,,,, diff --git a/Files/import/B316200100_ImportTemplate_ImportRecord_Column.csv b/Files/import/B316200100_ImportTemplate_ImportRecord_Column.csv new file mode 100644 index 00000000..a5897030 --- /dev/null +++ b/Files/import/B316200100_ImportTemplate_ImportRecord_Column.csv @@ -0,0 +1,26 @@ +Variable / Field Name,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record,Record +record_id,1,2,,,,,,,,,,,,,,,,,, +name,Jack,Jill,,,,,,,,,,,,,,,,,, +email,jack@test.edu,jill@test.edu,,,,,,,,,,,,,,,,,, +text_validation_complete,,,,,,,,,,,,,,,,,,,, +ptname,,,,,,,,,,,,,,,,,,,, +bdate,,,,,,,,,,,,,,,,,,,, +role,,,,,,,,,,,,,,,,,,,, +notesbox,,,,,,,,,,,,,,,,,,,, +multiple_dropdown_auto,,,,,,,,,,,,,,,,,,,, +multiple_dropdown_manual,,,,,,,,,,,,,,,,,,,, +multiple_radio_auto,,,,,,,,,,,,,,,,,,,, +radio_button_manual,,,,,,,,,,,,,,,,,,,, +checkbox___1,,,,,,,,,,,,,,,,,,,, +checkbox___2,,,,,,,,,,,,,,,,,,,, +checkbox___3,,,,,,,,,,,,,,,,,,,, +required,,,,,,,,,,,,,,,,,,,, +identifier_ssn,,,,,,,,,,,,,,,,,,,, +identifier_phone,,,,,,,,,,,,,,,,,,,, +slider,,,,,,,,,,,,,,,,,,,, +date_time_hh_mm,,,,,,,,,,,,,,,,,,,, +date_time_hh_mm_ss,,,,,,,,,,,,,,,,,,,, +data_types_complete,,,,,,,,,,,,,,,,,,,, +data_dictionary_form_complete,,,,,,,,,,,,,,,,,,,, +phone,,,,,,,,,,,,,,,,,,,, +demo_branching_complete,,,,,,,,,,,,,,,,,,,, diff --git a/Files/import/B316800100_WOUT_REPEATS.csv b/Files/import/B316800100_WOUT_REPEATS.csv new file mode 100644 index 00000000..420142dd --- /dev/null +++ b/Files/import/B316800100_WOUT_REPEATS.csv @@ -0,0 +1,2 @@ +record_id,redcap_event_name,name,email,text_validation_complete,ptname,consent_complete +4,event_1_arm_1,NewName,,,, diff --git a/Files/import/B316800100_W_REPEATS.csv b/Files/import/B316800100_W_REPEATS.csv new file mode 100644 index 00000000..0dd2a704 --- /dev/null +++ b/Files/import/B316800100_W_REPEATS.csv @@ -0,0 +1,3 @@ +record_id,redcap_event_name,redcap_repeat_instrument,redcap_repeat_instance,redcap_data_access_group,name,email,text_validation_complete +4,event_1_arm_1,text_validation,1,,NewName,, +4,event_1_arm_1,text_validation,2,,OtherNewName,, diff --git a/Files/import/instrument designation.csv b/Files/import/instrument designation.csv new file mode 100644 index 00000000..63ebf6ed --- /dev/null +++ b/Files/import/instrument designation.csv @@ -0,0 +1,14 @@ +arm_num,unique_event_name,form +1,event_1_arm_1,survey +1,event_1_arm_1,consent +1,event_2_arm_1,text_validation +1,event_2_arm_1,data_types +1,event_2_arm_1,consent +1,event_three_arm_1,survey +1,event_three_arm_1,consent +1,event_4_arm_1,text_validation +1,event_4_arm_1,data_types +1,event_4_arm_1,consent +2,event_one_arm_2,data_types +3,event_1_arm_3,consent +4,event_1_arm_4,consent diff --git a/Files/import/testusers_bulk_upload.csv b/Files/import/testusers_bulk_upload.csv new file mode 100644 index 00000000..911f75a2 --- /dev/null +++ b/Files/import/testusers_bulk_upload.csv @@ -0,0 +1,5 @@ +Username, First name, Last name, Email address +Test_Admin,Admin,Test,test_admin@redcap.edu +Test_User2,User2,Test,Test_User2@redcap.edu +Test_User3,User3,Test,Test_User3@redcap.edu +Test_User4,User4,Test,Test_User4@redcap.edu diff --git a/Files/import/user list for project 1.csv b/Files/import/user list for project 1.csv new file mode 100644 index 00000000..47af47d6 --- /dev/null +++ b/Files/import/user list for project 1.csv @@ -0,0 +1,6 @@ +username,expiration,data_access_group,data_access_group_id,design,user_rights,data_access_groups,reports,stats_and_charts,manage_survey_participants,calendar,data_import_tool,data_comparison_tool,logging,file_repository,data_quality_create,data_quality_execute,api_export,api_import,record_create,record_rename,record_delete,lock_records_all_forms,lock_records,lock_records_customization,mycap_participants,random_setup,random_dashboard,random_perform,forms,forms_export +test_admin,,,,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,1,1,1,0,0,1,1,1,1,1,"text_validation:1,data_types:1,survey:3,consent:3","text_validation:1,data_types:1,survey:1,consent:1" +test_user1,,,,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,1,1,1,0,0,1,1,1,1,1,"text_validation:1,data_types:1,survey:3,consent:3","text_validation:1,data_types:1,survey:1,consent:1" +test_user2,,,,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,1,1,1,0,0,1,1,1,1,1,"text_validation:1,data_types:1,survey:3,consent:3","text_validation:3,data_types:3,survey:3,consent:3" +test_user3,,,,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,1,1,1,0,0,1,1,1,1,1,"text_validation:2,data_types:2,survey:2,consent:2","text_validation:2,data_types:2,survey:2,consent:2" +test_user4,,,,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,1,1,1,0,0,1,1,1,1,1,"text_validation:0,data_types:0,survey:0,consent:0","text_validation:0,data_types:0,survey:0,consent:0" From cc81d67be3e215f7ecb80a8112b763a14f88366c Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Wed, 13 Mar 2024 17:00:33 -0400 Subject: [PATCH 95/96] upload file --- Files/import/File_Upload.png | Bin 0 -> 5243 bytes 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 Files/import/File_Upload.png diff --git a/Files/import/File_Upload.png b/Files/import/File_Upload.png new file mode 100644 index 0000000000000000000000000000000000000000..ff2eab5f658b6b257db739c0fd313ae800149cc7 GIT binary patch literal 5243 zcmV->6ol)EP)B300007bV*G`2jd45 z4k{~U!T*l{000SaNLh0L01EH`01EH{Laa2H000ykNkl3&R z?m6eX-+%u9ye_LK3R6c7!R2%Y>cEUTqqT-QqqT-QqqT-QqqT-QqqPRk=?qwg5Racb zaB#GzFE%hJBod+PmaKT-yGw8XPOB==;9UwfGk;gwI;E=3l%pw5-+X zq7VT)>*CR4k3DtnrGxoL8Y7>-c3CSBnHU%p6AAsFE3zUpvI@o%4mK>mq4CD$fu&2X zx%HNY6<>6^a2PPl7)_6i9(nNLZV&6?B{9LLEhPm72XaMG&K>bK z1V8t+w#Yr-p4HUO0!D$w$)m@j>dQMhns3yjKHgC`KnOoJRN{iMksg7;WDY4uu? zEJ;$qO#-|w`}SSeZ~iXV(BO1USOay8f+Ej9zc)vu2A~S0Igv^j{ygmU`#A3MwDFlm zC>1MU-ij~$&fh-~zVQoA*NO#D#3-27^DpeZ)bnQkK^M!;3xuWxJ|*xb(*aW9-D*j#Y@#K_TRSp*f8!xBg=6?%}PJ>1n zCZsTeG>b`flF^~v&%vwgSBP|KDS-Jk)AZ(`sJyz>&t*xyb^l(7T%D>elW>Mnkmd(l z9!i`ZEc-1wof^QOO7dx7rn;Y(lG?cZ`metHqW#rn2@dq@LaTY?&+o28C$yanK0i90 zfOuxQ(HE%t=N>oba+(USZZ?H=__@9{zbGfU|t%u{-0#2Es|K2z8t0Oj7nkCq3b%D-bKlYT)3FduN@JnU&ehlko zA8wImf5=j6S_DN_c(EWq!9^{%^}J$RrCEi28a1R792wx!44ujq|HW%`Cb~>n7t6T| zYH50O?9BFEc2%2Y*u0t+2@qz)g%rATTL~$V4|ohMv>sgG^%mY0pT7J`>fEP*xR9JXFB;p3ga(lQ~e$fUooLdD!MhE|K zht`wesw~iu#~06}Y$zud!|N`IfZD&FBL4;8=0u6ipNgD;qs6B${T@9{sDSY@kj^R)C!q~-E zerbPk%7O%=eTL_#ji>`&ZblS*Zqyj2EH3`v8}=8cEbucLJ$lUGlE{r&)xgq}mc>}# z+fEg#2$&fKFPB=Aiw6~&eh5sbJ~-uc=CZ)dXzH_3!*hI`GbUF9VpOW*&0YNE>rNFa zAD9_Uoc`GG9A`aTL`HQc@mwri4d4_oGb+XnOs-QtQ4T1KDvI8$toWHBVRF*JqG_;u zE})O|ILjzNs@6)#vaEl?#s78Q@Y>C&$K`gM(W>2D$%xU*N8fk0Xw2N)SwoPeDrN_Q zKn=A$PC*PaHyIT@Zp(~{CdL)AG0aJaV;Ibg`WG+K`4*HRRJ#fVBhrH4bzAETlw`Aw z@5JGw&X&$zM%^yZhqDFNV5unu2Un70lP5bK!(e9A(-7AC*2RgYtA;2nxx1nynm>K= zc)znn!_27umIW@>RrT6GyfCj(p=5IgeE|2)E_K518Tl74tn?M3Uh*nn(%mgxLTUyR z?>gC(l3=uAQ(ARsj~&pQ7p+e!0<@iiSPh+k_<(U&C^_I~wBd`hV6PZx&Y@AS^sTJX zDO;oSG(Y`v{PODy8jrUwcCcvpcY5?MS%jVlX@L5mQ7`+IBuVDoH(>GoRPtmh@tagK z!K?f8j0`hx_dfZrySHuIcF#Tc*k3gKD}pDF9y|V>O=Z7o@`tL}5R4G!2g0Q*h0RDa zAxk~U=sU@&t1MPPBof)NV@F3vhn?lZuhGD4&?r;VsF&SyEFU={`(tJYScZp(*R5OE z-rl}v&z|PyW_!v-WYzu~U%I92acVWH`9YOx;=Od@)v1YhCNEWet)`}?-rn9-t5(@i zE+YN9TsVxL2x;UrszWDuI)8O;;PK&)QRoE3VzJe$SA$Y*C>N1Eu){YlFT0HxRgh%K z>*g||P?k>Ma^K|mrPMUWD{kDl5#C9=OS5lRb6gM=iDem$P8XXUiub!bJ`Wd@#Pz3- z;pH+18%UjtqiGs|NRP}mdxHzZjZ4Gx=lOzRug}YJPmg>;h)xY#w{AUg;sm+$=a5D@ zm)qlZd)*#C$8j!Bguo-u*d`^RiSvU%kHjX3W&_$(&?q@li7=`&e@t7Xz%s1P2&JsZ z`GaoNZPDOW_ki=cy_|~$F8u||ffYWJ$)__erbB9ec8{NnXNb=w?(gs4rh-J`#G{vh z#~a|hAPx`wA@tOPYbr?z~dXhQ9$hRSX72Lc{HuJIN~$F1rth?Wlcwxzv7KDCe69)W5A+q**r_LPbA z0uFxf`^|wcJ!5A%NRlM*1vXq^6m_3uMr>+0aLY|HmsNQ*8U+EtJD5junE{!eJ$n{= zUlM+e%9E4V1ZjN!LUu%@ut|mhCL@UmPuYlU#-rhZX_F!ihWZK=` zjXjdVAHAes?ZuuZ7KnVNXdO~Q;)ALs4}EDxb2&Nzt5&Vj;*Fu9p$!{0;LQ>+ioKYa z8BM-*IQ<^MV5@3~qEOTe58hDF?a@r`!oRuSFa_{pK&d@FJ&{NRSFS+)*h`9&Q8|$u z`!W8e9vzY_i$bx74Bn8J%{Dso?_BHuZL^OQXlrW&y{=rj5=+Lw@L~^4aWXpgi zmZ6nAC_?2?Oi#{cuh=N$ue1g3NpGf<>6fJ3G;H2r&}g zBI99{R(s2o+S_T7Z&1S(S17pTslP)>982Iqqt&I?-iku$wh4aD<5o+(6{Xa_WwN`7W{ceT)isTObQ}6rY@QWn2B?fuYj4F8d&?^`<2m5p zE`IV6ELX8->X0QMF-ony%|0Ktusa@{TR}qdZ_C2A8GhzbJ)_jx+iU<@GNhX8@SA_< z+N%9q5@>5{!<%6BjM8gw#o_=|V&t&f%QCF*`pBY3wm6+ZvZ!+Gg<5-?b%?}bhbZd} zvDt8C>EnNk_j2gbB=(lL8jVtHZy8A_m_4LqCy34bzi9J)=KF6=0zI0LoMya*8 z;0{TJ>jS66jI1&W;Yy|PG8CXQ>byp&wYQ8W&^$~_yx+xv$;BA16yd;u11LYg?KTWC zaS^OBO0&H!9RX#oOd$IFGuv>5EBQe0tS8YyVU1CG?X4u1_7DZt&5;*BvKf2xsew*L zE%>^z*Lu#Y8;;Ho%q&!jre_}J8}|CqAG}dDfKGwGI=@#`BzN}dN!iH>&0lYucjq@q zT(q~hx3AB5w{IPQ$#rseC)nH5k3HSw3*>J|(d-WuofgleSeC&!snZZebf#p1m!&2y z`@m6%J{LZ`nb3972VMxRelg4F$fHlq^M|H0)4U{U6W%%2?at0s=klkkH~0d)B*xOo z0Ov)2PMHxDffw@kj!KFdm&>KmsYRb8nomYuyD~gHjFLhm5^<8zOM8DYd7}SvELynN zVYa6&rhf8!JU9I1U8#4Ei5JGe{N~Iuqdl;U0JRXP2!#t*0NOlFMx}Gvvp*r%eD2)2 z6EP7&OC%UGGqCy5iv!=f@6x3)opTm_^NtlyKL#H%gP+9qy#x_X&Vfqssf?K2q&Vos zV~Vqn<`(!|+^I0iw8-bU1aQli-tgQ%6H+J8sjV190SFZPWR$DLH#}po^GEu00Zb>d|B!dTeLVA*O6beWxFa>dL7mkBWgAA)&ifA{#gT}Meh zdS%Cs9S=VEAbL7P7ke9MG(9r<&h6{;lkhKIcCXvD#<%l>qF6bo@u>2T#Q&NUY5QNkOxR=-g`9vSka2 z*_rdD z6-km(e1=n>UJB$TL_Yf{Q`Qx@GILtPFrWIT3q!Aujm-QEE2F?ANa~3vp1_jY%9Sf2 z>>)a;YG8HKMo;^=?puFhhE9Mh9BTN}KZF;f+T_&nlgYOagD1tP9x|i)P}-SUA_YF9 z{tE-FzP~3e>_YbLJE2^dK~oX-QDC#d2KvCriGWm^hV69F0ehOpKYi z7MM7or>(6Gs#3pO9OQUH1$ys6DYOl6NOUO_!GKYn-Bok`Ez;!|w&a8hNPl!%iYLDE zCtqLPaP>xxi^7>y)^k3Wo;F zh{Tdgu(~$Obi;-X;Ac5v8>nNH5TJ5xkSScEv$Jz(XvogZI*Tw@7$quGAQD8mfB$|6 zleTT!WbEaNQgE~e@1JUW# zdWoGbgdXM`qctznImakd>oT2-jMlbHsbiGfl&XBxuuSJDqv$dvH$4*()G=xs5M{b^ z=T3WWKC76!jH37S(kauq%P4~^)2^;A3S~+iqll}fEp0tgn=*B}8?qRP#j!dPf<7Qa z+t>?r8nqdAtTsIs0;4o^IMBtYvrZ$TgF{L8Jzb2V17*9~ z*49?U=V*0xbvfnSDb-u&F>2AmZpzmdgo`<2KA;dgH zA`u7ckS>kV0Cbr;9LYF%Hfr2qx-{yzqo@I7ig<518Ob-N_n{wK4e0A)`N4H%09N=4kDv+On>q(PC@MGsx@E)PW?BXcH_vEM9I0^&MD z#%QUbRe)=QUcL55G8Ac)HZ(UkBZe`I6Ol}vQ9WRpoM7|NDMgG@HCsnRTU#6YGh=Oz zWGG^kPGISIw{uBFolygHbaY^Gp>3O8MiHYFT3trmfqtpV|kf%LErxY>j z_~2+Ipm+0X=I0XvsRH-+6C8wP#B`v4?p}6j;vj4f{re*qd&;Noxe#RJ63T96Wdsj(}3(Ta)>$Gim|o-Mkv0H7y-F1qwC( zm@6`af8k*M2Q#3BQ6PhUMzP#>8sO$AX5tEwj2fB)z%2s9TlB3VXxWWbo3Dkkzo`vR zQvso9GDW-)w4?g-Z-7W}EP&B!Zgd-USce{<5e4T~xgtkk6pp|HhoghtJPE^9+1zHX)~P%{pcPQ3?q0#TQ@9wVeR?3|=l6dHB|3 zI<&N-bu3u00DRgz?zkfq3bm>LlY8jUp=2@%$KhL(=}^=QScitLuCDxEK&v5BozYrD z-7~5+)ETWc)ETWc)ETWc)ETWc)ETWc)ETWc{69S+udlZ-a!CLH002ovPDHLkV1m3m BCQtwX literal 0 HcmV?d00001 From 2a0c9e934687b971aad9dfa887fb0a0cd651d5b5 Mon Sep 17 00:00:00 2001 From: Theresa <41602553+4bbakers@users.noreply.github.com> Date: Thu, 4 Apr 2024 12:40:24 -0400 Subject: [PATCH 96/96] Add files via upload --- Files/import/B.6.7.1500_Upload File.png | Bin 0 -> 24554 bytes 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 Files/import/B.6.7.1500_Upload File.png diff --git a/Files/import/B.6.7.1500_Upload File.png b/Files/import/B.6.7.1500_Upload File.png new file mode 100644 index 0000000000000000000000000000000000000000..4be05db0566c6725a1b6c435f867bafe8c0d8291 GIT binary patch literal 24554 zcmeFYg;QKl&^Eg0;;z971ecKDiw6nrZXrO>K=43thY+0L?(XjH?y`7rcmEE*?|pCG zs{1cos;J%CI@2@VJ=4?uJbi){_H%u)7O6((c+KsAdo@u=T9Q4E{jJis1Br8DRlS8 z>IWt|)kqb8A@SmIov3VKtxbsEY zgbz{nUpkFXBqrDVKs&w4K_kZBz*-T;qOuXjo=7Pu8dmlTOZ(cMSMP-wlLw4Nfpr3Z8H%5-U)2MFycn@C|NBA-KKt(zWcUC7 z@M?(vuRZ7(-4K2q%)iZ&^r$@9>Y&3#MZF_@Iju_bSS4(fe%Y9u_!?S9%72i9_IYYG z<8ohtlVr@`qSQGcYu@=);#wuU8n;QAFQ&lVc9{|v`(xS5?J4v!=_2^f-+w1nVU%r{ zBDZa4?`narclejxJEquo3A>A&j-Hp`b*Zgo%#Uilqr5v&Li)I#8b|zW5l=@jfYkOP zEX;Z$i^qs(@xne0bq$SF{bE~lh9Ya^y^rGlo$i_q-$!@}TOO=+1Z|;#LJr5<6cH`7 zuj^@-!NOdwbGV!r@_bAjOiZ+;A=T3k4tT2;DP>Kgjg67VL45D_#l)O8*5OC+o&#Tk z^xlo}4DZ47N^Q8_si&^}aoo)il<`&68cY!QI9-a}{&Zl$S78)#mb5#tuxK{3d~V)_ zhJ_qBr>d?YnU#k#BopixdJrL<6ID?Cd}Yg1eeDzG>2R>KI^kM#cm)3{N?Ht3&c-XG z5V^MXHe8uTlkc9fMOh6yOsz~yikan|`rxx`u_?=wK-(|ABPeTs_J?5A$8XM}$SfwwDEZSA&{x?W03inTSg zF77v)j|f0mtQ7Zgro@|r<%TumsgyYgwaf<5>!bYy;RK}t{r!h*eLL*>oXL)Ws9nOv9iRi zETkAMMOV=$Pc|#xZT^cDr!?KZRq@D(RNvtcEtrZjBSY@C#dj#g&DT_UZtU@&J`)QO zQN_q1ojhJB=(_IA={{2br+|{u0#ka#*RBWs`l>nycBGU&q|5s~e`7wAW8V>N+2U@C zS!Ge%=K=f$C*NPBL7%8&*KMiI*>@OP&L>Zw6?yFTJWqby9K6c%+DX4MoB>YPn8#jG zVz4y2(u#n(%E7&A_RqV+^~bEq8171Rq?!apng^64%Pv2x!CES-=X(vVXA{(LHiTCZ z`ra;BuI6Lm`nT$73C_wZPtA*bbkTSTN;+C<*ngOdna^%*wJ$z(){EiM`VBp_J=9|A zjh+;}deLhGmJBoM;v&$=qeC`JBxr0)w5Qm>9-|E_NratFT3Qoe93(4f$`@)i9CqV;?_eCniv|-=)1$HupnvHH@U{*g{aWZ5h)8t(3 ze^!*bqPLY`V+3X?ZNjaM5RUgC0Rt$5VDT`EO?}O>GfOLHKi{N=Pzxo+$mV5Y|0w}y zEK|a7z9c^8QLwf?qRi#I9!D<=9~@u+oZa`4#W}*A6z1x8xP_yLzWaw`T*>mq#YKhd zjV77co2(MS{!?vBVTiAR#LE!*6T}7ZIWUvv$l_gh=0!nB;fIWxgqgM@E!kpKLSm}5 zI3VT~uz$~TxyuM#y`3p*U?l^Ff?_saTx>TYm7+1lM~e!B)cv}ExOM1g5G(sF6PrXY znwkFWuI<6|II`t+hk%4h)B1edxt@uRRQ6&D zi~g!TsAK)Y<@E4xTb!<@lnO0>Gv7!)@pnfiJJh80m>cDBuh(ZlRGxjWF4c26MunU!<6(7=i=jp0%W-0`~308eucjg;OQ;Ck{pp zrHM8#nOJZB+mh{NXOz4`FH3Bmu}{f@7Xm}_EZQns4N=ksz{3i|j3r!@c)XmY>f6@MBazbNatOi&_@rd8x^=esBaf*R{Ov`a^T=en-p?{^qXQpcd zmDLxzg{A+-)n9ypX!5yQoj1MMtaBH0MWWBD%`nr%8JD>!<>3xBr-c&?0`onTWj(wQ zl4qg;gVx*xe}iAoHZlv#5H5;wlxEk*n!p$F|Izf%FMP~HPO@orb(VKCN9r+uW%C$AG0B`{_C(&Woje5} zj{K(>=^Z2ayd|HeidIc|=5e}lM<;FC_^-za16J~%TGxE9=^=>iIT(x@m{vF8fEA`% zoIMOt&_WI!h+Q0HgvtcRKudCgM};swk9ETel%L!Ruir9{$J zQ(E}XLHX)VmQy)FmPYrQ%4Rg?;a0-~!tD0pbxsgrYcMzquyP@F;q$NDH$x1^Q%P}Q z6lGzMcmMl@M-X`6?k@UmoDOFFs_%~PxvUz(s!N3Y-#zP^+x;JxY_E!*(h7C^Cip5W z-j;C2&XA{!Rf~EX`aX-l&e6IR=u&>VjQZa+jZxBr`p#vdFaKQ(2Ipe0J|r13(D5cY ztyL;4DA<~BqyK8eNcaDeo0HX7{0w-@?tKHbThEcls&OU<&i2jSJ33eQr&aR5|C7L& zJO_cxw4Y*uOv9+N=!`N!UQL3L$K54&xqhp8b2iZTzv!_6p}-`-5Mpz~|3!<-L4pY- za$|h|;jNqdtLfV1Qp3T)cL+soIAN+ZlMD+?$5J6n(WxqX)py)&&o*sw|1;O?b6l$G zijdRmWO1ef_`Hb$(_Y%0mg_RGvCV%uhph_MrigX*pgpF{tW>r#M1n5wL)@f@*+1^h z%DVq@n|g+zGcSWN(l0z=^72}T_JB3dRH9WXxe;HjR{t*OOxQmUgMY`hf54byFJ^lT z^4uo*ztZK_HoR@f;|^W>KYwFJlOA>3T#No+xxh%ugtO~vaWsF@dsbEtLq-!ia#GLB zzyHqzwrAS8a0lpm7uX~eje(3SxI{; zI0RB)O7P6H7LK8itb#(*?fR6~;f~Rsk2sRR0tq4rGJtuO?zGvvFdm=aJgcf+n*GSm zn(+DC1}lH-Wiw4vx@F^iGBV0)*qg)T2otC1r8Ly9_XTI-@!lJ#*2Hda3DgR@>~6rRiAIR z??TAO=G#kO_Qr$;x~>c*)_#8a)dWAaf0|apE)jpWVNAb&m%rYR=ZNHlK$1QE$@Cn| zI88GAVL+FikkSJmAalJe7+o4^t}1PGdS7AGBv_It#iOgyVhZGeVXJa9xEO(?c$p!~ zBcWwgp(C@*3roGjeBiq4J-%+ZFNsM>TB?RK{P2h{0hRPP^-CsF2o5|A^KTGAt-y+3 z6ZHxboA(!^nj_k7vF0W%B~B|Op{Q{lw9%tHKL^wa5ZsMPWfkIkL zFc=)}ajOuGx^0uWR6keBbFpgXNNLBoXB0?%-aXklztMT}m(V~LQd3^3ypeL|l8htz z?OPsS7;?UQBf^<5r$ggJg9IOh2#|8wMpo;!2HV>cjHJQnW|tTrS_YFJIz+UgiExYrFPG4uNk==KX1RR?T!E zOO=t8`2o@zDBUAe?aL(fXu;0$4U*6KgN9c$Rvl|vhS**%1@1bcj8v15nk1= zdxIkVbp$ED421N7hezs1X<3=Vb%+!@Cufc0f%>3SJ}w+6=3lf+`SFI=9|21IM(pGm zbew;P)KxzaxLY27&BfHKri)zRH=4es0tJawG#3>yDYiW1yX+kwL#xfFc6aj+9brJH zptNo{96iEuM8D|;UP^0L5>gq~o7U$+^r^O|;|X&Qfgst$`1tg}!Q0#VzOTa}7lnIPyqrceM ze>GP)sA`F@y#;kRoj{LoB(9ha0aQ2MFd6LHvnQ@YJTK@So z&iB?_*%WEj)mHwKk@S24)*RiEn=30T3mnJ`{g5;Z(N@18dZH9(z`uf0CJtMQ(;ZU4 z%}Ixa31N#K@SECeEZo1afQG<3s&Qs0ewXdM9NfsFGl*?TBtXN&yhwGyK5G{Tj#;G! zjBfklF(d`cY@1=r&=t7w1AXu@FYUctRX-{NwHAJnR?`zmbL_1=C_*>h9d13v}cC#4;Vbt;ArW3Y!i _TjM*1#od#!BYOHb;<^s0ZY(${c6r^%F_%aU%2j`Fy*FpeV z^Tb1YraHJi+e~~(99*okS+%ZPk#LMZK0bDVu)4Wh1I15&s9%@bL|vU@`jpRf zlLMU^>QMt9cjA>)w1_eMix?S;sAG^B>4}J1n5rtRBGCJP+3^yTd=c`z>5jbHrY*G` z8ra?49UoV;v@ANrhe0BcMsk2E@!Uw)y>CSPS`Gt3D))SO{`2S0FZTKJFI}{Mb)(W& z9@aX1#~>GI2M_EK;yF{LdQHY zJ<77GD%>-WaC2}lavYX%nbgmtqa$Bm-^w{y(BsLhj!nzManr)sUjq-`nFpb>V1?b) z>%*!skB6nzTq~?WXtT>{2Ut=|7Nq6`ULo*M(&+*LG`+)5?BAr;Yu!?sjKT7bfgeVE323ml=hz8UHWZ% zXf!;})`S&Scpu3qQi5Cg+U+e*(rBm&7h#}*8#O$v)ZZ~g5-zLVlM`+<#9_d6qBiwM zwM(Tf*NfjOYps|5HTbPXyRduSB3z5nkd_wdZyMox8 z+$rIe^fzoD+ut0+LH=;^m_<_8*6=m^(#`bSw*_X}JBnQnF(Cz6+5YED-mI)FhckQk znC#^SEu)HfpQwViyn?xyLZKTB!6t7ZZdO8?>cDJ@<0{ zDnrs8CT3?PY$BelhtFTj5;max=CzSaImBOQiIy!U!jK#_Hb77NIV-XqP-ip$id4+%!8jp8QWUywIg{M|9n-$!NaBjwG)!SK_+{Yw79 zsf^pfw5Twy_iCQq1b}=uAH`Hxz8NGO|Es;B=r- zgIrZ$w~#{XCT?ej%fJ(84kUz0(jqCxPIny1)bvBh0g{A^#2{(IsrZ1(uaPppx#_zb zskU)NA>?h_aXP!Qk5^@$?x$-aWgjVTw<^rmcRYdGq+TW`swdzrTV8bRx>W0);n6=K z!5sy?145A+;t((%j?>X1erQj(=a0gaHEi=W8`ZF^L0W%XzG*r-IyX1B*f$p|Q&U+| zaIhr-7BDp>CDv9}ztxLdTJ%z^6oY0%xZdzLnyIPrH-c1aJzqR#9SnJd7{rfdy@73M zJzxF`;l(hW+hn=4dl-K1!hOWTloz-zx*USKv6s{C$-aw}dh@LDE=Eh1ZWa&Hxc>N3 z*>#1Vj*4bt&L0Vuxq{8jqe3NEMJN~KDPgkZvw=CIW9Qg-*jYRoP$6~$rTmv z6~J&H_LGEfsmKX#JfG?L71vP>Zbj*r7SkIBw}djv)kI97f53U<4>JX6Zl*-_0(%aN z!zvi@7fs(wc_h2Bj;^nrB9TQRbpq7SlE$%o0z_eF!V8QTE9P!5FRP35vctl|Whh9< zLVH}@+%QRb)-p;zf!b$)6H%M;n>QQ-^CLY->I;ZQdK&Q+|{ixx?D9jHTka$b#IA#Q&-@IZtNc% zfDsXmR}wS%8gCKd8NY4SQXDVVgqA+-%E4m^A9jCxi**TofZkLR`z`p1r`=EIy`!T; zuM&C2ZB~wQ;UrJjnb5T>I87t@USGPOLef)~UET=09}4>E<936Ov+Tt#C+DTlc9;#+A2#XJhV za1Kn`vUC=2WBoDtcuwroA}gct5_?DwcCBGqmF+!TWsGV48X6ihGN`_UM$e}OO4q`H zG4ikD5kOeMVN}V9iHri-E>HJYn2=Lp`iI}fUHoqzZcZ>$659H4A;g&DC1$iKg@3kE zUC6YWOuvqK#?}|^hU@&+Sj2+sr^u2qp@skAJoRcIfvLKRiXXpzEmQO%gXXUb6x>6e zPLFInn=bj;8n$rMxh7W=ncws9^rx1@y?ne9H!1Tn@!nOB8Hm|cua3~wCv-ocGOGko z!fM6q-`9*n>0As}hh;i10A<{CdqRcGnelUS0^ zsvZ5JWmK05;oI0NzTREV0_pdW`|tzhpk0Oo@|K=Guvwxxbg(PEm2*+b`SQaG+lcRE z;&VGfECLoA9?M_Cj1hl&CY=1rkG7 zgC!#7eguPM7;=u-3}c$YToIv#8O(^~_xZ)8CjPlq=a!;Zs$42^K-y;W2bb@k7Gi%N zd&33Nf%&y4Gr?CS?;}*GOkN5!MLhO3djn!c2#i(3eg63DY^}{|D=wY5fjYF0n|HZ6VN0*G zzB{qy8Fov;!c5UEG&eI_(_V1Au~mlAn_z1?RC-mrSf8vQXzPXGr;az60AJH^bFuKW1JmPluI<^8p8qel z+WnCHpeXW}zCUElB(EvLUS1mO#9=z+Shw$GXThGr%I-t1uQ7F`?3-{tDgQ})1hIhw z!RGDGmDQM*R$ehNu{m9P^f_@#a(I*zvhErSrckdK{rsF9|0z5PRg;Bk^XPK6PDNT@ z3z?2RK5B$*7!e-I`u-1RYcu?<$1m6edzXWD6G~wFft>jSC2(YoCG;X% z0DotCK!2N*(S5giy%EXzz#eu(#NPfx>WCG|3E3zA8lO44!2IKx>1mqELCy~!x;8nO zd3M;pe*GGs7X-c*)|xfw=ldIf{RL zQ)>9~YtHjwlGk&Q+0A{Gnv%R;Cru2ZNV?%I0K0gGa%Se25ivDBPFa6oZ)3yu&g`Ga zuQcwx{H?rSOgS!*QAKLK<_3z0=@IRGZ(@bFiC9*2HqlXjt~G#R5=!#BgSL#{#bTJ8 zFRWR6{;W}60GOwV#YJh2PhUbeCmN(4{ltsE1@+S+N`lgyg!uRxf%26v6ZUpRt?L@0 z2hQ1M22g4HtdAnkWgH4EJ^54rr7NJQw9&%Q(9q6qvT1>GD>xz4hh0aBKISt`RL`>w zRZY~1y6RKl8G79^rJHpPe2i~v^Bn40BT(f*<$nHzEcVUA`*e02z3-4gi)pV-KZdrr z(W45?W`Cvfw%9+Gua%(k7KlCX4#vF;OjpuAH4>s0E36}jU#Bw5n86+xz^THYk+kf} z&@~8k_Soif3?SXA=$kqf`)j*kfZa|)FNJC;9G{eAf3uvoAG3D6SN#c7j(?L^q}5km z^4#RFUchNVP)CPIVbg`#scxHx`vr0903ub-rid^Qp#M^#DBA6~7y{Nxn-C5J&eE#hZQnRJ%ZiFnwN%M)adA}( z+Wm7sivOo=6Yz*EV}ksQ1ml9xT%D)s5m<=Q%_MY#3=@F+ zenexoM+F2R^8M&$9*UJYoSvTU?)Hnv$1q94@MB>rAMeuX@>H<6`AFk8srnlXv!@Kce&Gl%qT z=I0}Oh5SWCFhmnoM8Oe79_;a518#Ld*tA1=jQp&|Y-QSx^1u>ZT5L;h&bWBW&4=F* zS1QRuC3WF|N*5;bphGRcT)6k+uIZ9}K5xv7#Zc%R!UzlHoS|KPW(CE;pusGGdA2pwRsqsF2ry|2l2Rc@oZ+Z-!4r8s$bLvHlK7mQ}U}@wFrsw7YeHA%heY?

gE90!r;ltGegpu@*OJ5hHVBs%+$7Ro1Jgapqb(l zq(IJ>n%qKHx%|b`I(6lNLKOd2ar1x$O5DNb1YLa{rJuPnk>CJQzsi*mmvBBaOUtfg zaTuC&{mQn9nbN#G$#x%7iSJ+Bnsagx#6yTiPdYzxaZSR=e)f8HYT=Nhm`~;8=U@8U z^I)eQWQ1%~=wp_5$}AaWE|R;L%mk3<-6}$S_fIz^nbiv;F1cZ~jjR*daj>+T*6O zQT5BPwz8tq9LDFp?m;_?tIuC#fGrY1IaZ~0;2LrMeR5duEvs-=C(J7LtDT$s3Mg?mvtc;%#l0||1J+-v= zr|b3;3r|ykbhsw-yY%xTcJiQwH`NS&Bmdz4S+>98`m-g~mb*4ubNr0B0RaK@bV26U z7w!;xQi4to`s+~u@aKBx_v}=`ooHQ+fhRpti>pjSPTI0*DU&BZlI#&pEwX-~T4Y+r z>~B}5VhE6=dSqd#_QyZ>RPruPije~6)Mh3r77TiXIfiU8rfhk1DFiH27)Txu&a(W= z^0{mn^tQ9nr8eT$Srf&S^I!LR?91OALo|mp#2}lH0A1>+WoAE8GL}LGXvs_uk#4fPo!XdKn4cKqi11|*{LOmuUHO1)+)V^S@~h6Yip~wH%#PLQ6g<>)AuN!!@*2_`uz7T-qBULl_F4n?b6J) zIgd-ROSXQ_h$i%?8p-)PMa}NT_K-y@ z5MDDVV=;}wCl@(9tu0pP$)hrZY>bR*qv5F!xu`b0r4m;PT^Q*<)hJ6NHGdPl+F*XL zD(5*s>~+&pwVn8ro=oYn=0eXOimfI(Eu`KMMT)6^Ted={pxtDkUv>6)rIC8Y4vNE_ zM9r(DT3DY_iUdT}~$`xb5Mw6%0n9LYX%;zG3G@kYzMUOEG5+sa{ zm6o!;AIh8_t((b2JtJB;NB zMOXi~(i1eOiD`{HxwOR8Dk-=`Sgl*=9YjnJC5eiDOX|w8*%2%$VL(Cxv|Ak15ev~X zSAMr%>3e~DLQXMP&?NO_yxX_99v=%G{K_{yZDEj^El3nGRS^5>T??zW+K+2hB>?-a z`_sbnxG%$Mqotw5Ah8o%{*27;e0=E;ZK*#$NUD40vK(uXd=UPSv9f+05Xq)^O6m zrwj}8SFnJx@U`~5r1&R$`>G9JC-`W6D`mlqdpaJLf3Mf;g3FI{rhqG}K z95_-k(+)B@dpvG{`}kOp>uPwJ#FT)BmVEp(4?8<02a#Xp6b1$W_Oba2^RZnIs>PM# zhKQzwJ%n~9p1{o*!;c0hoDYeq^7!U|%#wzsg?}H5J4hws(OOgeN=|+*YO6fXbXI|s z*YU{BW%X3#$v-`63}}RFsD0vW`AwisprKqK#Ul$tS;=Q$A=he66+2K&Q}CRoJ%YIB zK!eBnD{jHa)$w{}&^DV(Tg!^mgYRasrO)6!FeA5`Rf|^6!z6kx?OdSOo6En4W)lIMG-DegVhtA2~b=XUWv~eTCNGp^_=o zR4*L*%>6=m;2J}gbL#Ny89MSKM!Lj_N;(^-N3fPl`6Iq;88h^zx8mih*V3d3Czw06 z=N(Dhd|M7cd1(qrZ1@d=6s3j-@;k#6Kqty9hNv<~K(XZED(X*rp5|saN#Xf4binEn z-jtSb;)=&Nm0iyBJiU;G#{pd3DcVn==q&jtI`c;1tj%Xt3%Iy>(5?4h8B)l}$jB-* zf9u`N>p>^O>5S*IKdNYjd`!K*xp8aEVsw#VAG)U$gMf-6){z{fp5Sk({E#cc~Md#{O4Yp1JjI z@_e!?^rB4%($fUSCMyGoC;(O{4k?ooUuEQif&?^UXmgfmPcZ26nHfdr+kM-w$q|?Q z1WLwm@t8j>@W5-ohlT^RFP8OFEQQXtx!?KTGzvo79h=?g<66suJwq~>oQ{`y1qE5R6Uk0@C}H!(WM9I1dnEvR zpxLi<54N}2^2sz8$pP8L=bG@q1q{( z$tH}~E77A*>WF0vxV4$&7myWnZ%H^xeHZB0aXxcjJ8+K!jhg{PNpw2;i(tO-&II z5q;EI;M`7SEu9OR1$v4}zJC_ha-jdd(ulv1PISe#+Pp(94go1Bm&15xJ_7Y&!LV9M z4~Sc3MCB*X8~PsoJKtz*)%Ih3WDlo^I%$ooO@QTKn){Olb7&XfvIY+MNU4bLtt{f{ z`7%8GyOQimwKV}{jSrwj9M)jQGAv7v2wGwbE$vKB)v`MVntKI9O% z6O6494)1)VISE1V#OLf@hw^8-BU06n8LD@lp^#tK^(l-3CV8zzW8tGm>OhlloW1iZYm7C+?pWH1}l;=`Am7fRMdYBKlQ>>ygBz9pw0nS^tv zC%?S9`oVH*=B`PjSha~&FC#6deQb~T1hnS+{4R8e0n-y9k!vd^*5zsd5Rq-ZUFQig zf*pk&E%}D`B(s`{3pb@AafXxvBb|>^06%thVl`WE!=?!v`FM?Pfi%f&m-mO=HI1qa z(2vCE+}w8_z_R`Ed&zH6=CF|*z61RXF8zmx#qs-*gEM3lG1`i6V)tK}(7UX~FFd4B z0B})Iz|eso7VW@cWz+QRCs24$CO5xVIh`FYpE(gEP6xmduMTOHx zhEOcbM?`d_L7$Xmd_?@F543Gih{A~?!%n{R_Xj!GVcrJE)7UhXZkAYpk-Eq;x|Ct~ zFcR?cNtP%<0q-8LP6Fux@@VKet*ud3djI6H$C~v*IaGjzGSJesfLmPLtR626yk^tJu#}?eD zlM>qOe;^kq97_`fmM40nz zHoVh*SPQ3HB=5Yz!b|H%XlLnkB`6R&rHo-IW-klp z1oj9(g!eK$mxf@)v9c%m;N2OHPfcxRm66xxp*PM+hU*m ztN$;?M)HSf0+@+W8~_mPpW^yCvSvmxD%!`%0A;ddlcR%!>UD^wu-Y{gs?R41PZ~kw z0!jr=zbDYnpxdP6C4yXrQ9%Zj>(kdJR7kc!T@8cOM;az;nR;nNjBr< zFGsqk&W-lvDfHdDchhOIompmG%EKxz#NU7lZf7*b?dCWKl^}(g_K$#v-URzajWa^w zS0W%h=r-HhS-%2d7t(OBUg5#XjO};ra1vY5xZ_^!a3n#+c7d4yUIm3h0gkHhaw=zV zIOCwf#f#tJcO7C&KH3>2JrG_lFE0(ZD0uvmn&gA5_{^-V9E#$^(s0B3dWyNMsi!lS zbF8@1#bP+|j5!hjQpCZ@>HcAstu2=X6Mv|A?7IUitmlUNH>Ib~@=6~RNl(bOf+Zgp z-<`udIFsg;KZ(|8qA5B>S}af!gw|A7U*6m($jeVQCRovXO+p-2wo;5AQ`kANFiFp5 zpX{LMNPuHQR!y08rs-X}p)k zr6slF)w1)(pD7!hST-UM+ismR%I=rRpoVqWnOmfgbnVD~?J^yEg6-huo>0k}dU02- zbk*^tr6e1ATW;g?A~RQ3au*X60+^!xlk0Ej-M)tFD_#J*xSx>;-%bI@7gwJ)`*G|+ z>5m?Xi6#Q)V_%JKGNRJ0+%Y_iHnYah&(Awkt7e9;1kXqKUc_ygb3vVN>g=dQqDDbMmA6G*>s_x7eGGO_@$=Orm zYclSN@fO%AJ&R~30Fx#??u2=Ldd$1uVER-!Z*L*a8acHAk4bekUIoRcxh2O!@YQQ_ zQrZqLWftV|{|Qe54ZBX=of>nS1=_mG+nEZq#oF;CEc9L9zqM<>OaGoBQezR>LYbf0 zTVNs8Bw_qQy=dn1HP%LvOixoJ5fjlt4tqhj{pxr9$Etwrpl@j!l6^q%a*IuI%Znn7O&q zhjRwP>pZdD((6`%C|1G1v{L}-0RXzNxMb)Kp`WQt*VWZ!#aC{%d&9y08w=|(dfoA- z0WgRmik`jLFiI3>pyBgNM}KEHAf-*V_!=|Q_5x#wqle1R#|Icu8m+XYDxbB#MsYIB z2xY`Q4#|w*yOmY;AU*lF+!&z2r6=#l4jCpua+-LGPheplUbs3&1G3iE(v=ZH@-}sa zU7nJ0d~2g(JT72eV}oAwRZlu7;iKU%R}B~1`|8ZaG0K1Z9YjY`omz7@Mm!Y+m<3zT zj~}b6t8Mk*OPdUlPn2o}^PLpABF=djp>kj}cg{2CJwz}Vj$eHc2g+>*&}cIvYP*Wv zC%puDHgxI7rRTiVhLxYX;gATRPo6QZ(uwi2aQLOxiofS>FlNTGjeP+?$4a;`#tj7s zjPZXOn4$g+e7@*07B}kM0KA%5(&S)5h^2>x*$zwLppI=@CZB?hWCXOqFQ>(ck64ED zp21X=lSxx3z|78> zh#Cj!cb(rOcjXim44f8BMCfa>Rai)b%^fWA6~E@5i^x_Lq8O;7bi--V8rDVt>_o$g z8~n0ChvO)+__5SLPb%`v!~|8vgjeKD34K{>tG??|b6y^J1gV*UBY`2F8vtaud zGC~0}BEq@-q9zyq;}tD;+@tU6jw+36NBcVyyGgChdZ`xJ@e4&&ix|0`q=Gc#=QwwJoe)Z=CUuL{JJ`^b78sS8X zpuG|mV`cXZ5>^5_&;rh$_t69klQPf(4)z|We{h3{2t8!lS!{v)lj?^oR7@EJAlg^X z?J@&5?Y^p!Ss8b*67 z%A=F1PR9RcAZOK1+!-37j z$od(VV7in^u;*~x%*^P^FS>3)2PWNDcfp59*t}ls{aG0Cwh~Uqm-KwZ!0rc1M^zQV z)rxRNutVX6zO;@`(wcUV*AqTz@`eZxDZ!&SseJwS_>|^Qi$;e;`lKa<8>Vugi`d_< zM2q_G&^hR<`Q|u^PRmLA30kaO1yjI5kCCylUmrGg>*@5@3*!3cquuVjp|CZr)UOru z)6+4P{uz{&No>v1!r$<<1k}3G;H#%gkCH7?a3Ljib#qr_G`Tl~cw({QGkh+)6K@Jv z`I%x^8VlMNnw-m;a!B3X`Q+{&9`?F`7(n_RsonA1a#6Q3yo|KeB$ADv5I=Ks zut(n6p;{&(L0HzAp(n#WQVuqtanPdV`0(&>Zx6d1&+$8U$Y0M&jxx0p5EP12|Fafi0T9AqFiat7(>GAePlw7NRx7>mb?*AOS3s`G^|KXqkk$fRbDq-uh1#7(oOyBnTG^d2VI)VdCMRl?cP z(Z5pf&U}o^WY3v33E!8i31uuQb5J27&C!-%;jX&~KrIH`=K3uJ`jMJRs1Et1J+BMX zPUl6;px6qLNj2B9^75`mq&}60)=n@>$plm`#)*h?l|g+dOiQk7ym()mb!Zwf!o{lw zR=N2Z1nkND<92$$XfU_JKxKe$1hwF%pB^8#U2BJ-fp@dA;f4WvOk`zsfoNDw>D)A3 z1@4;2k&9$76A=MQP$&zIUZ4x8w_Em}pPQS`6wy5g(Z-wHDMAW3bryoF?Kq7QDx&Gh zZ{5V3`<(E#G@Zv+nw)JGs|#9M+|A7TuUTlgh=oc%kTK%%0tK0bq~wqX!dR?$ea}A> z#?O9a&{VGqFxTC)U$$Ms)tjv_RyaIym(__#4j3P{9~SE8%d`twMioQ|aI3lq3%U}j zu1N7#BMMduf)XUj7D|u**d~dFQB0Ef%~H%INu2b*omW97R#j8++)zF(d^U$@5S$$h z3HOK#OWck-hDBu`)+qiygv#mD8qP_Py0s%UvCyp{V;Z$eVc9Nf5s^}ZW-4@(qjVX7 zyfuEbA3|5vi=4Fh2V95{_vE8HL`@DBYU{wc91t-}$;uQvwk71uu*b%uJc zLQmaQ!Z8gg&LlMM&(40dIWn@z2m1kTyDU{6!`$81%dG{>7DL^U(k_&x)a*61&?xE>4Iwc5ouHw8sh^1 z*X&tJ$fJRnN>pn-_tZ)51{)~0j1UA>smDaDU73sxCE(5NM%5s2OrihEY5D=5w&P6T z&(-G4hK2;jK?iLF>%U60zj3e=u|s}r4~oVzj;)~HSdLM@zhQd%i?w@jYY5Bj0qBAx zwL>kT*|Y?}nt7z*qv9c5U!_;@!~1TIS7dZJ`{e{;LV@7kvLusAq45WW>s!oWnNe6m zE}Sm2^r?!dFc&@QS^FR19yp-Tk^)eVaO;B}5>XJBB0JDWoEP2Ct@4+zL*lKXGR{SW zWSMP|UgDpM6n^KyXD$NxywDV#%fJvJ9N0>4;vldhB0d&yF?15_Jix^06IQ1(>QBti z_xr#EESM{@#BsfXV30ZD09?YQ7y!=uq)(Qdj@vEEiZb2OR*67!$o6ZrZ>;dsz)MtAD|=YGoQgoXYpy-*qi{Bir&$< zW#?~TF~6ivjYfJ|j(g!23-L~7Y{X8_csT?FSUfVUU_qEytXV3l)ab_<@qxg?Ko6Cn zq~5@bEJ0^qKmqyW5(Pja}GKNIbFkhMQ zpVg}m_xBPK64RJVuYvQMFGS53JqYXse~K;d^P#TEoW|?NsE+MtRw{x}pl9g>=oDn_ zN{|iM|Ki}3&wfxbr<5Q8hR)9usge0iZ3eAIigEU|xZM;s(2gh=`iJ_f>C}B!Ygi(8 zqu*+82OVc?`n!N~#|vofT77_*V+bFz!0e-EU0D%5v<-?tkB^KDs^0g4N={zh&m@7P z{y?7!#m%3H*LQLXF{&fYEsIvgdSg$9PP!K8Z4r{Nhtv4!Ll3{O*hwF`hA;swl@-M;RlWj62YIE^j&3OQ4tGg(*I98-xb#6 z)~y>wMJb{vpddtaiAX3eX(}ZMx=;{l(n~<3DZTfAE{K2>1>&Ojt^`5}2qDr$kWhut zLo-0=B%y>P?2q+7`(p3&ocnWea+hz;XMP#8WQ_5S_npc&Gamfz$^%ktmx(%^Z*MM6 z$^!w!wT*VemPM^~9zFP7@rR=gmc{tj7C#dk4e7 zmoA+PS?}j}>*Ha%`;NCQ!666d-}>`8I5krOel;&q;H6wdnE*yI3;sUZZV z98B_8Q8MdZ-)&WvtWU7C0SJ}AnBj<%mBwTa7r8}cdcW>!5Y6_5A@CRk`tjh%a-hSN z_9LMwC_vi=tjWf8WDF>LcQ2sVIFWPfr~&kUy;P-1vsr9g+?PTc(dF;4Sx8Y zlwjE(((%X@Ze#^c!mfKDC)^ud`?6FbQH&+l0hC^q;AuWN+j0=Lh4CL{(bi<*1w_>8 zDTkdKp&Mk~u#fXQ$759~%ev5=C7@F8q4G`6<%+vcxGM`_0weHB?)LL}v+kr$)HU}=kep(BQ z-zeJ5sX%Yt;n!fD&_p^ej$(P}>Ac7J%+Q3#d^c}qrCpguC7g&P6~`}ZT(Q>zNi{}73mJOen0{2}& z>;}9Zu&K~VL+|hADB*<8eJMBlk+8U2Edd@9bxWL%^w2;FlDc{c>5K{ilii~+bJ06Xn3>^+u1EOQ4YSPv{PvuZf3Wch%i(xy zU_R2fl#o!Cm$r3XadLbc1)Wv&(Hgt{H-|^}si?!+s{I(wG$`70g)g#Yd2=R|GNftB z{)bSsI=?*z3K|U$$Vv1Tl>UXQ{~#@b2bad;w7okDe}3Ng%oulThcXUx?Ndv+zah>Pky zOJs7ZSzQVSF>GEKx{o$dP&EH3p0EY$a; z4^c%V0q%F;S9e|u1)r_dSJ2a?NI4CFnM<0^uS@z_70Z{6>XzGPd%4XfTj_x&m+wE6 z3FuVffCcVs+WINqRR*a$#;Y*}r?)y}qMlv>fm!_sC))O5L2aI|9dyX~(P0XVJ<9d# zi_U5mo3jRU+XUxjPZ>9~uXx*!w8B6c0u!9DT=Mq9W|*Jv^&3Cuv|?KtL2@BCTvD&E>*cvmne*M*jOcKe0qRSOlrnW?Qp8NLbQw9H;! zflx6cA1-JrzZP8U3Qv^g2T1xS$jHFsAwV>?)JNO;)@9~Cf7-KIPga~$m>%zU+;IGA zZ*|LN3f#>!UB)M1vsq8!9zfHUd!Y9saE1-;?GVF6)zCg~8*|eM&cWICqp3pI>@&!$dtgD+<(T?VF?D4T*9G_^lM{PO$ za}RVHi(n;xxf6wEpT-@|u;W8M>D3vxD`=1DDg^HEmGh3NhVM7z>|akak#mml^ctB^ zRS&o*ADJc8q)SX9Uw8B2N6TG}@KUde7$8-dnQ>>wFEY5|U`yjuaf!=GQ(ridmdJS9 zazR1CmvCqz0Q3lD2{Cd>T5TfbX799O`YeOL6mF{j)SNbu!Cg}z9@m+d>EZ>4i`YKkcM@!?#;EY=8e}h z;H6iFF4|}G($PW@yXrK>Jw*kW{$hPD%7e{qzk7}9cn~|U*sR*cs!`s)z^hRKPipCCfkJSl>W(cojxxnp zB2n$wC!!;~v?CKDN*tQ0>J%B0u^O6<@Xb>7@_VoxGSHJ79lbVzfib&u1^sp>n*wFA zupu6$;_)LSYK4K4V}`hwI&IAY_jx9_Xt0a@|Vgn>&y z=-hJbM8(7}uN2i&f1``{JK;@>5j=9Qzbj{4fq$hwc2Y3Tt(?CQoRukN(jV)hrq1Fk zpCFRo8f)naxo#N0u@I01fi;v9zxQy7B()u&vCv(<=Eq|*^M~0x$93&fi}>@v?`!X0 z+pz=ZbLiNXYW}{;m;AYB81v1*6NoDHa{KHCBHbZaosx4hQ=-MD#54GlIUY&u_Nr>`)M(Miqeulq2wnUr+jKf1CsURsjZvNagK&_(WnD7c?$at_ zSncA8*QP!z_#>xb^6A-)PkWULvb7Z6o57FwPR3@N_58u9EGqKY@N-ufg?Opwbyd~= z^)c0=3(rkgZkFZ${HJI%&-`)Ki|5(Lw)q5^&(nj^S|OYmeplXf)9-_*+t15oEg|M` zeC8iP>4g*JQNHhnmGFP zASmE7hQ#z+=v&Z(>Q)ms+*)0+m{^Psd2udJ+lJuWmUSuD3wv69?3rrEU)9S5;wxYL zCjYZ&dMeA{Wo@lF-0q{gU37GpwsnR&CJE49Dc63DzT zGbs0m!XT+){0e_t`jQx8@xJoPn(uMXdcA1VKg4%t8pt231(I3BVO4#Y%1TP$1*TA} zE1aokr_CNRHf28dk|+ABO>~5rP6VW#jn6qKUPPFAk2z)3cSOCp{s#N#^G~Xr!Nu?{sPf5n-&^{_1AW zt$~*BfG2Ido|qJgw7L5W@oKo&QMx<-QYC$~cKQ11dG^8->1$d%PX`lZ2z{T)1=o$2 zznBL-ep{HN(!TcQ#>u&39+3f8b)xsxq>t`|nm&;>8mb!|kb_cNVmD6H#O-bNh51o* z6#0+^F6)bM#`Lb73S`pCM_lO9(Sbq!wStsFOZo0%f{yjOA1jB!O0}QOcGow1yTV}z zLz=e=XwvGdcLfSJ9KRZAJ)p8Q?KB#x zNf$#|Md^FA&O$l$GXsD^TUc_I)JBVTZBu&LqBYY{7bOkt_D zcaw)`h-L(rOl2JT=JX6=57%gOBG z8FP{St~it~xjG_RH>_*$kj#07GI97WWnIOd^Gf+mrQ$m}F#ys5+_ADL>m&WquEVC{ zTebAp&&P5-P8_!qI?Kb_oU6kP!p$=*K49iYEK14wmt)kdp<> zSXK}-M8=yRoM$GOpkqS11???j`uS@;cpLlr!SGN@T-(NsPsc0Vo9e|n8EjCLtZ*hk z6!W4azJlrz39VWgdVUlGDP!WzEWoTr5rf_!Th2m>M%FA_!lXxeYVifZ!KY^DyA|{- zfB8*yxQ?erQg;tHH8NRb4W;t-$y4;dcy97|^mkf~3r7hdxjCz_S2en`WXhb~+>ls~ ztC!7r7H$t^nh?V`+f6p)J`0l@pRuU9h{?3vRF&Y`O+E=cx%O;oae=p)0| zjDiZDERFF8m>al8NIK?3uxD~v`XNJL{7iC*Tw_VjwUu=<_wCc3{<(z%W~He5A!Oh} zl(2$ooZsJKZdHppD+1@ytelm_QyY-FeCNoUh+TnZ^#gsPdw1(7+f*%T)UFAN3a;~f z>@V9f*d;O-^5w+lg?6@kJr{}e^QXs3CAj{&su!vbBkPZKqkjGDWHaIak}X87F1qRH zGwR*u!IW=92STPy9=3Je)yEDp$F0U1GU_Ue%x7Lcejmm^o*qZOk?W$Pet2ohqL<}c zj>!-{D>V}eLYczF1c$|L2`!bU!?#l=I5+$^RadwZ&b2(^4z&;UDPEHe`JMeq*z~FU z9&m&{fSYoO=LIgGWYe&BRLIY?zhn*o49Z?_cUEtQ+)2pVmrZ7^>`b^pB#o9*c;HJK z$`!CVR0`vLe0=xOMg%N+I-PVBN|93D!mvY?yX1J`@z%^T;p}~Cap~yrq*Okkbh8lp zT#SFjx8$w^O2Alh37^(->Zz?e$6{=S%ss<`sG_8Dmj9Qtm|+w&5?m+GF_Gz9T`5m+ z;SMz!9~^$5ZRJj*RzJP359E^jy}r$n+yhEu6H6GUP!7nLF;Dm!0fqt!CdP-Xw_wT7 z{d#K=&3C?}ll*U)JB1O*Qj6%uoYiA(b`;WO)%tJej9vmkCqkn6`M|GF?gA_HZ}q_= zE0;w?n*_=p(6%8s_@`#SXGZXGJ)Xl3zwsAo+YA6Opw4AMUGfzB`xfP`yR8Wcr=&d- zp2#YGAoBxd z+CLlKKH*8lUu87S)uxg7;J||}dKDti(2d8E&D<5p;%pne0{~Hi&jw)Q^fueEtll=7aHvE;LY1 zo9>~U8vlFkY)&ec%4TYn&DGtb>Qx`8-4Awuo*)Nr`tu?e^%1hs5!-dWeJV0-Yv=ne zvlvV~_`!`KyRY;k3!wC^Gl9=pi+#olWsM$U;ybbF{-pKah6@1zOoE4dR}WW2QM+7Z zh6D#4k*3*+Zq#?fYhd*KpB|D$&elUUwc|@5k`|C`2Ro@GYQX0gGp^ZxZGOEx+X5CD z#)~~GDKeO|#YS;#7^ZFf2~ViV@u^=*91s@%>ayrArav4fJ+b=6YR920Zd&j;H9doV zANl*G=h>SIzIWx!yqy)Rw|o8FevI*-OH2ppmLMO=6QqZ+M z=vufetaFwm)v~V_z;TN1@~u8#Bps@5X<70Fh=ZBtEo-9B#*^Abr=tEi&AX$ zg33l~EC$OKjy!NrfV$m%IP781RsG;cT>T}?Xu~^CbfC6}SChVx7mzsKDC>~UqLC8L z2?)G8W7J|Hvj3!tT$_tg%#=SKU`OEtFvE4;jXquR=Rv5;eoXpa!fvvgUk**CY8%7y0ce1?A=u;i5>REnf^@(&?|BoP1w#_zSsAQLs+y@&>4B>Q znmqQ)jaT%levSvqV{}XE3wRT0d%viqIeFQ%Dru{t32Pq~AzLLRpbxvN`d18;yV!;H zbH`NI95S-h^EHE?B@nvX=KzVP%V*aHVN45OOfl}7Ba}W>VInV=)f-wxoQ-RRy~I6= zm9})9Up0Bv~GoXfVvB99|*q+hd zq^=*<>;O=HZuaQ^WIFrKmCMItR)7ycINjX`1Q`LV=HGxaC(tF_QGA$#yZP^cqwW`x zU+a#m-ToH}Kk+=Q{dmCXAQs5|-O*SP;YGkz8*H)yM}U05DRZ81#hRlc!3p){n?=V! zxBt^A2mXh;5jL{eiA_xnpg;r7Zwi5CHJjNgC*T_hl=yb!UwHrj!2AFIga29o_(^b literal 0 HcmV?d00001