What is Automated Testing?

Testing is usually the last phase of the Study Build process. It is common to write a scripted test for each programmed Edit Check. The script instructs a tester to manually login and enter data into Rave in order to prove that the Check fires or does not fire according to specification. An example test script might look like this:

Name : Check SCREENING_VISIT_DATE Version : 1

Step

Instruction

Expected Result

Actual Result

Comments

User

Date

Pass / Fail

1

Log into EDC using an Investigator role

Login succeeds, user is at Rave User home page

2

Navigate to Site 123

User is at Subject listing for Site 123

3

Create a new Subject with the following data:

Date of Birth = 10 JAN 1978

Subject is created with Date of Birth 10 JAN 1978

4

Navigate to Folder Screening, Visit Form and enter the following data:

Visit Date = 13 DEC 1968

Visit Date for Screening Folder is 13 DEC 1986.

5

Confirm that Edit Check has fired on Visit Date with text “Visit Date is before patient Date of Birth. Please correct.”

Edit Check has fired.

Regardless of the exact format a test script will have at least:

  • A set of actions to take

  • Expected results of those actions

  • A column for the tester to enter actual result

  • A column for the tester to enter any comments (especially in the case of an unexpected result)

  • A date/time for the tester to enter when this test step was performed

  • An initials/signature column for the tester to confirm this step was performed

  • A PASS/FAIL column to document result of the step

Additional evidence may be taken in the form of screenshots.

Writing and executing these test scripts manually takes a lot of effort so many organizations take a risk-based approach and write tests only for a subset of Edit Checks.

TrialGrid Automated Testing makes it easy to create and run these kinds of tests at a fraction of the effort of manually writing them.