Note
The following instructions apply to TG_UAT draft 19 and higher.
Medidata accounts
To run Test Cases users must have access to Medidata Rave.
The user accounts should be configured with access to the project, environment and site(s) being tested, with roles matching the roles specified in the Test Cases.
The user accounts must also have permission to enter data in the TG_UAT study and site. This applies to all Medidata Rave user accounts for Automated Testing, including those with roles such as 'Data Manager', which do not have data entry permission, in the study(ies) being tested. In the TG_UAT study these users must be assigned a different role in Medidata Rave, one which can enter data into the TG_UAT study.
Rave EDC
iMedidata user accounts are required to run Test Cases for Medidata Rave EDC URLs.
The EDC role assigned to user accounts for TG_UAT data entry must also be used to register the Medidata Rave EDC URL.
An additional Medidata Rave Classic account is required to create subjects. If the Test Case(s) do not create subjects, this account will not be required.
Rave Classic, direct login
Medidata Rave accounts can be used to log in directly to run Test Cases for Medidata Rave Classic URLs.
Rave Classic, iMedidata login
iMedidata accounts can be used to log in to run Test Cases for Medidata Rave Classic URLs.
When using iMedidata accounts for Medidata Rave Classic URLs, the following restrictions apply:
the roles specified in the Test Case(s) must exactly match the Medidata Rave Classic roles
the name of the role used to access the TG_UAT draft must be entered when the Medidata Rave URL is registered and the same role must be assigned to users running Test Cases.