Automated Testing Limitations

TrialGrid Automated Testing supports the majority of Medidata Rave Edit Checks but with some limitations.

  • Test cases are not generated for Logical Record Position Edit Checks.

  • Test cases are not generated for Edit Checks using the IsNonConformant or InLocalLabRange step functions.

  • Test data cannot be entered for a Field with a Unit Dictionary if no Unit is specified. This is a limitation of Rave Web Services.

The following Check Actions are not supported by TrialGrid:

  • BalanceCreateSubject

  • BalanceDispense

  • BalancePDALUpdate

  • BalanceRandomize

  • BalanceRandomizeAndDispense

  • BalanceRedispense

  • BalanceSubjectDeactivate

  • MarkActivityComplete

  • OldMrgMatrix

  • RequireReview

  • SendMessage

  • SetFolderRequiresSignature

  • SetFormRequiresSignature

  • SetSecondarySubjectName

  • SetSiteInformation

  • SetSubjectRequiresSignature

The following Check Actions are supported by TrialGrid:

  • AddComment

  • AddDeviation

  • AddForm

  • AddMatrix

  • CustomFunction

  • IsPresent

  • MrgMatrix

  • OpenQuery

  • PlaceSticky

  • RequireVerification

  • SetDataPoint

  • SetDataPointVisible

  • SetDynamicSearchList

  • SetNonconformant

  • SetSubjectName

  • SetSubjectStatus

  • SetTimeForward

  • SetTimeZero

OpenQuery Check Actions using Rave 'gxml' are supported by TrialGrid Test Cases.

AddComment and PlaceSticky Check Actions using Rave 'gxml' are not supported by TrialGrid Test Cases.

TrialGrid uses the Veeva API to run test steps. Because of limitations in the Veeva API the following features are not supported in TrialGrid yet.

  • Form Linking

    This can not be set via the Veeva API.

    Note: Item-to-Form linking is supported.

  • Automatic detection of subject name changes

    If a data entry step changes the subject name there is no indication from the Veeva API that the name has changed and subsequent test steps might fail. To workaround this the 'I select the subject named' step should be added after the data entry step, with the expected new name for the subject.

  • Form screenshots might not always have the form displayed

    Veeva does not have 'stable URLs' for forms. TrialGrid tries to identify the form in the subject and open it for screenshots but this will not be 100% reliable.

  • Mark as blank / intentionally left blank

    This can not be set via the Veeva API.