Module : Validation
Issue |
Type |
TrialGrid Version |
Description |
|---|---|---|---|
3677 |
Bug |
64 |
21 CFR Part 11 Statement was updated to show that 2FA cannot be set up for users who are managed by Single Sign On. |
3678 |
Bug |
64 |
Introduction to validation docqumentation clarifies the test coverage level required for individual files and the maximum uncovered lines allowed in any individual file. |
3629 |
Bug |
61 |
Validation docs did not include code standards findings output. This was corrected. |
3508 |
Bug |
57 |
In validation documents links between issues and source code were not rendered correctly. This was corrected. |
3070 |
Bug |
44 |
The validation IQ document was missing the Postgresql database version. This has been corrected. |
2649 |
System |
42 |
In the validation documentation features are categorized into modules. These modules now have introductory text to provide an overview of the function. |
2431 |
System |
30 |
All references to "Annotates" modules in release notes were replaced with "Document Templates" for greater consistency with the system UI. |
2429 |
System |
30 |
All references to UAT module in release notes were replaced with "Automated Testing". |
1714 |
Feature |
30 |
Related functional module was added to release notes in the help and validation documents. |
2406 |
Feature |
30 |
The Validation documentation now lists Unit Tests which test TrialGrid's security (user authentication and logical security/user permissions). |
2403 |
Feature |
28 |
Installation Qualification and Operational Qualification documentation was added to the Validation documentation. |
2393 |
Bug |
28 |
The Validation documents were displaying the wrong version number. This has been corrected. |
2387 |
Feature |
28 |
Validation documentation was updated to refer to the TrialGrid Ltd Quality Management System for details of 3rd Party Systems used to support the TrialGrid. |
2061 |
Feature |
21 |
The validation package generation process was updated to include greater information on tests run. |
1901 |
Feature |
19 |
A summary of validation activity counts was added to the validation documentation (i.e. number of unit tests run, number of requirements tests executed etc). |
1828 |
Bug |
17 |
In validation documents some testing scenarios were not properly presented. This was corrected. |
1845 |
Feature |
16 |
Disaster recovery information in the validation plan now references the Quality Management System instead of repeating this information. This change only affects the validation plan which is reviewed by auditors. |
1434 |
Feature |
14 |
Validation documents now include a link between references in the source code to an issue and the documentation for that issue. This provides a link for auditors between an issue and the testing code that shows the issue is addressed or feature implemented. |
1435 |
Feature |
14 |
Validation documents now include a link between an issue and any testing scenarios (feature tests) related to that issue. This provides a link for auditors between the issue and the evidence that issue was addressed or feature implemented with visual test evidence. |
1436 |
Bug |
14 |
In validation documents some steps where text was input were not displayed correctly. This was corrected. |
1186 |
Feature |
13 |
Static Application Security Testing (SAST) output should be included in the validation package. SAST analysis examines the TrialGrid source code for potential security vulnerabilities. The output of this automated analysis was added to the validation package for TrialGrid releases. |
1112 |
Bug |
13 |
Validation docs were no longer showing screenshots in validation portal. This was fixed. |
1113 |
Bug |
13 |
Validation docs were showing copyright 2018. This was updated to 2019 for future releases. |
1114 |
Bug |
13 |
Validation docs were not showing some text elements in the results section. This was fixed. |
924 |
Bug |
9 |
The application version number was incorrect in the help documentation on the production site. This has been corrected. |
965 |
Feature |
9 |
When a change is made via a Diagnostic, this is reflected in the audit trail with a small badge next to the audit trail entry which shows the short-id number of the Diagnostic (e.g. 0001) In the full audit listings (at user, URL, Project and Draft level) Diagnostic short names also have their own column in the table. Note this badge is only shown for Diagnostic results from runs made after this change, not historical results. |
908 |
Bug |
9 |
Display/formatting of release notes help page was fixed. |
571 |
Bug |
3 |
Link to code testing coverage documentation in validation package is incorrect on index page leading to a file not found error when viewed on validation portal. This was fixed. |
571 |
Bug |
2 |
Invalid link in validation documentation to code coverage was addressed in previous change but issue returned. This was fixed. |
351 |
Feature |
1 |
Validation Docs: Link between Issues / Merge Requests. |
352 |
Feature |
1 |
Validation Docs: Link between Requirements tests and Issues. Where an Issue is referenced in a Requirement Test the validation docs now generate a hyperlink to a copy of the Issue and its history in the validation package for ease of traceability. |
340 |
Bug |
1 |
Requirements test coverage for Core Configuration settings was expanded. |