Module : Automated Testing

Issue	Type	TrialGrid Version	Description
3999	Feature	72	There will be a warning next to a tagged Edit Check in the Test Case Editor if the Edit Check references a Form or Field in in steps or actions which is not included in the Test Case steps.
3981	Feature	72	When registering a Rave Classic URL with the new iMedidata home page the iMedidata Client and Study Group must be entered.
3973	Feature	72	There is a new system configuration setting to control whether Test Case Run debug log messages are created. These log messages are only visible by TrialGrid Ltd staff and will be disabled by default.
3975	Feature	72	Test Case Runs will now fail and stop running when 5 scenarios have failed.
3970	Feature	72	Test Case Run Results which were generated more than 365 days ago will be automatically deleted. The number of days after which they will be deleted can be configured by contacting support@trialgrid.com.
3958	Feature	72	Test Case PDF and Excel files which were generated more than 365 days ago will be automatically deleted. The number of days after which they will be deleted can be configured by contacting support@trialgrid.com.
3968	Feature	72	Test Case PDF and Excel files which were generated more than 365 days ago will be automatically deleted. The number of days after which they will be deleted can be configured by contacting support@trialgrid.com.
3983	Bug	71.2	Further investigation revealed that the problem occurred if an invalid iMedidata password was entered. This has been corrected.
3983	Bug	71.1	There are intermittent problems logging into iMedidata to run Test Cases. A change was made in the TrialGrid code to attempt to resolve this issue.
3960	Feature	71	The list of Matrices which the Test Case Advisor will exclude when choosing a wild-carded Folder can be configured, see How does the Test Case Advisor work?.
3956	Feature	71	The Test Case PDF will include the versions of Medidata Rave, TrialGrid and the TG_UAT draft in the Test Case Run results section.
3957	Feature	71	There is a new option for Test Case PDFs to generate a 'Results' PDF. Test results will be included. Screenshots and test step result text will not be included. There will be less whitespace. The file size of the PDF will be significantly smaller. The previous options for generating Test Case PDFs are still available.
3963	Feature	71	When running Test Cases for Rave EDC URLs with multiple Rave EDC Roles in the test steps the user credentials can be entered for the first EDC role and then, if the same user account is to be used, the credentials do not need to be re-entered.
3964	Bug	71	The warning about a role not being in the core configuration was displayed on the wrong line in the test case run view if there was no blank line between the previous step and the login step. This has been corrected.
3965	Bug	71	The Test Case advisor could fail to generate test cases for Derivations if the Derivation target was a date field. This has been corrected.
3966	Bug	71	The Test Case editor would incorrectly display a warning about whitespace differences on data entry steps for date fields if the data format contained unknown parts. This has been corrected.
3962	Bug	70.2	The 'open primary form to add a subject' step would fail when the study site number was different from the site number in Medidata Rave. This has been corrected.
3961	Bug	70.1	Test Case Runs could fail when using TG_UAT version 19 or higher if a user tried to run a Test Case requiring multiple Rave EDC Roles, entered credentials for an iMedidata account, cancelled, then chose a different Test Case and tried to run that Test Case. This has been corrected.
3948	Bug	70	The Environment Name and Protocol ID were not being remembered correctly after clicking 'Start again' in the Test Set Run wizard. This has been corrected.
3949	Bug	70	The Rave URL version was not being recorded in the Test Case Run log when using TG_UAT version 19 or higher. This has been corrected.
3950	Bug	70	There is an intermittent 'ChangeCode can not be zero' error when running test cases. Additional logging, and a retry, have been added to help resolve the issue.
3951	Feature	70	TrialGrid will automatically switch users to the new Rave EDC user interface if the user's iMedidata account has been upgraded to the new iMedidata home page.
3954	Bug	70	When running automated tests for Rave EDC screenshots could be taken with the wrong EDC role selected if the test case contained multiple login steps with different roles. This has been corrected.
3944	Feature	70	The Test Case and Data Advisors can be configured to generate dates with an offset from the base date, see Test Advisor Instructions.
3945	Feature	70	The Test Data Advisor for Matrices will generate a log record for each Default Value defined for a Field.
3946	Feature	70	The Test Data Advisor for Matrices can be configured to generate a number of log records, for all log forms or specific forms, see Test Advisor Instructions.
3942	Feature	70	The Test Data Advisor for Matrices has a new option to report coverage of the draft; which forms, fields and data dictionary entries have not been included in the test data.
3941	Bug	70	The 'I assign lab' test step would fail if the lab name contained lower case characters and the Rave core configuration was set to upper case data entry. This has been corrected. Version 23 of the TG_UAT draft is required for this feature.
3936	Feature	70	The Test Case and Data Advisors can be configured to use specific values for fields using Instructions, see Test Advisor Instructions.
3937	Feature	70	The Test Case and Data Advisors can be configured to use low and high ranges for numeric fields using Instructions, see Test Advisor Instructions.
3938	Feature	70	The Test Case and Data Advisors can be configured to use low and high dates for date fields using Instructions, see Test Advisor Instructions.
3939	Feature	70	The base date used by the Test Case and Data Advisors can be configured using Instructions, see Test Advisor Instructions.
3940	Feature	70	The date increment used by the Test Case and Data Advisors can be configured using Instructions, see Test Advisor Instructions.
3929	Feature	70	The Test Data Advisor for Matrices will not include data for inactive Forms.
3930	Feature	70	The Test Data Advisor for Matrices will create one scenario for each Folder.
3931	Feature	70	The Test Data Advisor for Matrices will allow the creation of multiple subjects, creating one test case for each subject.
3932	Feature	70	The Test Data Advisor for Matrices will create different data values each time it chooses a value for a field.
3933	Feature	70	The Test Data Advisor for Matrices will choose dates and times in sequence for each value chosen for a field.
3934	Feature	70	The Test Data Advisor for Matrices will choose date values with unknown parts when the field format has unknown date parts.
3920	Feature	70	There is a new test step to ensure that all Folders/Forms in a Matrix exist in the subject. TG_UAT version 21 or higher is required for this step.
3923	Feature	70	The Test Data Advisor for Matrices has a new option to choose whether Folders and Forms are created in separate steps or using the new test step for matrix folder/forms - see #3920.
3924	Feature	70	The Test Data Advisor for Matrices has a new option to choose whether to delete existing Test Cases.
3925	Feature	70	The Test Data Advisor for Matrices will not include data for any Forms which are view or entry restricted to the selected role.
3926	Feature	70	Matrices can be added as tags in Test Cases.
3927	Feature	70	The Test Data Advisor for Matrices will insert tags for the selected matrices.
3928	Feature	70	The Test Data Advisor for Matrices will create a test case with the OIDs of the selected matrices in the name.
3919	Feature	70	The Test Case Advisor has a new option to generate additional scenarios using a 2nd folder, if there are wildcarded folders in the Edit Check steps.
3856	Feature	70	The Test Case editor will now display a warning if a date/time value in a data entry step has different whitespace compared with the Fields data format.
3918	Bug	69	During platform maintenance the servers running test cases might need to be restarted. This will now happen automatically.
3914	Bug	68.8	When checking access to run Test Cases in a Rave EDC URL there would be an error if the user's default environment for that study was not the same as the environment in which to run Test Cases. This has been corrected.
3912	Bug	68.7	Test set runs could fail when the user had new iMedidata and new Rave but old TG_UAT version. This has been corrected.
3905	Bug	68.6	Test case runs would fail to add a matrix with a single quote character in the matrix name when testing in a Rave EDC URL. This has been corrected.
3903	Bug	68.5	The Test Set Run wizard would fail to find a site in the new iMedidata/Rave EDC header if the site number contained a hyphen character. This has been corrected.
3898	Bug	68.4	The Test Case Advisor would fail to generate a Test Case if an edit check has a time field and a static time value and additional scenarios were requested. This has been corrected.
3899	Bug	68.4	The Test Set Run wizard could fail if 'check user roles' was not selected. This has been corrected.
3895	Bug	68.3	An error will now be displayed if a user tries to run a test case when: the Rave EDC URL has TG_UAT version 18 or lower installed and the user has the new iMedidata home page and the 'UAT Subject URL' has not been configured in the TrialGrid Project
3897	Bug	68.3	There is a new configuration option for TrialGrid administrators to control how long TrialGrid will wait after clicking the Cancel button on a Rave EDC datapage.
3894	Bug	68.2	Test Case Runs on Rave EDC URLs could fail due to a problem in refreshing Rave EDC datapages. This has been corrected.
3892	Bug	68.1	Test Case Runs could become stuck in a loop while checking if the Medidata Rave error page was displayed. This has been corrected.
3880	Bug	68	The Test Case Advisor would fail if there was a derived field in the check steps with an IsEmpty or IsNotEmpty function, and additional scenarios were requested. This has been corrected.
3868	Bug	68	The Add Event Test Case step was not working correctly on some Rave URLs. This has been corrected.
3846	Feature	68	The new iMedidata home page is supported when running test cases on Medidata Rave EDC URLs.
3847	Feature	68	The new iMedidata home page is supported when registering Medidata Rave EDC URLs.
3848	Feature	68	The Medidata 'Protocol ID' is required when running test cases on Rave EDC URLs.
3849	Feature	68	The Medidata 'Environment Name' is required when running test cases on Rave EDC URLs.
3850	Feature	68	The Protocol ID will be automatically set to the Study name in the Automated Test Configuration for existing Projects.
3851	Feature	68	The Environment Name will be automatically set to the corresponding standard Environment in the Automated Test Configuration for existing Projects.
3852	Feature	68	The Protocol ID will be automatically set to the Study name in the Automated Test Configuration for existing Test Set Runs.
3853	Feature	68	The Environment Name will be automatically set to the corresponding standard Environment in the Automated Test Configuration for existing Test Set Runs.
3854	Feature	68	The URL of the TG_UAT subject must be entered in the Automated Test Configuration section for Projects using TG_UAT version 18 or earlier.
3864	Bug	67.4	When running tests for Rave EDC using TG_UAT version 21 the Create subject step sometimes failed with message "Create subject user account not found" when the classic Rave account had the same role name as the EDC account. This has been corrected.
3861	Bug	67.3	Data entry steps could fail if a form was added using an 'Add form' step, then removed and added again in custom functions with Merge/Unmerge matrix actions and then used in a data entry step. This has been corrected.
3862	Bug	67.3	When running tests for Rave EDC using TG_UAT version 21 the Create subject step sometimes failed with message "Create subject user account not found". This has been corrected.
3842	Bug	67.1	Test Case Runs would fail if the registered Medidata Rave URL had a trailing slash. This has been corrected.
3811	Feature	67	There is a new Organization report showing the number of screenshot files for Test Case Runs, per Project.
3812	Feature	67	There is a new Organization report showing the number of screenshot files which will be deleted (see #3810 below), per Test Case Run.
3809	Bug	67	Obsolete Test Case Run screenshots were not always being deleted, for example when deleting a Test Set Run. This has been corrected.
3810	Feature	67	There is a new configuration option for Organizations to delete screenshot files for Test Case Runs older than the specified number of days. By default this option is disabled and no screenshot files will be deleted. TrialGrid administrators can configure this option on request.
3766	Feature	67	The 'validate' button has been removed from the Test Case Editor. The button was not needed because Test Cases are automatically validated when the content is changed.
3767	Feature	67	The Test Case editor will not display the error count and warning count in the toolbar as well as at the bottom of the page.
3768	Feature	67	The Test Case editor will display a 'waiting' icon instead of the error and warning counts if validation is taking longer than 2 seconds.
3029	Feature	67	When using the helper to edit data entry tables, any comments, commands and empty lines in the table will now be preserved in the same location when the table is updated.
3769	Feature	67	The 'has text' and 'does not have test' test steps will display an error if no text provided in the Test Case
3770	Bug	67	The lint markers for errors and warnings inside templates were not displayed on the correct line when the template was included in a Test Case. This has been corrected.
3771	Feature	67	The Test Case editor will display errors on lines which require a subject to have been selected or created if no subject has been selected or created in a previous step.
3772	Feature	67	The Test Case editor will display errors if the necessary steps for data entry on an open form are not present. See Creating subjects using the Primary Form.
3758	Feature	67	There is a new test step (for Rave EDC only) to open the primary form to add a new subject. See Creating subjects using the Primary Form.
3773	Feature	67	There are new test steps (for Rave EDC only) to verify that a subject has, or has not, been created after saving data on the primary form. See Creating subjects using the Primary Form.
3774	Feature	67	There is a new test step (for Rave EDC only) to open the primary form for an existing subject. See Creating subjects using the Primary Form.
3775	Feature	67	There is a new test step (for Rave EDC only) to enter data on an open form. See Creating subjects using the Primary Form.
3776	Feature	67	There are new test steps (for Rave EDC only) to wait for a field to become visible on an open form, waiting for a default or specified time. See Creating subjects using the Primary Form.
3777	Feature	67	There are new test steps (for Rave EDC only) to wait for a field to become not visible on an open form, waiting for a default or specified time. See Creating subjects using the Primary Form.
3778	Feature	67	There are new test steps (for Rave EDC only) to save data on an open form, waiting for a default or specified time. See Creating subjects using the Primary Form.
3779	Feature	67	There is a new test step (for Rave EDC only) to cancel data entry on an open form. See Creating subjects using the Primary Form.
3780	Feature	67	There is a new test step (for Rave EDC only) to refresh an open form. See Creating subjects using the Primary Form.
3781	Feature	67	The "I Wait" step now accepts integer or decimal values between 0 and 3600 seconds.
3793	Feature	67	There are new test steps (for Rave EDC only) to save data on the primary form, waiting for a default or specified time, and check if the subject has been created or not. See Creating subjects using the Primary Form.
3800	Bug	66.1	There is sometimes an error logging into iMedidata when running Test Cases for Medidata Rave EDC. Additional logging has been added to help investigate the cause of the error.
3802	Bug	66.1	There was a javascript error if a user clicked on the 'Add Step' button in the Test Case editor with no step selected. This has been corrected. The user would not have seen this javascript error.
3806	Bug	66.1	There was a javascript error if a user deleted a Test Case in the Test Case list, and then tried to delete another test case. This has been corrected.
3798	Bug	66	Test Cases were not running on Medidata Rave Classic URLs when using iMedidata logins. This has been corrected.
3787	Bug	66	The Test Case Advisor could fail if an Edit Check contained static values for a text field and static values for a date or time field. This has been corrected.
3786	Bug	66	Tags and line breaks in Test Case data table values could cause errors in PDF generation. This has been corrected.
3755	Feature	66	When entering data on landscape Forms data will be entered in one transaction for all records (standard and log) which exist on the form. Data for log records which do not already exist will be entered in separate transactions. This feature is only applicable when using TG_UAT version 21 or higher.
3762	Feature	66	There are new Test Case steps to check if a query is open, or not open, for a specified Marking Group. These steps are only available when using TG_UAT version 21 or higher.
2891	Feature	65	There are new Test Case steps to check if a form is Active or Inactive. These steps are only available when using TG_UAT version 21 or higher.
3744	Bug	64.2	Data entry on the primary form immediately after the subject was created could fail in Rave EDC tests. This has been corrected.
3734	Bug	64.1	The screenshot for a Rave Classic log record was not open on the log record if data has been entered onto the log record in the immediately preceding test step. This has been corrected.
3736	Bug	64.1	Query text was not being highlighted on Rave Classic datapages if another field had the same query message and a pretext which contained the pretext of the field to be highlighted. This has been corrected.
3737	Bug	64.1	A system configuration setting used by TrialGrid to determing how long to wait for a datapage to be saved was not being set correctly for Rave EDC. This has been corrected.
3718	Feature	64	There is a new Organization default setting for the Test Case runs which will cause test case query steps to fail if there is any difference between the expected query message and the actual message. Whitespace differences and differences in case will cause the step to fail. The default setting is that whitespace and case differences will not cause the steps to fail. Please contact support@trialgrid.com if you would this setting to be configured.
3714	Feature	64	There will be a warning in the Test Case editor if a data entry step has a value which is not 0 or 1 for a checkbox field.
3715	Feature	64	If a checkbox field in a Test Case data entry step has an empty value, TrialGrid will automatically enter 0 (not checked) as the value.
3716	Feature	64	When testing against a Rave Classic 2024.1.1 URL, if a value for a checkbox field is not 0 or 1 then the value will be marked as non-conformant. Rave EDC URLs will not mark the value as non-conformant.
3717	Feature	64	Users can run test cases on Rave EDC URLs if they have a different EDC role for the TG_UAT draft from that used to register the Rave URL.
2637	Feature	64	Test Cases can now have an optional Priority. Test Cases will be run in priority order.
3449	Feature	64	Steps for testing data values will highlight differences in whitespace in the test results.
3450	Feature	64	There will be a warning in the Test Case editor if the expected value in a datapoint 'has value' step contains line break characters r, n or <br/>, in which case the 'has text' step should be used.
3607	Feature	64	When using TG_UAT draft 21 or higher, if a Form cannot be found the test results will display any Edit Checks with AddForm check actions for that Form and Folder.
3329	Feature	64	When using TG_UAT draft 21 or higher, steps testing Folder Names will match if the only differences are in whitespace and/or upper/lower case. The differences will be highlighted in the test results.
3696	Feature	64	When using TG_UAT draft 21 or higher, steps testing Form Names will match if the only differences are in whitespace and/or upper/lower case. The differences will be highlighted in the test results.
3686	Feature	64	If there is a system error while starting a Test Case Run there will be an entry in the Test Case Run log.
3690	Feature	64	The Test Case editor will display an error if the "Dynamic Search List should contain the following values" step references a Field which is not a Dynamic Search List.
3694	Feature	64	When viewing history on the Test Case Run status page the URL totals will display a count of passed and failed test cases in that period.
3725	Bug	63.3	Test Case generation using the Test Case Advisor could sometimes fail for Edit Checks with fields not visible by default. This has been corrected.
3729	Bug	63.3	The Test Step to check values in a Dynamic Search List would fail if the value in the Dynamic Search List starts or ends with whitespace characters. This has been corrected.
3730	Bug	63.3	Test Steps running against Rave EDC could become stuck and not complete. This has been corrected.
3712	Bug	63.2	Additional logging was added to assist with debugging issue #3712 (see below).
3713	Bug	63.2	An incorrect error message was displayed if two test case scenarios tried to enter data into a form which did not exist in the Medidata Rave subject. This has been corrected.
3712	Bug	63.1	There is an intermittent problem when running Test Cases against Rave EDC URLs where there is no response from Rave EDC after saving data. TrialGrid will now try to reload the Rave EDC page to collect results.
3665	Bug	62	If a Test Case had started running and then the Test Case was deleted and a new Test Case with the same name was created then when trying to run the new Test Case there would be an error. This has been corrected.
3639	Bug	62	Invalid Test Cases could be run by clicking on the Run button in the right-hand column of the Test Case list. The Run button in the list is now disabled for invalid Test Cases.
3646	Feature	62	It is now possible to register Medidata Rave Classic URLs and run Test Cases on them using iMedidata accounts.
3659	Bug	62	Test steps would fail when checking a query message containing curly braces, {}, and where there was whitespace difference between the expected query message and the actual query message. This has been corrected.
3669	Bug	61.3	If a Test Case with multiple login roles was run against a Rave EDC URL using the same iMedidata account for each role, it was possible that the associated Rave Classic role could be wrongly assigned. This has been corrected.
3663	Bug	61.2	When running Test Cases on Rave EDC URLs using TG_UAT version 21 the 'inactivate record step' would fail if the log record to be inactivated was scrolled off the bottom of the page. This has been corrected.
3631	Bug	61	The URL Registration wizard would not show the final page if iMedidata 2FA was required. This has been corrected.
3633	Bug	61	The Test Set Run wizard was always prompting for the 'Create Subject' credentials for Rave EDC tests, even after those credentials had been entered. This has been corrected.
3634	Bug	61	There could be a timeout error when taking a screenshot of a very large landscape log form in Rave Classic. This has been corrected.
3635	Bug	61	Test Cases containing template structures such as for loops could become longer than the maximum allowed characters. An error message will be displayed.
3636	Bug	61	The Test Set Run wizard was not prompting for the 'Create Subject' credentials for Rave EDC tests if the Test Case contained 3 EDC roles. This has been corrected.
3620	Feature	61	When a Test Case PDF is generated TrialGrid can send an email on completion to the user who requested the PDF.
3630	Bug	60.5	In Test Cases with multiple user login steps, there could be intermittent errors logging in with the new user account when using TG_UAT version 21. This has been corrected.
3623	Bug	60.4	When using TG_UAT version 21 the 'Activate log record' step was not creating a new log record if the record did not already exist. This has been corrected.
3624	Bug	60.4	Multiple, simultaneous generation of the same Test Case PDF can cause errors accessing the image files to construct the PDFs. This has been corrected.
3621	System	60.3	Creating zip files with a large number of Test Case PDFs was consuming a lot of memory on the TrialGrid server. Less memory will be used now.
3619	Bug	60.2	The server on which Test Case PDF files are created could run out of disk space. Temporary image files are now deleted to avoid this.
3618	Bug	60.2	When viewing results for Test Cases with data entry steps in the Background section, the data entry table could be incomplete. This has been corrected.
3617	Bug	60.1	The server on which Test Case PDF files are created could run out of disk space. Temporary PDF and Zip files are now deleted to avoid this.
3605	Bug	60	Test Case PDF generation could fail if a data entry step in a test result scenario contained Folder.Form.Field OIDs with a combined length of 59 characters and that row in the table coinciding with a page break. This has been corrected.
3597	Feature	60	There is a new configuration setting to disable Test Case Run worker replacements. This is a system change, not visible to users.
3596	Bug	60	Test Case Runs could be marked as Passed if there was a failed scenario and then the Test Case Run was paused and re-started. This has been corrected.
3604	Bug	60	The counts of scenarios passed and failed on the Test Set Run page could become incorrect. This has been corrected.
3603	Feature	60	When generating Test Case PDFs there will be progress messages while screenshots are being downloaded.
3579	Feature	60	When running Test Cases against an iMedidata URL the iMedidata username will not now default to the user's email address.
3578	Feature	60	There is a new Test Step 'I view Rave audit records for "{datapoint}"' which will display Rave audit records for the specified datapoint. Version 21 of the TG_UAT draft is required for this feature.
2098	Feature	60	There is a new Test Step 'I should see Rave audits for "{datapoint}"' which will check that specified Rave audit records exit for the datapoint. Version 21 of the TG_UAT draft is required for this feature.
3581	Feature	60	The results for the 'I create or select the subject named' step will now display whether the subject was created or selected.
3582	Feature	60	If a Form does not exist in the SUBJECT folder TrialGrid will not attempt to verify if the SUBJECT folder exists in Medidata Rave.
3584	Feature	60	When viewing a Test Case run there will be warnings displayed if, for example, a Folder has parent Folders and is not referenced by an absolute folder path. If there are multiple warnings for the same Folder in the same step, only 1 warning will be displayed.
3588	Feature	60	When viewing a Test Case run the results for each step will be in a green bordered box if the test has passed and a red bordered box if the test case failed.
3589	Feature	60	When viewing a Test Case run there is a new option to view only Failed test steps.
3590	Feature	60	When viewing a Test Case run there is a new option to view only the currently running test step.
3591	Feature	60	The Test Case editor will now highlight strings in blue, not in red. This is a visual change only, to improve usability.
3592	Feature	60	There is a new Test Step 'there should not be a closed query on {datapoint}'.
3593	Feature	60	When viewing a Test Case run whitespace or case differences between an expected query message and the actual message will be highlighted, to make it easier to view the differences.
3580	Bug	60	In a test case if a table is ended with an escape character (a ) instead of a | symbol, an error occurs. This was corrected.
3598	Bug	59.2	When running Automated Tests on Rave EDC URLs, the test case could become stuck in an infinite loop if an error occurred while trying to open a form from the Rave EDC sidebar. The error will now be reported and the Test Case will fail.
3599	Bug	59.2	Screenshots were becoming too large during Test Case runs. This has been corrected.
3601	Bug	59.2	Test Case PDF generation could fail if a data entry step in a test result scenario contained a value between 16 and 19 characters in length on a row coinciding with a page break. This has been corrected.
3569	Bug	59.1	The Create Subject step is failing on Rave EDC URLs with TG_UAT version 20. Version 21 of the TG_UAT draft is required for this fix.
3578	Feature	59.1	When Automated tests enter data into Rave the Rave audit trail should show the user account running the test, not 'system' Version 21 of the TG_UAT draft is required for this fix.
3583	Bug	59.1	Some screenshots were not showing the complete Rave datapage. This has been corrected.
3566	Feature	59	Additional validation has been added to the Automated Test Configuration tab on the Edit Project page.
3560	Feature	59	There are new Organization default settings for the Test Case Advisor which make the 'Unknown date', 'Additional scenarios' and 'Additional log record' default to be selected. Users can still change these settings if they wish when running the Test Case Advisor. Please contact support@trialgrid.com if you would these default settings to be configured.
3561	Bug	59	The Test Case list was not remembering the 'Not run' or 'Running' filter selections when re-visiting the page. This has been corrected.
1564	Feature	59	The Test Case list now includes a column showing when Test Cases were last run.
3555	Feature	59	The background worker to generate Test Case PDFs will be scaled down when no PDFs have been requested for a period of time. The background worker will be scaled up automatically when a PDF is next requested. There may be a short delay while the worker is scaled up before the PDF is generated.
3558	Feature	59	The background workers to run Test Cases will scale up and down automatically depending on the volume of Test Case Runs. There may be a short delay while a worker is scaled up before a Test Case starts running.
3559	Feature	59	When a background worker is scaled down, any Test Cases which are running on it will be automatically transferred to another worker.
3570	Bug	58.2	Custom logos were not being included in Test Case PDFs. This has been corrected.
3543	Bug	58	When checking the subject calendar, TrialGrid was not finding sub-folders. This has been corrected. Version 20 of the TG_UAT draft is required for this fix.
3542	Bug	58	When entering data onto a Form containing a derived Field, the status of the derived Field in Medidata Rave is now Frozen, for consistency with data entry directly in Medidata Rave. Version 20 of the TG_UAT draft is required for this fix.
3478	Bug	58	When running an Automated Test on a Form with entry restrictions, TrialGrid was submitting the entry restricted fields. This has been corrected and fields which are entry restricted to the test user will not be submitted. Version 20 of the TG_UAT draft is required for this fix.
3541	Feature	58	The Test Case editor will display a warning if multiple Edit Checks reference the same query message, on the same datapoint.
3534	Feature	58	When clicking on a related object in the Test Case list, it will open in a modal window. When right-clicking on a related object in the Test Case list, and choosing 'Open in new tab', the related object will be opened in a new tab.
3524	Bug	58	Rave EDC URLs were not being registered correctly. This has been corrected.
3553	Bug	57.3	When running automated tests, TrialGrid launches a Chrome browser for each Test Case run. Chrome was downloading a large file on startup which, after many Test Case runs, was consuming too much disk space on the TrialGrid servers. Chrome will not now download this large file, and any other temporary files which Chrome creates will be deleted.
3518	Bug	57.1	The screenshot could be out of date when a select value from DSL step was followed a data entry step, on the same form. This has been corrected.
3515	Bug	57	An error could occur when testing a Form containing a 'NOW' derivation triggering a custom function which adds new instances of the form. This has been corrected in TG_UAT draft 19 and higher.
3512	Feature	57	The "I should see {datapoint} has value" test step would pass if the actual value was the same as the expected value, but the actual value was non-conformant. This has been changed so that this step will fail if the value is non-conformant. This change is implemented for TG_UAT version 19 and higher.
3513	Feature	57	There are new test steps "I should see {datapoint} has non-conformant value" and "I should see {datapoint} has non-conformant text" which can be used to verify the non-conformant data values. This change is implemented for TG_UAT version 19 and higher.
3493	Feature	57	The Subject CRF Version ID will be displayed when a subject is created or selected. This change is implemented for TG_UAT version 19 and higher.
3498	Feature	57	The Import Test Case list can now be filtered by the status of the last Test Case Run (Passed/Failed).
3514	Feature	57	The Import Test Case list now displays the number of scenarios for each Test Case.
3509	Feature	57	There is a new page to view the Medidata Rave URLs which have been registered to run Test Cases.
3487	Feature	57	When running Test Cases, the Medidata Rave URL can be selected from a list of registered Medidata Rave URLs.
3510	Feature	57	Authorized users can register Medidata Rave URLs. Please contact support@trialgrid.com if you would like permission to do this.
3511	Feature	57	Authorized users can delete Medidata Rave URLs. Please contact support@trialgrid.com if you would like permission to do this.
3505	Feature	57	Document Templates can now include details of the changes made to Test Cases each time the Test Case is saved. These details are not available for changes made before this release.
3381	Feature	56	The 'I inactivate folder' Test Case step has been retired. No Test Cases were using this step.
3389	Feature	56	A maximum of 3 Rave Roles can be used when running Test Cases.
3390	Feature	56	An error will be displayed in the Test Case editor if the same Rave Role is used with different case, e.g. 'Investigator' and 'investigator'.
3391	Feature	56	The 'Subject Admin' role is no longer required when running Test Cases with TG_UAT version 19.
3517	Feature	56	TrialGrid no longer uses Rave Web Services to run Automated Tests when TG_UAT version 19 or higher is used.
3458	Bug	56	When running Test Cases for Rave EDC, screenshots could be scrolled to the right when a field has a data dictionary with long user strings and a query is open on the field. This has been corrected.
3480	Feature	56	When using TG_UAT version 19 there will not be a screenshot for 'Form exists' steps.
3492	Bug	55.3	Datapoint references with spaces before or after OIDs, for example ' SCREENING.DM.AGE' caused errors in the Test Case Data view and in Excel and PDF reports. This has been corrected.
3475	Bug	55.1	Diagnostic 146 did not properly record its results. When these results were explained, each individual explanation was associated with every result causing a multiplication of explanations and results. This could cause display timeouts and reports to fail to generate.
3476	Bug	55.1	When explaining a diagnostic result the activity record shows the diagnostic result text and not the text entered by the user. This was corrected.
3469	Bug	55	The Test Case Advisor would suggest an invalid scenario if an Edit Check was comparing 2 date Fields with unknown days, and the default unknown day for the Project was the same as the day of the month on which the user ran the Test Case Advisor. This has been corrected.
3457	Bug	55	If a Test Set Run took longer than 1 day to complete, the Test Cases run after 1 day would be queued but would not run. This has been corrected.
3425	Feature	55	The Test Case Excel list, available on the Test Case list page, now includes columns with the Folder Name, Form Name and Field PreText. For each datapoint (if any) in a 'then' step, the Folder, Form and Field columns will be included. The query text will be included in the expected scenario result.
3442	Bug	54	When running Test Cases for Rave EDC URLs, TrialGrid was sometimes waiting too long before opening a log record to take a screenshot. This delay has been removed.
3438	Bug	53.2	On some Rave URLs, calls to Rave Web Services are randomly returning HTTP 500 errors when creating subjects, but the subject is still created. This can cause Test Case runs to fail with a 'duplicate subject' error. TrialGrid will now detect these errors and continue using the initially created subject.
3435	Bug	53.1	On some Rave URLs, calls to Rave Web Services are randomly returning HTTP 500 errors, causing Test Case runs to fail. TrialGrid will now automatically retry after these errors.
3403	Feature	53	The Test Case Excel report now includes a worksheet 'Data Table' which displays the data and actions for each Test Case scenario is tabular format.
3404	Feature	53	The Test Case Advisor has a template which specifies the structure and content of the Test Cases. This template can now reference the draft, project and URL so that, for example, different content can be generated for different URLs in an organization. The template can be modified by TrialGrid Ltd. Contact support@trialgrid.com if you would like to do this.
3405	Bug	53	The Test Case Advisor was not creating a Test Case when 'Additonal Scenarios' was selected and the initial scenarios had issues preventing complete scenarios from being generated, such as a Custom Function in the Check Steps. The Test Case Advisor will not now try to create additional scenarios if there are issues in the initial scenarios.
3401	Bug	52.3	When running Test Cases with many scenarios on a Rave EDC URL, the user session was being logged out repeatedly, leading to slower test case run times. This has been corrected.
3399	Bug	52.3	Test Case advisor fails if 'additional scenarios' chosen when creating the Test Case AND there is a Field which is not visible by default AND the Edit Check has one or more fields referenced by 'UserValue'. This has been corrected.
3387	Bug	52.2	When testing on a log record form with an inactive record, adding a new record was not triggering custom functions. This has been corrected.
3379	Bug	52	Some Test Cases were running slower than expected. This has been corrected.
3378	Bug	52	When saving a Test Case Template, sometimes the related Test Cases were not being updated. This has been corrected.
3349	Feature	51	The Excel report, on the Test Case list page, now contains worksheets summarizing test scenarios for queries, deviatons, dynamics, field visibility and field values.
3305	Feature	51	The Test Case PDF report has a new option to select the number of Test Cases which should be included in each merged PDF file.
3335	Bug	51	The scenario passed/failed count on the Test Set run page could be wrong if a Test Case run had been restarted. This has been corrected.
3337	Feature	51	The Test Case Advisor will now use the static value closest to a Field when an Edit Check contains multiple OR steps.
3332	Feature	51	The Test Case Advisor will now create additional scenarios for Edit Checks which have two 'IsNotEmpty' steps.
3366	Bug	50.2	Some requests to Rave Web Services are unexpectedly failing when running automated tests against some Rave EDC URLs. These errors should now be handled by TrialGrid.
3330	Bug	49.4	If a Medidata Rave URL has multiple web servers, and Rave Web Services on one of the web servers is returning errors, TrialGrid should retry requests to RWS until one of the requests reaches a Medidata Rave web server which is operating normally. This extends the scope of retry requests (see 49.3 below).
3330	Bug	49.3	If a Medidata Rave URL has multiple web servers, and Rave Web Services on one of the web servers is returning errors, TrialGrid should retry requests to RWS until one of the requests reaches a Medidata Rave web server which is operating normally.
3310	Bug	49.2	When saving test cases with errors, the internal count of steps was not set correctly. This had no impact on users, it is just an internal metric. The issue was corrected.
3302	Bug	49.1	Test Steps would sometimes fail, at random, with a 'ConnectionError' when there was a problem with the communication between TrialGrid and Medidata Rave. TrialGrid will now automatically retry the request to Medidata Rave if this errors occurs.
3308	Bug	49.1	Data entry into Fields which were made visible by data entered into other Fields in the same step could fail. This has been corrected.
3309	Bug	49.1	During daily TrialGrid server restarts, a test step could fail with a server error in the run log, but then on restart of the servers the remaining steps, and the overall test case could pass. If a test step fails with a server error during the daily server restart, then the whole test case will be re-run.
3311	Bug	49.1	Extremely long Test Cases could run for more than 24 hours, and be restarted indefinitely after daily TrialGrid server restarts. There is now a time limit of 20 hours, after which a Test Case run will be stopped and the Test Case run will fail. Long Test Cases should be reduced in size and/or split into several smaller Test Cases.
3287	Bug	49	In Test Case runs, TrialGrid would create new log records on Forms with fixed default values. This has been corrected. Draft TG_UAT Version 18 is required for this change.
3288	Bug	49	In Test Case runs, default values were not always being submitted when the page was saved. This has been corrected.
3289	Feature	49	Test Case results will display a table of all queries on a datapoint, including closed ones, when verifying queries on a datapoint.
3285	Feature	49	There are new Test Case steps to check for Open, Answered and Closed queries.
3265	Bug	49	Pending Test Case runs were displaying with a green background in the Test Case list. This has been corrected.
3261	Bug	49	The Test Case editor was not flagging errors if a string used as a placeholder also contained placeholder tags. This has been corrected.
3152	Feature	49	The current date and/or time can now be used in Test Cases. See Dates and Times in Test Cases.
3263	Feature	49	The Test Case Advisor will now produce better test scenarios for Edit Checks which have a leading 'IsEqualTo' step and multiple IsEmpty/IsNotEmpty 'or' steps, and for Edit Checks which include a Field with a Data Dictionary which has only 1 entry.
3262	Feature	49	The Test Case Advisor will remember the options selected by the user.
3267	Bug	48.1	The Test Case editor helper for 'I enter and save data on active fields' steps was changing the step to 'I enter and save data'. This has been corrected.
3276	Bug	48.1	The Test Case editor helper for 'enter data' steps was removing blank lines after the end of the data table. This has been corrected.
3252	Bug	48	The Test Case Advisor was sometimes suggesting invalid scenarios when generating unknown date scenarios. This has been corrected.
3253	Feature	48	The Test Case 'Data' view will now display a short name for the test steps when 'Actions' are selected.
3239	Feature	48	The custom functions in the TG_UAT Draft have been modified so that they do not throw exceptions. Draft TG_UAT Version 17 is required for this change.
3110	Feature	48	There is a new Organization configuration setting which, when turned on, will cause a Test Case to fail if the expected query is open more than once. By default, this option is turned off. Please contact support@trialgrid.com to turn on this option.
3240	Feature	48	There is a new Test Step which will allow multiple queries to be open on the same datapoint, even if the Organization configuration does not allow it. For example: Then I should see the following query on "AE.AE.AETERM" [multiple allowed]
3242	Feature	48	The Test Case results will display the expected and actual query messages if there are only whitespace and/or case differences.
3238	Feature	48	When a TrialGrid server which is running Test Cases is re-started, the Test Case will resume from the step which was last executed, if possible.
3248	Bug	47.2	Some Test Case steps were incorrectly being marked as passed when the datapoint reference contained folder repeats which do not exist in the Rave subject. This has been corrected.
3222	Feature	47	Test Case runs are now processed by a shared worker process.
3226	Feature	47	The Test Case Run status page now contains a summary of the number of Test Cases pending or running for each Rave URL, and the maximum number of concurrent runs allowed for the Rave URL.
3209	Feature	47	The Test Case Advisor will not now use a separate step for entering values into DSL fields.
3210	Feature	47	The Test Case Advisor will try to generate test cases by changing one value at a time, if the Edit Check has only empty and/or isnotempty steps.
3218	Bug	47	The Test Case Advisor was sometimes creating data values with scientific notation (for example '5.000000E+08'), which is non-conformant on entry into Rave. This has been corrected.
3219	Bug	47	The Test Case Advisor was sometimes creating invalid scenarios for Fields with partial dates. This has been corrected.
3154	Bug	47	The Automated Test Step Reference page in the Help documents contained 'smart quotes' in the step headings. These have been replaced with double-quotes.
3028	Feature	47	In the Edit Check Quickedit view, comments can be added at the end of step lines. This feature is disabled by default. Please contact support@trialgrid.com if you would like this feature to be enabled.
3215	Bug	46.6	The 'enter and save data on active fields' step would sometimes fail if all Fields in the step were missing or inactive. This has been corrected.
3216	Bug	46.6	Data entry steps containing multiple Forms where not triggering Edit Check actions for each form, which could lead to failures if the actions are required to add forms or records. This has been corrected.
3217	Bug	46.6	Test Case Runs could become slow with multiple concurrent users. This has been corrected. Draft TG_UAT Version 16 is required for this fix.
3172	Bug	46.4	Duplicate queries were being opened when entering data into mixed Forms. This has been corrected.
3171	Bug	46.3	Test Case runs were not saving default values on Fields. This has been corrected. Draft TG_UAT Version 15 is required for this fix.
3166	Bug	46.2	Some Test Cases were failing when entering data into Forms containing Derivations. This has been corrected.
3163	Bug	46.1	Test Cases were being displayed as 'Changed' after being run. This has been corrected.
3151	Feature	46	When a Test Case is created using the Test Case Advisor, the Activity Record will show that the Test Case Advisor was used.
3157	Bug	46	When a user deleted a Test Case, the Activity Record description recorded that the Test Case had been updated. This has been corrected.
3159	Feature	46	When existing Test Cases are deleted by the Test Case Advisor, there will be an Activity Record for each deleted Test Case.
3156	Feature	46	The Test Case PDF now includes the email address of the user who ran the Test Case (if the email is different from the username, otherwise only the username will be included).
3103	Bug	46	Changing a Test Case template was sometimes causing too many other Test Case in the Draft to be marked as 'Changed'. This has been corrected.
3139	Feature	46	The Test Case list will display a label with text 'Missing' next to related objects which are not in the Draft.
3140	Feature	46	The Test Case list can be filtered to show Test Cases which have missing related objects.
3141	Feature	46	The Test Set Run settings for Screenshots, Check user roles, Continue on failure, Run concurrently will be remembered and used when creating another Test Set Run.
3136	Feature	46	If there is a Custom Function error in Rave while entering test data, the error will now be displayed in the test step result text.
3138	Feature	46	When creating a Test Set Run you can now choose to capture screenshots for Given, When and Then steps. The default setting is to capture screenshots for When and Then steps.
3129	Bug	45.1	The Test Case Advisor for Derivations could fail if the Derivation if the Derivation steps contained a wildcarded log Field. This has been corrected.
3111	Bug	45.1	When running tests against Rave EDC, the Rave header could display the wrong Site if subjects were created at different sites. This has been corrected.
3130	Bug	45.1	The Test Case editor was sometimes generating 'additional scenarios' which were not compatible with the original check steps. This has been corrected.
3131	Bug	45.1	The Test Case editor was displaying a warning message if the expected query message was only different from an Edit Check query message with leading or trailing whitespace. This has been corrected.
3097	Feature	45	The Test Case run view will display any validation warnings for each step in the Test Case.
3098	Feature	45	The Test Case run view will display any related objects for the Test Case.
3099	Feature	45	The Custom Function editor will display a summary description of the source code in the tab named 'Summary'.
3101	Feature	45	Clicking on the icon next to an object reference in the Test Case editor will now open that object in a modal window.
3079	Feature	45	The Test Case editor will display a warning if the value to be entered does not match the Field data format.
1296	Feature	45	The Test Case editor will not display a warning if the only difference between the expected query text and the text of the Edit Check action is leading or trailing whitespace.
3094	Feature	45	The Test Case editor will not display a warning if expected query text is in a string in the C# code for a referenced Custom Function.
2937	Feature	45	The Test Case editor will display a warning if a Specify value is for a Data Dictionary entry which is not a Specify entry, or if a Specify Data Dictionary entry does not have a Specify value.
3008	Feature	45	The Test Case editor will display a warning if an Edit Check has a Check Action which does not have a 'matching' check step. Previously a comment was added was added to the background steps; the comment is not now added.
3010	Feature	45	The Test Case editor will display a warning if a Custom Function referenced by the Test Case contains a string matching a draft Field OID, and that Field does not exist, or is inactive, in the draft.
3050	Feature	45	The Test Case editor will display a warning if a value is specified for a data or unit dictionary Field, and the value does not exist in the dictionary. Previously this would have been an error, and the Test Case would be invalid and could not be run. Now a warning is displayed and the Test Case can be run.
3073	Feature	45	The Test Case editor will display a warning if a step will try to enter data into a derived Field.
3092	Feature	45	The Test Case editor now displays counts of errors and warnings.
3096	Feature	45	The Test Case editor will display a warning if a referenced Edit Check, Form or Derivation is inactive.
3082	Feature	45	When a Test Case imports or includes a Test Case Template, and when a Test Case uses 'if' statements or 'for' loops, any errors and warnings will now be displayed next to the appropriate line in the Test Case editor.
3087	Bug	45	When running Test Cases, Rave will sometimes log out the user account. TrialGrid tries to log in again and continue testing. The log in attempts were not being successful with Rave Classic. This has been corrected.
3085	Bug	45	The wrong screenshot was sometimes being captured in Test Case results. This has been corrected.
3106	Bug	44.2	The Test Case Advisor would fail for an Edit Check which includes a dictionary Field and a time Field with a 'timespan' check step with a static time value. For example: D1.FORM.FIELD1.CodedValue != "1" and timespan(D1.FORM.FIELD2 , t"10:00") < 60 This has been corrected.
3107	Bug	44.2	The Test Case Advisor could fail if the format specified in a check step did not match the static value specified in the step. The Test Case Advisor will now report an error explaining the problem.
3108	Bug	44.2	The Test Case Advisor was not generating results correctly for Fields with a format including 'HH+' or 'hh+'. This has been corrected.
3071	Feature	44	Versions 7,8,9,10,11 of the TG_UAT draft used to run Automated Tests have been retired.
3087	Bug	43.2	When running Test Cases, Rave will sometimes log out the user account. TrialGrid tries to log in again and continue testing. The log in attempts were not being successful with Rave Classic. This has been corrected.
3085	Bug	43.2	The wrong screenshot was sometimes being captured in Test Case results. This has been corrected.
3088	Bug	43.2	The 'I should see {datapoint} has value {value}' Test Case step was failing for checkbox fields which were not checked (i.e. value '0'). This has been corrected.
3054	Bug	43.1	When running multiple Test Cases with 'run concurrently' turned off, a 'failed' message would appear, and updates to the test case runs would stop. This has been corrected.
3059	Bug	43.1	The Test Case Advisor was not suggesting good scenarios if a partial date, with a format like 'MMM yyyy' was being compared against a full date, with a format like 'dd MMM yyyy'. The Test Case Advisor should now generate sensible suggestions for the date values and scenarios.
3060	Bug	43.1	The Test Case Advisor was sometimes suggesting values with different record positions when a field with a default value was used in an Edit Check. This has been corrected.
2938	Bug	43	After clicking the 'auto-indent' button in the Test Case editor, the object markers in the margin were being lost. This has been corrected.
3043	Feature	43	Because of a bug in Rave Web Services, data can not be entered into Forms and Fields which are entry restricted to a role (for example 'Clinical Research Coordinator - Blinded') which starts with the same text as the role being used for testing (for example, 'Clinical Research Coordinator'). If TrialGrid detects this problem it will now attempt to enter the data using a custom function in the TG_UAT draft, and the data entry step should pass. TrialGrid will not attempt to use Rave Web Services, it will immediately try to enter data using a custom function. This feature requires version 13 of the TG_UAT draft. Please contact support@trialgrid.com to request TG_UAT draft version 13.
3044	Feature	43	There is a new configuration setting to limit the rate of requests to run custom functions in the TG_UAT draft when running many Test Cases at the same time against a Rave URL. This setting can be configured by TrialGrid Ltd on request.
3014	Bug	43	When generating additional log records, the Test Case Advisor was setting standard, non-log, fields to have record position 2. This has been corrected.
3015	Feature	43	When generating additional log records, the Test Case Advisor now creates separate scenarios for record position 2 so that edit checks with log and standard fields will be thoroughly tested.
3019	Bug	43	The markers for related objects after the first line were being removed when the Test Case content was changed. This has been corrected.
3020	Bug	43	Horizontal scroll bars were not always being displayed in the Test Case editor and data views. This has been corrected.
3025	Feature	43	The Test Case Advisor 'create additional scenarios' option will create three scenarios for IsLessThan, IsLessThanOrEqualTo, IsEqualTo, IsGreaterThan, IsGreaterThanOrEqualTo steps. One value will be immediately below the comparison, one equal and one greater than.
3026	Feature	43	The Test Case Advisor 'create additional scenarios' option will create, if possible, a positive and negative scenario for each AND and OR step.
3027	Feature	43	The Test Case Advisor 'create additional scenarios' option will create, if possible, a positive and negative scenario for each IsEmpty/IsNotEmpty step.
3041	Feature	43	The size of Test Case screenshot files has been reduced by reducing the color depth of the images. This will also reduce the size of PDF files containing screenshots. The size reduction will only apply to screenshots captured after this feature has been released. Existing screenshots will not be modified. The reduction in size is expected to be about 75%.
3034	Feature	43	A new view is available by clicking on 'Test Case Runs' on the user home page. This view displays all Test Case Runs which are pending or running, for all URLs and Projects in your Organization. You can choose to view finished Test Case Runs for various time periods.
2977	Feature	43	Additional information has been added to the Test Case run log to assist TrialGrid Ltd when investigating issues. This information is only visible to TrialGrid Ltd users.
2985	Feature	43	The TrialGrid URL name is now included in the Test Case pdf.
2986	Feature	43	Debug log messages are not now included in the Test Case pdf.
2989	Feature	43	Screenshots in Test Case run results will now be displayed in a 'collapsed' view, to help review the overall results.
2990	Feature	43	Clicking on a screenshot in Test Case run results will expand it to full size, clicking again will collapse it.
2991	Feature	43	Test Case run result screenshots containing a highlighted area, for example, a query message, will be scrolled to display the highlighted area.
2993	Feature	43	All screenshots on a Test Case result page can be hidden, collapsed or viewed in full size display.
2994	Bug	43	In rare cases it was possible to create a draft where Test Set Runs could not be created due to database errors. This was corrected.
3006	Bug	42.2	Test Cases using the 'see form ... with name' step with a child folder, not specified with an absolute path, could not be saved in the Test Case editor. This has been corrected.
3007	Bug	42.2	There was an error entering data in a Test Case step referring to more than 1 form, if one of the forms was view restricted to a role starting with the same text as the role being used for data entry (see issue 2965 below). This has been corrected.
2998	Bug	42.1	Test Case screenshots were being truncated when displayed in the test case results. This has been corrected.
2987	Bug	42	If Test Case results contained a screenshot of a log form with a large number of fields, this could cause other screenshots to be displayed incorrectly. This has been fixed.
2983	Bug	42	If a Rave Classic landscape form had the same query opened on multiple records, then the query text was not being highlighted. This has been corrected.
2954	Feature	42	The Test Case Advisor has a new option 'Create additional log records'. If an Edit Check has wildcarded log fields, the Test Case Advisor will create test steps for record position 1 and record position 2.
2957	Feature	42	The data entry helper in the Test Case editor was limited to 200 rows. This limit has been removed and there is no restriction on the number of rows.
2959	Feature	42	The Test Case Advisor now has a template which specifies the structure and content of the Test Cases. The template can be modified by TrialGrid Ltd. Contact support@trialgrid.com if you would like to do this.
2944	Feature	42	The Test Case editor will automatically format the Test Case when it is saved. Automatic formatting can be disabled by un-checking 'Format on save'.
2877	Feature	42	The Test Case Advisor is now available from the Edit Check editor sidebar, replacing the Add and Replace buttons.
2960	Feature	42	The Test Case Advisor results now contain hyperlinks to the created Test Cases, so that a Test Case can be opened directly by clicking on the link in the results.
2939	Bug	42	The Edit Check list was not being updated correctly after closing the Test Case Advisor. This has been corrected.
2940	Feature	42	When looking for a Folder for a wildcarded step in an Edit Check, the Test Case Advisor will look in Matrices before looking for an AddForm Check Action matching the Form in the Check Step.
2200	Feature	42	The Test Case Advisor has been changed so that Labels can be applied to newly created Test Cases, without having to choose Labels for suggested, review recommended and invalid Test Cases.
2948	Bug	42	If a Test Case was deleted after it had been included in a Test Set Run, then the Test Case Run would not be marked as passed/failed on completion. This has been corrected.
2950	Feature	42	A default worker queue can be assigned for an Organization.
2965	Bug	41.2	Because of a bug in Rave Web Services, data could not be entered into Forms and Fields which are entry restricted to a role (for example 'Clinical Research Coordinator - Blinded') which starts with the same text as the role being used for testing (for example, 'Clinical Research Coordinator'). If TrialGrid detects this problem it will now attempt to enter the data using a custom function in the TG_UAT draft, and the data entry step should pass. This feature requires version 13 of the TG_UAT draft.
2973	Bug	41.2	The 'draft.has_form_field' method in Test Cases was not always checking if the Form and Field were active. This has been corrected.
2947	Bug	41.1	Folders with repeating Parent Folders inside Grand-parent Folders were not being matched correctly during Test Case runs. This has been corrected.
2930	Bug	41	When running Test Cases against Rave EDC URLs, Rave EDC will sometimes spontaneously log out the user account. TrialGrid will now log back into Rave EDC if this happens.
2925	Bug	41	If a Field had Pretext containing a single quote character, this would be rendered in the Test Case pdf, if objects names selected, as an escaped HTML sequence, &#x27;s. This has been corrected.
2915	Bug	41	Test Case and Test Data generation would fail if a Field has a numeric format and has a Data Dictionary and has a default value. This has been corrected.
2916	Bug	41	Test Case and Test Data generation would fail if a Field has a numeric format and has a Data Dictionary which contains coded data entries which are not numeric. This has been corrected.
2919	Feature	40.3	When running Test Cases against Rave EDC URLs, the role name in the Rave Core Configuration can be different from the Cloud Admin Role name. TrialGrid will now display a warning if the EDC Role is not found, and will select an available role for that user account.
2914	Bug	40.2	The Test Case editor was not displaying warning messages for log record steps which could cause the Save button to be disabled because of a javascript error. This has been corrected.
2903	Bug	40.1	Landscape Forms with many default values were not being opened for screenshots when testing Rave Classic. This has been corrected.
2904	Bug	40.1	The 'I should see record ... is active' and 'I should see record ... is inactive' steps could not be used with standard records. This has been corrected.
2900	Bug	40	When running multiple Test Cases at the same time against Rave EDC, some calls to Rave custom functions could fail. This has been corrected.
2889	Bug	40	If a Derivation is inactive, it will not be included in the Test Case generated for an Edit Check which references the Field which is the target of the Derivation.
2895	Bug	40	Test Case results were incorrectly reporting fields as being entry restricted. This has been corrected.
2878	Feature	40	The Test Case results will report if the same query is open more than once on a datapoint. The step will still pass.
2893	Bug	40	Test Cases would not run when testing Rave EDC studies if the Site Number was different from the Study Site Number. This has been corrected. The Site Number should be entered and TrialGrid will look up the Study Site Number and use that to navigate in Rave EDC.
2892	Bug	40	The Test Case Advisor would fail for Edit Checks referencing an integer Field using StandardValue and UserValue. This has been corrected.
2744	Bug	40	In a Test Case with an included Template, the helper icons would not always be positioned on the correct line. This has been corrected.
2881	Feature	40	A new Test Case step will check if a Form exists in the specified Folder in the Rave subject and if it does not, then TrialGrid will ignore it and will not attempt to enter data into that Form. See Automated Testing Step Reference
2864	Feature	40	The Test Case Excel report now includes the email of the user who created the Test Case, when it was created, and the email of the user who last updated it and when.
2870	Feature	40	Invalid Test Cases will not be included in Test Case PDFs or Test Case Excel reports.
2871	Feature	40	The number of scenarios in each Test Case is displayed in the Test Case list
2872	Bug	40	Test Case results were not including screenshots for all forms if the form was inside a nested folder (a folder with a parent folder) and there were multiple instances of the parent folder. Test Case results were not being verified correctly for Forms inside nested folders. These issues have been corrected.
2873	Feature	40	The Test Case editor will display an error, and the Test Case will be invalid, if there is no login step in the Test Case.
2874	Feature	40	The Test Case editor will display an error, and the Test Case will be invalid, if there is no create or select subject step in the Test Case.
2875	Feature	40	The Test Case editor will display an error, and the Test Case will be invalid, if the Background line has been accidentally deleted.
2876	Feature	40	The Test Case editor now displays a count of the number of scenarios, and a count of the number of test steps.
2878	Feature	40	The Test Case results will report if the same query is open more than once on a datapoint. The step will still pass.
2860	Feature	40	A new 'healthcheck' has been added to alert TrialGrid Ltd if any Test Case runs have stalled.
2861	Feature	40	Stalled Test Case runs will be automatically set to a state of Failed by TrialGrid.
2839	Feature	40	When saving a Test Case Template, TrialGrid will check all Test Cases in the Draft to see if they import or include that Template, and will update them if so.
2841	Feature	40	Before deleting a Test Case Template, a confirmation message will be displayed asking the user to confirm that the Test Case Template should be deleted.
2849	Feature	40	When deleting a Test Case Template, TrialGrid will check all Test Cases in the Draft to see if they import or include that Template, and will update them if so.
2842	Feature	40	When a new Test Case Template is created, TrialGrid will check all Test Cases in the Draft to see if they import or include that Template, and will update them if so.
2843	Feature	40	The Test Case 'Is Template' property is now included in Draft exports and imports.
2844	Feature	40	When copying Test Cases into a Draft, Test Case Templates will be copied first.
2845	Feature	40	Test Case Templates cannot include or import another Template.
2850	Feature	40	When saving a Test Case Template, there will not be an error message if the Template has no Scenarios.
2851	Feature	40	When editing a Test Case Template, the View, Data and Run History tabs will not be displayed.
2828	Bug	40	The "I add folder" test steps were creating additional parent folders when adding child folders to parent folders. This has been corrected. A new version of the TG_UAT draft, version 12, is required.
2829	Feature	40	The Test Case editor will display a warning for steps which reference nested folders or parent/child folders and which do not use an absolute folder reference.
2830	Feature	40	The Test Case editor will display a warning if the 'folder exists' step is used with parent/child folders. An 'add folder' step should be used.
2835	Feature	40	The Test Case Advisor will now insert the Parent Folder OID for any Folders which have a Parent Folder.
2835	Feature	40	The Test Case Advisor will now insert the Parent Folder OID for any Folders which have a Parent.
2836	Feature	40	The Test Case Advisor will now create 'I add folder' steps for Folders which have a Parent.
2824	Bug	39	Saving a Test Case Template which is used in many Test Cases was taking longer than 30 seconds, and timing out. Performance has been improved and saving should not now timeout.
2801	Bug	39	Test Case editor helpers were not using 0 as the default for Form Ordinal. This has been corrected.
2793	Bug	39	Test Data steps to verify the value of a Field were sometimes passing incorrectly, when the Form was not present in the specified Folder. This has been corrected.
2781	Bug	39	For some Edit Checks which reference a Field by both Standard and Coded Value the Test Case Advisor was generating multiple values for the Field. This has been corrected.
2783	Feature	39	The Test Case Advisor will now to try create additional scenarios using empty values for Fields used in an IsEmpty or IsNotEmpty step.
2795	Bug	38	Saving a Test Case Template which is used in many Test Cases was taking longer than 30 seconds, and timing out. Performance has been improved and saving should not now timeout.
2661	Feature	37	If a completed test step does not capture a screenshot, a message will be displayed in the test results to make it clear that no screenshot has been taken. If a test step is pending or running, no message will be displayed.
2741	Feature	37	A message will be displayed in the step results for the 'enter and save data on active fields' step if a field is being ignored because it is inactive or does not exist in the Draft.
2661	Feature	37	If a test step does not capture a screenshot, a message will be displayed in the test results to make it clear that no screenshot has been taken.
1317	Feature	37	It is now possible to cancel the Test Case Advisor before it has finished generating Test Cases.
2643	Feature	37	It is now possible to cancel Test Case PDF generation before it has finished generating PDFs.
2725	Feature	37	A maximum size for combined Test Case PDFs can be set. If the size of the individual Test Case PDFs is greater than the limit, then multiple PDFs will be created in a zip archive. Contact support@trialgrid.com if you would like this to be configured for you.
2714	Feature	36	The Test Case Data view will not display an error message if the 'enter and save data on active fields' step is used and a Field in that step is not present in the Draft. The 'enter and save data on active fields' step ignores Fields which are inactive, and Fields which do not exist in the Draft and so an error message is not necessary when viewing the Data view.
2611	Feature	35	TrialGrid has limited support for running tests against Rave EDC using iMedidata accounts which have two factor authentication. TrialGrid Ltd will add full support for two-factor enabled iMedidata accounts in a future TrialGrid release. As a temporary workaround, to run Test Cases using two-factor enabled iMedidata accounts you must first log in via the Draft Import or Export wizard (you do not need to import or export a draft). For an example, see iMedidata Two Factor Authentication.
2682	Feature	35	The Test Case run log now contains the TrialGrid version number.
2610	Feature	35	The Test Case run log now contains the TG_UAT version number.
2626	Feature	35	The Test Case Advisor now only shows EDC Roles which are active.
2702	Bug	35	When copying a Test Case containing template commands the template was not being updated correctly after copying. This has been corrected.
2648	Feature	34	Importing or exporting a Draft to Medidata Rave via iMedidata now supports two factor authentication using the Okta system recommended by Medidata.
2646	Bug	34	Test Cases were not saving when using Internet Explorer. This has been fixed.
2646	Bug	34	Test Cases were not saving when using Internet Explorer. This has been fixed.
2521	Feature	34	The Test Case results will display a message if a Rave EDC user does not have permission to save a form in Rave EDC.
2537	Feature	34	The Test Case Advisor has a new option to create test scenarios using the Rave unknown date formats, UN, UNK, UNKN for days, months and years.
2620	Feature	34	The Test Case Advisor has a new option to create additional test scenarios such that each Field is tested with at least 2 different values.
2634	Feature	34	The Test Case Advisor will attempt to use the same value (0 for unchecked, 1 for checked) for all checkbox Fields if there are multiple checkbox Fields in an Edit Check.
2605	Feature	34	A default for the data entry step used by the Test Case Advisor can be set for each URL in TrialGrid. Contact support@trialgrid.com if you would like this to be configured for you.
2590	Feature	34	The Test Case Advisor will now create separate steps to select values from Dynamic Search List fields.
2607	Feature	34	The Test Case Advisor will now add references to Dynamic Search List custom functions
2608	Feature	34	A default for the content of new Test Cases can be set for each URL in TrialGrid.
2609	Feature	34	It is now possible to import or include the content of one Test Case inside another Test Case.
2615	Feature	34	There is a new 'Data' view for a Test Case which displays the data entered in each test scenario in a table. The table is read-only.
2616	Feature	34	The Test Case view will remember which tab was selected and display that tab the next time a Test Case is opened.
2583	Bug	34	Test Case runs against Rave EDC are sometimes failing with an error 'Folder not found' or 'Form not found'. Additional logging and error handling has been added.
2591	Feature	34	When text cannot be highlighted in a Test Case screenshot a message is added to the Test Case log. This message now has a level of 'info'.
2592	Feature	34	If TrialGrid receives a '500 Internal Server Error' from Rave when entering Test Case data, a message will be added to the results to explain that this might be caused by a Custom Function error.
2541	Bug	34	Long Draft names were overflowing the table border in the Test Case pdf report. This has been corrected.
2554	Bug	34	TrialGrid would sometimes incorrectly check Queries when running Test Cases. This has been corrected.
2521	Feature	34	The Test Case results will display a message if a Rave EDC user does not have permission to execute the test step, for example if their Rave EDC Role does not have data entry permission.
2524	Feature	34	The Test Case results will display a message if a subject is required for a test step and one has not been created or selected in the previous steps.
2542	Bug	34	Test Cases without screenshots were not running against Rave EDC. This has been corrected.
2552	Feature	34	Test Case results will now include a message if non-ascii characters are present in expected or actual query text.
2518	Bug	32	Test Cases were failing when run against Rave EDC 2021.1.4. This has been corrected.
2502	Bug	32	Copying Test Cases with a 'See Query' step referencing a Field which does not exist in the target Draft would fail. This has been corrected.
2501	Bug	32	Test Case PDFs could not be generated for Test Cases with a forward slash character '/' in the Test Case name. This has been corrected.
1442	Feature	31	New Test Steps are available to assign a Lab to a Form and to check that Lab Ranges are correct. A new version of the TG_UAT draft (version 10) is required to check Lab Ranges.
2461	Feature	31	Test Cases in a Test Set Run will now be run concurrently, with a default concurrency of 2 running at the same time. Separate test set run workers can be configured for each Rave URL, with a configurable concurrency limit - please contact TrialGrid support if you would like a separate worker configured.
2468	Feature	31	The 'Enter and save data on active fields' test step will now ignore Fields which do not exist in the Draft as well as ignoring inactive Fields.
2463	Feature	31	The Test Case list can now be filtered by status of Not Run (includes Created, Pending and Cancelled), Running, Failed and Passed.
2466	Bug	31	Query text was not being highlighted for queries on Lab Fields in Rave Classic. This has been corrected.
2460	Bug	31	When running Test Cases containing multiple EDC Roles against Rave EDC URLs then some Test Cases would fail, depending on the order in which they were run. This has been corrected.
2450	Bug	31	When a running Test Case was cancelled the Chrome browser on the TrialGrid server was not being closed. This has been corrected.
2262	Feature	30	Test Case PDFs can now display Folder/Form/Field OIDs or names in the test results.
2436	Feature	30	Test Case PDFs can now display all screenshots, or screenshots for Given, When or Then steps, as selected when generating the PDF. Note: selecting Given, When or Then screenshots will only work for Test Cases run AFTER the date of this release.
2438	Feature	30	There is a new Test Case step 'When I enter and save data on active fields' which will ignore any inactive Fields, or Fields on inactive Forms, in the data table.
2415	Feature	30	Versions 4,5,6 of the TG_UAT draft used to run Automated Tests have been retired.
2416	Bug	30	The Test Case Generator was including inactive Forms for AddMatrix and MergeMatrix Check Actions. Inactive Forms are now excluded from the suggested Test Case.
2385	Bug	28	Automated Tests would not run on older versions of Classic Rave URLs. This has been corrected.
2381	Bug	27	Test Cases can now be generated for Edit Checks which include Derivations containing date or time Fields.
2382	Feature	27	Test Cases can now be generated for Derivations which construct dates and/or times using strings.
2363	Bug	27	A comment in a test case which appeared after a table of data was moved above the table of data when autoformat was selected. This was corrected.
2358	Feature	27	There is a new Test Case Step to check multi-line Field values.
2351	Bug	27	When copying a Test Case into a Draft, labels were duplicated in the list. This has been corrected
2354	Bug	27	The Test Case Advisor was not suggesting the correct Subject Status for Edit Checks with a SetSubjectStatus Check Action which was not 'FromDataValue'. This has been corrected.
2344	Feature	27	The Test Case PDF report now lists Test Cases in alphanumeric order.
2345	Feature	27	When scrolling the content in the Test Case editor, the editor toolbar will remain visible.
2350	Feature	27	The Test Case list PDF export now has a title of 'Test Case Status'.
2349	Bug	27	The screenshot for Subject Status steps did not show the subject's status. This has been corrected for Rave Classic (the Primary Form is used) and Rave EDC (the sidebar is used).
1965	Feature	26	Test Case PDFs can now include the Log of Test Case runs.
2019	Feature	26	Test Case PDFs can now include only screenshots and no other content.
2162	Feature	26	Test Case Archives can be generated for Test Cases with or without run results.
1812	Feature	26	Test Cases can now be generated for Derivations from the Derivation editor sidebar. Note: there is no 'Test Case Advisor' to generate Test Cases for multiple Derivations at the same time.
2289	Feature	26	Test data uploads now create separate steps to enter data into Dynamic Search List fields.
2007	Feature	26	Test Cases with no scenarios are now marked as Invalid and cannot be run.
1950	Bug	26	If a Test Case run finds a Rave subject which is not on the latest CRF Version then it will log a warning and will use that subject.
1994	Feature	26	The highlighting of query messages in Test Case result screenshots was improved.
2257	Feature	26	Multiple lines can be commented/uncommented in the Test Case editor using a new 'Comment' button.
2315	Feature	26	When viewing a Test Case run, screenshots can be displayed or hidden.
2316	Feature	26	When viewing a Test Case run, there is a list of scenarios on the left hand side which can be used to navigate between scenarios.
2317	Feature	26	When viewing a Test Case run, debug messages in the log will be visible to super-users.
2318	Feature	26	When viewing a Test Case run, the run can be cancelled directly from that page.
2299	Bug	26	A system error was being logged when copying test cases from Drafts with long names. This error was not user visible.
2306	Bug	26	Test Case Runs would fail if a query message contained a Tab character. Test Case Runs will not now fail and the Tab character will be replaced by a space when comparing the query message against expected results. Tab characters are normally not enterable in Rave. TrialGrid also replaces them when uploading Architect Loader Spreadsheets.
2294	Bug	25	The Import button on the Test Case list was not enabled if the user role had Manage Tests permission. This has been corrected.
2295	Bug	25	The Derivation list would not display if Test Cases were related to Derivations. This has been corrected.
2275	Bug	24	Test Data Upload files should have Folder and Form repeat numbers starting with 0. Previously they started at 1, but this was inconsistent with Test Cases.
2274	Bug	24	Applying and removing Labels on the Test Case list, and other Draft object lists, requires the Label permission and does not now require Edit Objects or Manage Test Case permission.
2260	Feature	23	The default Test Case name format can be customised by TrialGrid on request.
2246	Feature	23	An additional column has been added to the TG_UAT_TestCases worksheet in downloaded Architect Loader Spreadsheets which will contain a warning if the Test Case is longer than the Excel cell character or line break limit. The warning explains that if the worksheet is saved in Excel then the Test Case will be truncated.
2252	Bug	23	The Test Set Run view would sometimes display start/finish times in different time zones (UTC and the user's local timezone). It now displays a start and finish times as 'from now' in the user's timezone.
2251	Feature	23	In test cases formatting the test case formatter now removes empty lines in tables.
2250	Bug	23	When Exporting Test Cases to ALS and then re-importing test cases lines become double spaced. This was corrected.
2190	Bug	22	Users should be able to create and edit Test Cases if their Project Role has Manage Tests permission. Edit Objects permission should not be required
2186	Feature	22	The performance of the Test Case editor has been improved, particularly for large Test cases.
2187	Feature	22	The Test Case Run view is now split into 3 tabs, Summary, Results and Logs. The Results page will 'lazily' load screenshots, i.e. screenshots will be loaded and displayed only if you scroll to that section of the page.
2169	Bug	21	Test Case PDFs could not be generated if the pdf was greater than 2Gb in size. This limit has been removed.
2161	Bug	21	The Test Case generator would fail if an Edit Check contained a variable only Check Step and a variable only Check Action, if the Step and Action variables were different but associated with Fields on the same Form. This has been corrected.
1942	Feature	21	The Edit Check list page can now be filtered to show Edit Checks which do or do not have Test Cases.
2127	Bug	21	Labels in the Label filter list on the Test Case list page were not displaying correctly. This has been fixed.
2152	Feature	21	If the TrialGrid servers are re-started while a Test Case run is in progress then the Test Case run will resume running automatically after the re-start.
2146	Bug	21	Test Cases steps to add a log record with record position greater than one would not reliably trigger Custom Functions because of an issue with Rave Web Services. TrialGrid now detects this situation and takes measures to workaround the RWS issue so that Custom Functions will run as expected.
2147	Bug	21	The Test Case Advisor would fail when processing an Edit Check with a variable only Check Step referencing a date Field. This has been corrected.
1796	Feature	21	Test Cases are now included in Draft Comparisons.
2145	Bug	21	The 'enter and save data' Test Step now has additional code to ensure accuracy of results.
2095	Bug	21	The correct Default EDC Role for the Test Case Advisor was not being displayed on the Edit Project page. This has been corrected.
2104	Bug	21	Test Case Archives were failing to generate. This has been corrected.
2108	Feature	21	The View display in the Test Case Editor is now on a separate tab.
2029	Feature	21	New Test Case steps can be used to add folders and forms to the subject and within existing folder instances. See: Given I add folder "{folder_oid}" to the subject Given I add folder "{folder_oid}" to folder "{folder}" given_i_add_form_form_oid_to_the_subject given_i_add_form_form_oid_to_folder_folder
2065	Feature	21	Test Cases now support 'grand-parent' folder structures. See Folder, Form and DataPoint References
2066	Feature	21	Test Case steps can reference folders using an 'absolute' path. See Folder, Form and DataPoint References
1161	Feature	19	When running Test Cases against Rave EDC a new step can be used to switch between EDC Roles when taking screenshots.
2052	Bug	19	TrialGrid will now take multiple screenshots for long subject calendars which span multiple pages (Rave Classic) or one long screenshot with all folders (Rave EDC).
2058	Bug	19	The wrong screenshot was taken for Folders when running tests against Rave EDC. This has been corrected.
2050	Bug	19	The Test Case pdf would sometimes not include screenshots for Test Cases with more than one Test Set run. This has been corrected.
1934	Feature	19	Rave credentials for running Automated Tests can be managed by TrialGrid on request. Users will not enter Rave user credentials when running Test Cases.
2036	Feature	19	If no iMedidata URL is entered in the Project configuration then Test Cases for Rave EDC will default to the production iMedidata site.
2037	Bug	19	Test Cases for Rave EDC will now work if the iMedidata user account has access to more than one site in the study.
1310	Feature	19	A new feature to generate Test Cases for Forms and Matrices has been added. A Test Case can be create for a single Form from the sidebar in the Form Editor. Test Cases can be created for one or more Forms by selecting Forms in the Form list and clicking the "Test Data Advisor" button. Test Cases can be created for all Folder/Forms in a Matrix (or several Matrices if multi-select is enabled) by clicking the "Test Data Advisor" button.
2035	Bug	19	Numeric Fields with a non-numeric Default Value would cause Test Case generation to fail. This has been fixed and non-numeric Default Values will be ignored for numeric Fields.
2023	Bug	19	The performance of the Test Case editor has been improved, particularly for large test cases.
1956	Bug	19	Query messages were not verified correctly by TrialGrid Test Case if the message used Rave 'gxml' tags. This has been corrected. Note that use of gxml in Comments and Stickies is not currently supported by Test Cases.
1962	Feature	19	Test Case results will display more information if a datapoint cannot be found or entered, e.g. if a Field exists in the TrialGrid draft but does not exist in the Rave version.
1977	Feature	19	TrialGrid will detect whether a Rave URL is Rave Classic or Rave EDC (RaveX). It is no longer necessary to configure Rave EDC links.
1978	Feature	19	Rave credentials are cached between Test Set Runs and do not need to be re-entered.
1979	Feature	19	The Test Set run dialog displays information about the type of account required.
1980	Feature	19	A warning will be displayed when entering Rave credentials if a Rave production environment has been entered.
1986	Feature	19	A new test step has been added to activate Log Records which are inactive.
1993	Bug	19	A new test step has been added to enter data into Dynamic Search List fields.
2009	Feature	19	If the Rave error page is displayed during a Test Case run (for example when trying to view a CRF Page which is view restricted) then a screenshot of the error page and the error detail will be captured.
2011	Feature	19	A new test step has been added to perform a Medidata Rave Add Event action.
2018	Feature	19	New test steps have been added to check whether Log Records are active or inactive.
2003	Bug	19	Automated Testing Test Case Run Archive files were not stored with unique names so that Archives could be overwritten and would need to be regenerated. This was corrected.
2002	Bug	19	In the Data Manager and Programmer view of the Test Case PDF, Enter Data steps in scenario backgrounds were not properly formatted. This was corrected.
2001	Bug	19	Users would get system timeout errors when trying to download Testing Archives (zip files of Test Case PDF results) if the download did not complete in 30 seconds. This was corrected.
1991	Bug	19	Edit Checks containing the same Field in a Check Step and a SetDataPointVisible Check Action could cause an infinite loop error when generating Test Cases. This has been corrected.
1992	Bug	19	Rave allows strings and integer values to be concatenated using the StringAdd Check or Derivation Step. TrialGrid Test Case generation now supports this.
1982	Bug	19	For each step of a Test Case screenshots are taken. A test case can contain background steps which are run for each Scenario. Screenshots from later scenario background steps were overwriting the screenshots of earlier Scenarios. This was corrected. Overwritten screenshot records will be removed from Test Case Run results and will no longer appear in PDF results or the Test Case result web-pages. New Test Case runs maintain all screenshots correctly.
1935	Feature	19	Test case traceability in validation documentation was improved.
1975	Bug	19	On the Test Set execution and UAT Archive page the "Test Cases" breadcrumb was missing. This was corrected.
1981	Feature	19	A run history page was added to the Test Case editor. This makes it easier to track which Test Sets included the Test Case.
1966	Feature	19	When running Test Cases if the Rave URL entered is not a valid URL then an error message will be displayed.
1967	Feature	19	When running Test Cases if the Rave URL is entered with 'http' it will be automatically upgraded to 'https'.
1968	Feature	19	When running Test Cases the Rave URL can be entered without the protocol and domain. For example entering 'innovate' will automatically run tests against 'https://innovate.mdsol.com'.
1955	Bug	18	The Test Case PDF was not including the latest run results if a Test Case was included in a later Test Set which had not been run. This has been corrected.
1943	Bug	18	If an error occurred while saving Rave data during a Test Case run then a potentially misleading message 'Could not be find <field>' was displayed. This has been changed so that 'Could not find <field>' will be displayed if the Rave form could not be located and otherwise 'An error occurred while save <field>' will be displayed.
1922	Bug	17	Test Case generation would fail if an Edit Check referenced a Field with a numeric format and a numeric Default Value. This has been corrected.
1925	Bug	17	Test Cases running against Rave EDC (RaveX) would sometimes fail because the test session was logged out to the iMedidata login page. Automated tests will now attempt to login again if this happens and should recover from this situation.
1923	Bug	17	If an invalid test case is queued to be run the resulting test case run page cannot be viewed because of a system error. This was corrected. It should not be possible to queue invalid test cases to be run.
1904	Bug	17	When importing a Draft from the filesystem, import messages were not displayed until the import was completed. This was corrected.
1921	Bug	17	Errors were occurring when viewing test case runs. This has been corrected.
1416	Feature	17	The Test Case PDF list now has selection options to control what content is included in the PDF output.
1914	Feature	17	Test Case runs do not now automatically create a PDF document of the test run results. A PDF of one or more Test Case runs can be generated using the Test Case PDF option on the Test Case List page.
1916	Feature	17	The Test Case editor will now display an error if a table is inserted after a step which should not have a table.
1875	Bug	17	The Test Set Run view would time-out if it contained a large number of Test Cases to run, this was corrected. In addition, the performance of the display was improved.
1873	Bug	17	When there were a large number of Test Case Runs in a a Test Set run, it was not possible to refresh the page and see the current status of the run. This was corrected.
1896	Bug	17	When running Test Cases for Rave EDC (RaveX) timeouts and other settings have been configured to reduce the number of errors when accessing Rave EDC.
1893	Bug	17	Test Case runs would fail if the Site Number or Subject Name contained a 'smart quote' character. This has been corrected.
1871	Bug	17	Test Case results were reported incorrectly when checking if queries had been closed if there were other open queries on the same datapoint. This has been corrected.
1886	Feature	17	A small improvement to the performance of running multiple test cases was made.
1883	Bug	17	Test Case runs were not converting the Unit String into Coded Units for Unit Dictionary Fields. This has been corrected.
1813	Feature	16	Documentation about creating Test Cases for Derivations has been added. See Testing Derivations.
1162	Feature	16	Configuration settings for Automated Testing can now be set for each Project. See Project Test Configuration.
1863	Bug	16	The Test Data Upload was not processing rows for Fields with Unit Dictionaries if no unit was specified. This has been corrected.
1859	Bug	16	Uploading a test data file with multiple unit dictionaries would fail. This has been corrected.
1860	Feature	16	When uploading a test data file an upload name can be entered and this will be included in the names of the created Test Cases.
1849	Bug	16	Data entry would sometimes fail after the 'Create or select subject at site' Test Case step. This has been corrected (continuation of issue fixed on 2020-05-11).
1849	Bug	16	The 'Create or select subject at site' Test Case step would fail if subjects with the same name were present at different study sites. This has been corrected.
1628	Bug	16	Data Dictionary 'other' entries are now supported in Test Cases.
1833	Bug	16	The 'Create or select the subject named {name} at site {site}' Test Case step was creating a subject with the wrong name. This has been corrected.
1831	Bug	16	The status of Test Case runs was sometimes displayed incorrectly. This has been corrected.
1826	Feature	16	Test Case steps have been added to allow creating a named subject at a specified Study Site.
1803	Feature	16	Test Cases can now be created by uploading a file containing test data. See Uploading Test Data
1822	Bug	16	The performance of deleting Test Cases was improved.
1817	Bug	16	The Test Case Advisor would fail for Edit Checks containing a date Field with a Default Value of a single pipe character, "|". This has been corrected.
1553	Bug	16	The performance of the Test Cases list view was improved.
1808	Bug	16	Automated Test results were not being reported correctly when the expected query was different from the actual query. This has been corrected.
1809	Feature	16	When verifying expected data values the Automated Test results will report if the value in Rave has only whitespace differences from the expected value.
1806	Bug	16	Test Cases could not be copied from another URL if the Test Cases were labelled with Labels not existing in the target Draft. This has been corrected.
1790	Feature	16	When checking Test Case results differences in whitespace characters (in query messages for example) will be noted in the results but will not cause the step to fail.
1791	Bug	16	Test Case Generation would fail on Edit Checks containing an 'IsEmpty' step and a step referencing a Log Field with multiple default values with a comparison against a default value on a Log Record after the first one. This has been corrected.
1789	Bug	16	Test Case result screenshots were displaying out-of-date information in some cases when testing against Rave EDC (RaveX). This has been corrected and the page is refreshed before the screenshot is taken to ensure the latest information is visible.
1788	Feature	16	If a Test Case step which requires Rave Subject Admin permission fails then a message will be displayed in the test results asking if the given user account does have Subject Admin permission.
1787	Bug	16	When running Test Cases on a Rave EDC (RaveX) URL scenarios after the first scenario would fail. This has been corrected.
1786	Bug	16	When running Test Cases on a Rave EDC (RaveX) URL the user accounts required will now include Rave EDC roles when required for Test Steps such as 'When I enter and save data'.
1782	Feature	16	Test Cases have new steps to check whether a datapoint is submitted, see Automated Testing Step Reference
1770	Feature	16	Test Case subject names are now truncated on the right.
1771	Feature	16	The default Test Case subject name format is now the first 20 characters of the Test Case name followed by a timestamp.
1772	Feature	16	The default Test Case subject name format now has additional formatting options which can be configured by TrialGrid on request.
1767	Bug	16	The 'randint' subject name parameter can now be formatted. See Test Case Subjects
1765	Bug	16	The performance of running Test Cases has been improved.
1760	Feature	16	The Test Set Run history now has default ordering of most recent runs first.
1717	Feature	16	Labels can now be added or removed from multiple Test Cases using the 'Apply Label' button on the Test Case list page.
1762	Bug	16	Line breaks in query text messages were causing errors in Test Case runs. This has been corrected.
1763	Bug	16	Double quote characters in Form or Folder names were causing errors in Test Case runs. This has been corrected.
1761	Feature	16	New parameters are available to format test subject names in Test Cases. See Test Case Subjects
1758	Bug	16	Test Case results would not highlight query messages containing double-quotes and some other symbols. This has been corrected.
1750	Bug	16	Test Case run screenshots were not capturing the complete page for non-log forms (introduced by changes from #1725). This was corrected.
1751	Feature	16	The TrialGrid Project and Draft have been added to the Test Case run pdf.
1740	Feature	16	When copying Test Cases from another Draft or Library there is now an option to select only those Test Cases for which the related Edit Check(s) exist in the target Draft.
1745	Feature	16	When running the 'subject exists' step in Automated Tests TrialGrid will attempt to create a subject using the EDC Role specified in the Test Case. If this Role does not have permission to create subjects in Medidata Rave then TrialGrid will attempt to create the subject using the "Subject Admin" user, if available.
1734	Bug	16	A failure to generate the pdf for a particular Test Case run was corrected.
1744	Feature	16	Test Case Templates can now use control structures such as 'for' loops. See Test Case Templates
1739	Feature	16	Test Case Templates can now use optional Folders. See Test Case Templates
1439	Feature	16	Incomplete date and time values can now be specified in Test Cases. See Dates and Times in Test Cases
1732	Feature	16	The 'Then I should see form' Test Case step will now include a screenshot of the form in the test results.
1737	Feature	16	Test Cases will now run if the Rave user account uses a non-English locale such as Japanese. Japanese, Chinese and Korean fonts should display correctly in result screenshots.
1727	Bug	16	The Test Case 'Save as new' button was not creating a new Test Case. This has been corrected.
1712	Bug	16	If multiple queries with the same query text were opened then the Test Case Run screenshot would highlight the first on the page, not the one connected to the relevant Field. Now the Field PreText will be used to make sure that the correct Field is highlighted.
1725	Bug	16	Rave pages containing log records were sometimes truncated on the right or left hand side. This has been corrected and the entire page should now be included in the screenshot.
1726	Bug	16	The Test Case Result pdf was not generated if test data included symbols such as '<'. This has been corrected.
1683	Feature	16	If access to the TrialGrid UAT draft has not been correctly configured an error message is displayed. The text of this error message has been improved.
1723	Bug	16	A javascript error could occur on loading the Test Case list page. This has been fixed.
1720	Feature	16	Automated Test Case runs were consuming more server memory than necessary. This has been improved. A previous attempt to correct this issue was made on 2020-02-06.
1720	Feature	16	Automated Test Case runs were consuming more server memory than necessary. This has been improved.
1693	Feature	16	Test Case Templates now have placeholders for Check Action target datapoints. See documentation for more details.
1689	Feature	16	Test Case Templates now have placeholders for Folders. See documentation for more details.
1497	Feature	16	Test Case Templates are now supported. See documentation for more details.
1687	Feature	16	When editing Test Cases, error messages will now be displayed at the bottom of the editor as well as when hovering over the error marker next to the line(s) with error(s).
1685	Feature	16	The Test Case Excel list now highlights Folder, Form and Field names in the Edit Check description column.
1475	Feature	16	Test cases now have Standards Compliance comparisons against libraries.
1485	Feature	16	The Test Case list has Standards Compliance information so it can be filtered for objects which are different from the library, not found or modified.
1554	Bug	16	Test Case editor loading performance was improved. This is especially noticeable with large Test Cases.
1681	Feature	16	When a Folder which has a Parent Folder is referenced in a Test Case an editor warning symbol will be displayed if the Folder is part of a nested Folder structure. This is to help avoid surprises because Rave will create the Parent automatically.
1584	Bug	16	When a Folder which has a Parent Folder is referenced in a Test Case, the Parent Folder should be specified in the Test Case, using an absolute folder reference.
1675	Bug	16	< and > characters in query text messages would cause errors when generating the Test Case list pdf document. This has been corrected.
1667	Feature	16	The Test Case Excel list now contains the description of Edit Checks.
1668	Feature	16	The Test Case Excel list now contains the Names of related objects such as Forms.
1670	Feature	16	The Test Case pdf list now contains the description of Edit Checks.
1669	Feature	16	The Test Case pdf list now contains the Names of related objects such as Forms.
1671	Feature	16	The Test Case Results pdf now has the Edit Check Description at the start of the main content.
1672	Feature	16	The Test Case Results pdf now contains the Names of related objects such as Forms.
1678	Feature	16	Edit Check descriptions now contain the Pretext of Fields to make them easier to understand for all users.
1660	Feature	16	When running Test Cases there is now an option 'Continue on failure'. When set on the Test Case runner will attempt to execute steps after a failed step in a scenario. When off (the default) the runner will stop running steps within a scenario when it encounters a failed step. This option can be useful to report the success or failure of all test steps without having to fix the first issue and then re-run.
1661	Feature	16	When running Test Cases there is now an option 'Check user roles'. When set on (the default) the Test Case runner will check that the Rave user accounts have the specified role in Rave. When set off the Test Case runner will report that the roles are different but will attempt to execute the tests using the given accounts.
1665	Feature	16	The Test Case helper for data entry steps will not insert a Units column in the step table if no units are specified.
1659	Feature	16	Automated Test steps which check data values will now match decimal numbers if there is a difference in leading or trailing zeros, e.g. 012.20 will match 12.2. Numbers will still not be rounded so 12.19 will not match 12.2.
1625	Bug	16	The performance of importing Architect Loader Spreadsheets with Automated Test Cases was improved.
1635	Bug	16	The Test Case Advisor now only checks Folders in the Subject Calendar if the Folder is in the default Matrix or the Folder is created in the Test case.
1634	Bug	16	The Test Case Advisor will add an issue and the Test Case will require attention if more than one Form in the same child Folder is not in the default Matrix.
1655	Bug	16	The Test Case Advisor will now add a 'save form' step for any folder and form which is present in a Check Action but not in the Check Steps. This will ensure that the datapoints on that Form are submitted and the Check Action will run. Note that such Checks might deviate from recommended best practices - see Diagnostic 0058 'Check Actions should have a matching Check Step'.
1656	Bug	16	The Test Case Advisor will now add steps to create Folders and Forms which are used in a sub-check to make Fields in the main edit check visible and if these Folder/Forms do not exist in the default Matrix.
1657	Bug	16	The Test Case Advisor was generating values for 'age' derivations the wrong way around, ie. the earliest and latest dates were inverted. This has been corrected.
1653	Bug	16	The Test Case Run pdf would fail to be created if there were data entry steps containing long Folder, Form or Field OIDs. This has been corrected.
1654	Bug	16	The Test Case Run pdf would fail to be created if the Test Case referred to an Edit Check which does not exist. This has been corrected.
1650	Bug	16	The Test Case Run pdf would fail to be created if an Edit Check name contained a ':' character. This has been corrected.
1651	Bug	16	The Test Case Advisor was not always choosing an appropriate Folder when adding steps to make a Field visible. This has been corrected.
1649	Bug	16	Automated Test Case run pdf files were not being generated if the content contained an '&' character. This has been corrected.
1647	Bug	16	Automated Test pdf files were not being generated because of an error in the location of font files. This has been corrected.
1297	Feature	16	The Test Case Advisor will now add data entry steps to make Fields visible if they are not visible by default and are referenced in the Edit Check.
1315	Feature	16	The Test Case Advisor has a link to navigate directly to the Test Cases list.
1426	Feature	16	If a Field has a Default Value the Test Case Advisor will now attempt to use that value in the suggested Test Case. If the Default Value can be used to generate test scenarios then the Field will not be included in enter data steps and a note will be added to the test scenario. If the Default Value is not used then an alternative value will be provided (if possible).
1573	Feature	16	Screenshots are now taken of the 'Form exists' step. Note that from TG_UAT draft version 19 and onwards, there will not be a screenshot of the 'Form exists' step.
1574	Feature	16	When running a Test Case TrialGrid will expand the horizontal width of the screenshot if the page in Rave is wider than the default screen size, for example to display a log record table.
1578	Feature	16	The Test Case Advisor will now add data entry steps to populate derived Fields which are used in an Edit Check, if the Derivation can be evaluated.
1579	Feature	16	If the Test Case Advisor cannot suggest any data entry values then it will create enter data steps with no values, to make it easier to manually enter values.
1580	Feature	16	The Test Case Advisor will create cross-references to any Forms referenced in the Edit Check.
1581	Feature	16	If the Test Case Advisor cannot create a valid Test Case it will insert a step to document the issues which need to be resolved manually.
1584	Bug	16	Parent Folders can now be used in Test Cases, see Automated Testing Step Reference
1600	Feature	16	The Test Case list has a new option to export the selected Test Cases to a pdf document.
1610	Feature	16	The Test Case Advisor suggested words such as 'TREATMENT' for text Fields. These words were sometimes not appropriate for the Field. Now the Test Case Advisor will use an alphabet string such that a text Field of length 5 characters will have a suggestion of 'ABCDE', up to a maximum of 10 characters. In future TrialGrid will have features to allow pre-defined lists of potential test values to be created.
1615	Feature	16	When a Form contains a derived Field with a 'NOW' Derivation which triggers Custom Functions to run then the 'enter data' test steps will not trigger the derivation (a limitation of Rave Web Services). To ensure that all expected actions have occurred a new Test Step can be used, e.g.: When I save form "AE" in folder "VISIT"
1624	Bug	16	When verifying Test Case results, TrialGrid was not taking into account datapoints which had multiple queries and so might report a false result. This has been corrected.
1639	Feature	16	The Test Case Advisor will use the enter and save data entry step.
1646	Feature	16	The Test Case list has a new option to export the selected Test Cases to an Excel spreadsheet.
1643	Bug	16	Copying and pasting a password when running a Test Case could lead to an error. This has been corrected.
1640	Feature	16	Test Cases now have database fingerprints which will be used to add Standards Compliance for Test Cases. No changes are visible to users yet.
1642	Feature	16	'User Acceptance Testing' has been renamed 'Automated Testing'.
1630	Feature	16	Scenario count was removed from the Automated Testing table. It didn't provide a lot of value and we wanted to reduced the visual clutter on that table.
1632	Feature	16	If a Test Case was edited since it was last entered into a Test Set it now shows it was changed in the Test Case listing.
1633	Feature	16	If an object related to an Test Case is edited after the Test Case is put into a test set the Related Object should show a Changed marker in the Test Case List.
1607	Bug	16	The Test Case editor helper for data values was not refreshing the list of Fields when a Form was selected. This has been corrected.
1412	Bug	16	If the Test Case Advisor is run concurrently on the same Draft or the same Edit Check there was a risk of failure because of a duplicate Test Case name. This should not now happen, though it is possible that the resulting Test Cases will have identical names.
1565	Bug	16	If the Test Case Advisor is run concurrently on the same Draft or the same Edit Check there was a risk of failure because of a duplicate Test Case name. This should not now happen, though it is possible that the resulting Test Cases will have identical names. (Duplicate of #1412)
1566	Feature	16	When the Test Case Advisor has been run it can be re-run without closing and re-opening it.
1567	Feature	16	When creating Test Cases using the Test Case Advisor with 'delete existing test cases' selected the Test Case Advisor was appending '(1)' to the Test Case name. This is not necessary since existing Test Cases are deleted.
1568	Feature	16	When creating a Test Case for an Edit Check there are now 2 buttons in the sidebar. 'Add' will create a new Test Case in addition to any existing ones. 'Replace' will create a new Test Case and delete any existing ones for that Edit Check.
1572	Feature	16	When the Test Case Advisor processes an Edit Check containing a Field which is not visible by default the Test Case Advisor will attempt to find an Edit Check with a SetDataPointVisible check action for that Field and will add data entry steps to make the Field visible. If no check action can be found or if the check action is in an inactive Edit Check or an Edit Check which also references a Custom Function then the additional data entry steps will not be added.
1575	Feature	16	Comments added by the Test Case Advisor are now displayed in the list of Edit Checks processed.
1140	Bug	16	The PDF report generated from the Custom Function list page was incorrectly showing a list of commas in the UAT Test column. This has been removed.
1563	Bug	16	The PDF report generated from the Test Case list page was incorrectly showing the checkbox selection column. This has been removed.
1577	Bug	16	In UAT results long data tables caused PDF generation to fail, this was corrected.
1534	Feature	16	If an Edit Check has multiple check steps with no Folder specified then the Test Case Advisor will select one Folder to apply to all these steps when it suggests test data.
1559	Bug	16	The Test Case Advisor will order test data by Folder Ordinal and Form Ordinal.
1560	Feature	16	The Test Case Advisor will only use 'Other, specify' data dictionary entries if there is no alternative.
1561	Feature	16	The Test Case Advisor will suggest empty values for data dictionary fields which are compared against a value of 0. This is because Rave treats 0 as being empty when evaluating edit checks for dictionary fields.
1540	Feature	16	Lists with Label columns can now be sorted by label.
1336	Bug	16	In the Test Case Import dialog, long Test Case names would cause the table of Test Cases to overflow the popup window. This was corrected.
1529	Bug	16	When running a set of UAT Test Cases if the background server is restarted or fails for some reason the UAT Run would become stuck in a "running" state but would never complete. The system now detects when a UAT Run was not complete and will restart the task, re-running from the last test not completed.
1538	Bug	16	UAT Run button ignored checkboxes and would include all filtered entries. This was changed to honor the checked selections.
1533	Feature	16	The Test Case listing now has checkboxes to select test cases to be archived, run or batch deleted.
1531	Bug	16	If the PreText for a Field used in a UAT test contains a html non-breaking space (&nbsp;) PDF generation for the UAT result would fail. This was corrected.
1508	Feature	16	There are now Test Case steps to inactivate Folders, Forms and Log Records.
1519	Feature	16	When searching lists of Folders, Forms and Fields in Test Case editor helpers, the search is now case-insensitive.
1520	Feature	16	The Test Case editor helpers display lists of Folders, Forms and Fields in Ordinal order.
1521	Feature	16	There are now Test Case editor helpers for '{subject_name}' steps.
1522	Feature	16	There are now Test Case editor helpers for '{datapoint}' steps.
1523	Feature	16	There are now Test Case editor helpers for inactivate Folder, Form and Record steps. Note: The inactivate Folder step has subsequently been retired, see #3381.
1526	Bug	16	The Test Case editor will display a warning if you change the Test Case Name or steps and try to leave the page without having saved the Test Case.
1528	Feature	16	The Test Case editor helpers for '{datapoint}' steps let you select the Folder OID, Folder repeat number, Form OID, Form repeat number, Field OID and Record Position.
1530	Feature	16	The Test Case editor helper for query steps lets you select query text from Check Actions in the Draft or enter some other text which is the expected result of the Test Case.
1491	Bug	15	The Test Case Result PDF document did not include all table headings. This has been corrected.
1492	Bug	15	The Test Case Result PDF document did not include query text messages. This has been corrected.
1493	Feature	15	The Test Case Result PDF document now includes the description of any related Edit Checks.
1506	Feature	15	The Test Case Editor now includes a button to switch between editing mode, where Folder, Form and Field OIDs will be displayed, and view mode where names will be displayed.
1507	Feature	15	The Test Case Result PDF document now includes a description of the Test Case using Folder, Form names and the Field Pretext, in addition to the description using object OIDs.
1483	Feature	15	A UAT Editor helper was added for the "I should see/not see the following query" check step. This allows the user to search for and select the Open Query text from Edit Checks.
1495	Feature	15	The TestCase Advisor and Edit Check TestCase generator will now create a test case for the UniqueSubjectName check action. This Test Case is generated in an invalid state since the user will need to add steps which ensure a duplicate subject number is generated in order to fire the check.
1482	Feature	15	In a UAT test an unknown EDC role is normally a warning but for the value "{role}" it is now an error. The Test Case Advisor enters this value for roles when it does not know what role to choose for entering view and entry restricted data.
1476	Bug	15	The save button in the Test Case Editor was disabled after trying to save a Test Case with no name entered. This has been corrected.
1472	Feature	15	New steps available in Test Cases allow subject names to be specified in the Test Case. See Test Case Subjects for more information.
1457	Bug	15	Intermittent failures have been noticed in Test Cases run against iMedidata and Rave EDC when taking screenshots. This appears to be caused by iMedidata returning to the login page after a successful login has occurred. Additional logic and logging has been added to TrialGrid to work around this issue.
1458	Feature	15	The Test Case run log now records the Rave user account names used during the test run.
1460	Feature	15	The Test Set Run page is now clearer that the Rave Study Site Number is required.
1461	Feature	15	If the Rave credentials provided for a Test Set Run are invalid then all Test Cases within that run will be marked as Cancelled and will have a Run log message with details of the problem.
1419	Feature	15	When creating a UAT Test Run the URL, Study, Environment and Site parameters will be cached and will be used as the defaults when creating another Test Run for the same draft.
1420	Feature	15	A page heading has been added before each scenario in the UAT Test results pdf to make it easier to see where a new scenario starts.
1443	Feature	15	The Test Case Advisor has a new option 'Delete existing test cases', which will delete any existing test cases for the selected Edit Checks in the draft and then create new ones.
1438	Bug	14	UAT tests would not run against a Rave URL with the Core Configuration setting 'All upper case' enabled. This was corrected.
1423	Bug	14	Test Case result screenshots were not always showing open log records. This has been corrected. Note that Rave EDC (RaveX) Test Cases will open log records for screenshots if there are fewer than 100 log records. Test Cases with more than 100 log records will run but without taking screenshots of log records after 100.
1424	Bug	14	Test Case results for Rave EDC (RaveX) now show the whole screen when a screenshot is taken.
1429	Bug	14	If a failure occurred in an early part of the processing for a UAT run before any test cases were executed, the error was not reported to the user, the task would simply fail. This was corrected and these errors are now reported to users and test cases are shown with a Failed status.
1431	Bug	14	Infrastructure changes caused UAT result live-update to fail. This was corrected.
1427	Bug	14	Some Test Cases containing unicode characters would fail to run. This has been corrected.
1415	Feature	14	If a Draft object (Form, Edit Check, Folder, Custom Function, Dictionary or Test Case) is copied from a Library or another Draft then the sidebar will contain informaton about which object and Draft it was copied from. Standards Compliance information is now displayed in the object sidebar. Note that Derivations cannot be copied yet - this will be added in a future release (issue #1428). (Duplicate of #733)
1365	Bug	14	In UAT Run page Study Site Number was whitespace-sensitive meaning a space at the start or the end of the Study Site Number would cause the system to not match the study site. This was corrected.
1366	Feature	14	When running UAT tests invalid username/password messages now make clear when the issue is with Rave Classic accounts.
1313	Bug	14	The UAT Test Case Helper for the 'When I log in with role "{role}"' step would change the step text to 'When I am logged in with role "{role}"' which was invalid. This was corrected.
1314	Bug	14	When selecting a Step to insert in the Test Case editor it was not possible to add the same step repeatedly. An "Add" button must now be clicked to add the step to the Test Case editor. This allows a step to be selected and then added each time the Add button is clicked.
1319	Bug	14	A Helper (wrench icon) was shown for the 'Then I should see "{datapoint_ref}" has value "{value}"' UAT step in the Test Case editor when it should not have been shown. This was corrected.
1316	Bug	14	If an Edit Check referenced a numeric Field by value and by 'IsEmpty' or 'IsNotEmpty' check steps then the Test Case Advisor would fail to generate a Test Case. This has been corrected.
1320	Bug	14	The Test Case runner would sometimes record a failure when trying to take a screenshot of a Log Form. This has been corrected.
1321	Bug	14	The Test Case Advisor has been changed to suggest Test Cases with 'I enter only this data' steps rather than 'I enter data'. This works better for Edit Checks comparing values across standard and log Fields in Rave. Some Edit Checks which use Custom Functions might be better run with 'I enter data', this will need to be reviewed and tested. 'I enter data' submits all datapoints on the form. 'I enter only this data' submits only those datapoint which are included in the Test Case.
1322	Bug	14	The Test Case runner would fail when verifying an Update Form or Update Folder Name action if the Check Action referenced a date Field. Rave uses a mixed case date to update the Folder or Form Name (for example 'AE 10 Jun 2010') even if the date on the form is in upper case ('10 JUN 2010'). Now the Test Case runner will perform a case-insensitive verification on Folder and Form names.
1326	Bug	14	The Test Case Advisor was not generating suitable values if a date Field, with 'yyyy' format, was being compared against another date Field with 'dd MMM yyyy' format. The suggested test values would not satisfy the logic of the Edit Check. This has been corrected.
1329	Bug	14	The Test Case Advisor was not incorrectly inserting a sub-folder reference on Merge Matrix Check Action steps. This has been corrected.
1330	Bug	14	If a Folder has a parent Folder then the parent will be included in suggested Test Cases. For example, a Folder 'AE_P' has a parent 'AE'. Suggested Test Cases will have steps like: When I enter data: | DataPoint | Value | | AE/AE_P.SAE.AETERM[1] | HEADACHE |
1331	Bug	14	If an Edit Check included static values then the Test Case Advisor would include them in the suggested Test Case even if they would be non-conformant for that Field. This has been corrected.
1335	Bug	14	The Test Case runner would fail if the User Data String in a Data Dictionary Entry contains a single quote. This has been corrected.
1337	Feature	14	The Test Case Advisor will base date values around a date 2 years before the current date. It will suggest values (depending on the data format) which are 1 day, 1 week, 1 month and 1 year before and after the base date (2 years ago). This will avoid future dates being included in the suggested data.
1328	Feature	14	If an Edit Check references a Dynamic SearchList Field the Test Case Advisor will add a comment to the suggested Test Case, which will be categorised as requiring review. TrialGrid Test Cases can verify values within a Dynamic SearchList and can enter data into a DSL Field, but the values cannot be suggested automatically and must be inserted into the suggested Test Case.
1342	Feature	14	If an Edit Check references a FileUpload or Signature Field the Test Case Advisor will add a comment to the suggested Test Case, which will be categorised as requiring review. TrialGrid Test Cases cannot test FileUpload or Signature Fields.
1343	Feature	14	The Test Case Advisor will check Field view and entry restrictions. If a Field is view or entry restricted to the default role then an additional 'When I log in with role "{role}"' step will be inserted before the restricted Field. If further Fields are not restricted then a log in step for the default role will be inserted after the restricted Field steps. A comment will be added to the suggested Test Case, which will be categorized as requiring review.
1344	Feature	14	The Test Case Advisor will choose Lower and Upper range values for numeric Fields in preference to the maximum possible values. This leads to more realistic Test Data.
1345	Feature	14	The Test Case Advisor will now generate Test Cases for Edit Checks which have Logical Record Position check steps. A comment will be added to the suggested Test Case, which will be categorized as requiring review.
1346	Bug	14	The Test Case Advisor was suggesting values for Set Datapoint Check Action steps using the Coded Data value (for Fields referencing a Data Dictionary). The Test Case expects this to be the User String. This was corrected.
1403	Feature	14	The Test Case Advisor will now add a comment if the Edit Check references an inactive or invisible Field, or an inactive Form.
1404	Bug	14	If a SetDatapoint check action has a value which is not present in the Data Dictionary for the target Field (if that Field has a Data Dictionary) then the Test Case Advisor will use the value in the Check Action and will add a comment to the Test Case.
1235	Feature	14	In the UAT Test Case editor, the test step "I am logged in with Role" is now checked against the core configuration in TrialGrid and a warning is shown if the EDC Role name is not present or the role is present but inactive.
1245	Feature	14	The 'I am logged in with role "{role}"' UAT test step now has an associated editor which can be accessed by clicking the icon in the margin of the Test Case editor. A dialog opens which allows the user to choose an EDC role from the core configuration or to enter a new role name.
1249	Feature	14	The "folder {folder ref} exists" UAT test step now has an associated editor which allows selection of a Folder OID and the entry of Folder paths such as FOLDER1[1]/CHILD_FOLDER[2].
1255	Feature	14	The "form {form_ref} exists in folder {folder_ref}" UAT test step now has an associated editor for the selection of Form and Folder OIDs and the entry of Form references containing repeats e.g. "AE[2]" and Folder paths.
1256	Feature	14	The "I enter data" UAT test step now as an associated editor. This allows the selection of Folder / Form / Field / Data Dictionary and Unit Dictionary values (where required).
1237	Bug	14	Rave 2018.2.3 and 2018.2.4 restrict access to the Rave API from within Custom Functions. The TrialGrid UAT draft has been updated for compatibility with these Rave versions.
1156	Feature	13	When running a UAT Test Case no screenshot will be taken on a Login step. This is to avoid capturing information about studies other than the study being tested.
1157	Feature	13	Before running a UAT Test Case the TrialGrid UAT study must be configured correctly by a system administrator. If it is not configured correctly the Test Case cannot be run. More informative error messages are now displayed explaining what part of the configuration is incorrect.
1134	Bug	13	When creating a UAT Test Run if a non-existent Rave URL was entered then an internal error message was displayed. This has been replaced by a readable message.
1135	Bug	13	In the UAT Test Case Editor selecting the 'Then I should see form {form} in folder {folder}' step was incorrectly inserting another step. This has been corrected.
1137	Bug	13	Because of a bug in Rave Web Services (MCC-147590) the 'Enter Data' step in UAT Test Case was not causing all Fields on a Log Record to be submitted. The Rave Web Service calls have been modified to workaround this bug and the 'Enter Data' step now functions as expected on Log and Standard records.
1123	Feature	13	Draft Properties now includes an option to control whether to show UAT Coverage statistics on the Draft Home page. These statistics show how many Edit Checks, Derivations, Forms and Custom Functions have associated UAT Tests and how many passed on their last run.
3562	Feature	13	The Test Case list can be filtered by the status of the last run.
1064	Feature	13	Clicking the UAT Test Case count on the Draft home page shows a list of UAT Test Cases.
3562	Feature	13	The Test Case list can be filtered by the status of the last run.
3563	Feature	13	The Test Case list can be filtered by label.
3564	Feature	13	The Test Case list can be filtered by validity.
3565	Feature	13	The Test Case list can be searched.
1065	Feature	13	A Test Case can be deleted from the list of UAT Test Cases.
1066	Feature	13	A Test Case editor was added.
1067	Feature	13	Entering @EditCheck:EDIT_CHECK_NAME in the Test Case Editor creates a relationships between the Test Case and the Edit Check for test coverage and traceability from test to Check.
1068	Feature	13	Similar to other object Editors, users can make comments on Test Cases.
1069	Feature	13	Similar to other object Editors, users can assign Labels to Test Cases for workflow.
1070	Feature	13	Steps which test Query text in a Test Case such as "Then I should see Query Text...." are checked against referenced Checks (via the @EditCheck:CHECK_NAME) and a warning is given if no referenced Edit Check has an OpenQuery action with that text.
1071	Feature	13	Similar to Edit Checks, Derivations may be referenced with @Derivation:DERIVATION_NAME in the Test Case editor.
1072	Feature	13	Similar to Edit Checks, Custom Functions may be referenced with @CustomFunction:CUSTOM_FUNCTION_NAME in the Test Case editor.
1073	Feature	13	Similar to Edit Checks, Forms may be referenced with @Form:FORM_NAME in the Test Case editor.
1074	Feature	13	Reference tags (@EditCheck, @CustomFunction etc) are not case sensitive.
1075	Feature	13	Object references are shown in the Test Case list as links to those objects. If a reference tag points to an object that does not exist (@EditCheck:NO_CHECK_OF_THIS_NAME) then the reference is shown in red text and the text is not a link.
1080	Feature	13	When a Test Case is related (via @) with an object that does not yet exist, creating that object will activate the link in the Test Case list and remove the red text.
1076	Feature	13	In the margin of the Test Case editor, an icon for a referenced object will appear. Clicking the icon in the margin navigates to that object (hint: Ctrl-Click to open in a new tab)
1077	Feature	13	Tickets may be referenced in Test Cases via the @Ticket:TICKET_NUMBER or @Specification:TICKET_NUMBER tag. This feature was removed in favor of #1673 in September 2021.
1081	Feature	13	New Test Cases are created with a boilerplate example outline of a test to help users get started.
1082	Feature	13	When an Edit Check has related Test Cases, this is shown in the side-bar of the Edit Check editor as a robot icon with a count of Test Cases.
1083	Feature	13	From the side-bar of the Edit Check editor a new Test Case can be generated for the Edit Check.
1084	Feature	13	In the Test Case listing, clicking the Run button creates a Test Set.
1085	Feature	13	The Test set created by clicking the Run button in the Test Case listing contains all the visible (filtered) Test Cases. Custom Test sets can be created by filtering the Test Case list.
1086	Feature	13	A snapshot of the Test Case (i.e. it's current content) is copied into the Test Set. The original Test Case can then be changed but the version in the Test Set is fixed, will not change and cannot be edited.
1087	Feature	13	If a Test Case is included in a Test Set and that Test Case is subsequently changed, a marker appears on the copy of the Test Case in the Test Set to show that it is no longer the same as its source Test Case.
1088	Feature	13	If a Test Case is included in a Test Set and the original Test Case is subsequently deleted, the copy of the Test Case remains in the Test Set and a market appears on that copy to show that its source has been deleted.
1089	Feature	13	Invalid Test Cases (such as ones that reference Datapoints that do not exist) cannot be added to a Test Set run and will be ignored.
1090	Feature	13	Users may delete Test Set Runs. All associated results and screenshot evidence will also be deleted.
1091	Feature	13	When running a Test Set, all the roles referenced in the Test Cases are found and the user must provide username/password credentials for them in order to run the Test Set.
1092	Feature	13	When running a Test Set the system will identify if a Test Case requires Subject Admin permission and ask for credentials for a user with that Role. Subject Admin permission is required where a step like "Given FormA in FolderB exists" is used.