Automated Testing

TrialGrid provides a system for automating testing of studies in Rave EDC. This allows users to write testing scripts which can be run by TrialGrid to enter data into Medidata Rave and collect screenshots of evidence that Edit Checks have fired correctly.

Important

Before you can start running Automated Tests some setup in required on your Medidata Rave URL. See the Getting started guide.

• What is Automated Testing?
• Medidata accounts
  • Rave EDC
  • Rave Classic, direct login
  • Rave Classic, iMedidata login
• Test Case List
  • Test Case PDF
  • Test Case Excel
• Test Case Run Status
  • Warnings
  • Queues
• Test Cases
  • Comments (optional)
  • Referencing Edit Checks and other Draft Objects (optional)
  • Declaring the Feature (required)
  • Declaring Background (optional)
  • Declaring Test Steps (required)
  • Test Step Instructions
  • Declaring Scenarios (required)
  • Test Case Priority
• Editing Test Cases
  • Editor buttons
  • Validation of Test Case content
  • Keyboard shortcuts
• Test Case Templates
  • Template Syntax
  • Optional Fields
  • Optional Forms
  • Optional Folders
  • Custom Properties
  • Folder placeholders
  • Action datapoint placeholders
  • Using For loops to avoid repetition
  • Variables
  • Including content from a Template Test Case
  • Importing a Template Test Case into a Test Case
  • Commenting out a Template structure
• Test Case Advisor
  • Running the Test Case Advisor
  • Test Case Advisor Results
  • Labelling results
  • Object references
  • Links to Test Cases
• How does the Test Case Advisor work?
  • 1. Folders, Forms and Fields
  • 2. Test data values
  • 3. Solutions
• Testing Derivations
• Uploading Test Data
  • Example Upload File
  • Order of data entry
  • Upload File Format
• Test Case Subjects
  • Creating unique subjects per scenario
  • Creating subjects with specified names
  • Using parameters in subject names
• Creating subjects using the Primary Form
  • Modifying Primary Form data for an existing subject
  • Supported fields
  • Errors when creating a new subject
  • Identifying fields on the form
  • Valid sequence of steps
  • Field visibility
  • Saving and cancelling data entry
  • User permissions
• Folder, Form and DataPoint References
  • Nested Folders
  • Parent Folders
  • Absolute Folder References
  • Creating Parent/Child Folders
• Dates and Times in Test Cases
  • Partial dates and times
  • Incomplete dates and times
  • Current date and time
  • Offsets from current date and time
• Running Test Cases
  • Selecting the Rave URL and Environment to Run on
  • Test Run settings
  • User Credentials
  • iMedidata Two Factor Authentication
  • Monitoring Running Tests
  • Cancelling a Test Set Run
  • Archiving Results of Test Set Runs
  • Re-Running a Test Set
  • Server re-starts
  • Test Case Priority
• Whitespace and case differences in test results
  • Datapoint values
  • Query messages
  • Deviation text
  • Folder names
  • Form names
• Historical Automated Test Runs
  • Changes to Test Cases
  • Deleted Test Cases
• Test Archives
• Automated Testing Step Reference
  • Given steps
  • When steps
  • Then steps
• How does Automated Testing Work?
  • TG_UAT Draft 19 and higher
  • TG_UAT Draft 18 and lower
• Automated Testing Limitations
  • Rave EDC (RaveX) Support
  • Test Case Generation Limitations
  • Test Case Limitations
  • Check Actions Not Supported
  • Check Actions Supported
  • Rave XML in Check Actions
• Project Test Configuration
  • Automated Test Configuration
  • Test Case Advisor Configuration
• Medidata Rave URLs