Merging Manual Validation with Automatic Testing

Manual Validation Test Scripts vs. Gherkin Features

The table below will help you to understand how the existing manual script pieces correspond to what we need for Gherkin specifications within a REDCap Cypress test.

	Manual Tests	Automated Tests
Validation Test Script	The Word documents that outline how a test functions.	In Gherkin, a "Validation Test Script" is considered a "Feature." The files containing Gherkin specifications are tagged as .feature files.
System Setup	Included in "System Setup" Section at top of Validation Test Script.	Handled on Technical Side of REDCap Cypress test framework in the cypress.env.json file.
Test Summary	Included in Validation Test Script.	Top of .feature file includes statement of what the "Feature" is.
Test Users	Usernames and passwords in Validation Test Script.	Handled on Technical Side of REDCap Cypress test framework within cypress.env.json. All a test script writer needs to know is whether they want a standard user or admin user within the scope of a particular scenario.
Project Setup Steps	- Project - Project Setup - Data Import File - Other Files	Depends on the test as to whether additional setup is needed.
Test Steps: Action Step	Inconsistent for 9.1.3 specs, but tells user what to do and where to go.	Roughly equivalent to action steps within a scenario. Generally "clicks" or "visits" are these kinds of steps.
Test Steps: Expected Result	Describes what the expected conditions are on screen following the action.	Includes the assertions that are made. Generally "should" statements like "should see" or "should NOT see".
Test Steps: Pass / Fail	Describes whether Expected Result was met.	Handled on Technical Side of REDCap Cypress test framework. Displays check for pass, X for fail.