'Tester' field of run step appears blank after changing the execution status by using the drop-down list
Description: When executing a test run in Manual Runner, the Tester field of each test step should populate with the current user's ID when a step status is selected. This functionality works correctly when using the Pass/Fail buttons, but not when selecting the status directly from the drop-down list.
Impact: This issue is limited to the user interface, because the Tester field is being populated in the back-end. The user interface will reflect this the next time the screen is properly refreshed.
Workaround: Wait for the next action that causes the screen to refresh. The data will become visible.
'Pin to Baseline' should not be permitted on test sets with signatures.
Description: Currently, VERA will allow the Pin to Baseline action a test set with pre-execution approval signatures in the Ready for Execution workflow state, as long as no test runs exist within the test set. This is an issue, because pinning to a baseline may cause the deletion of any test instance not associated with the baseline, which would invalidate the pre-execution approval signature(s).
Impact: For teams using both baselining and approvals on test sets, the Test Set Designers must be careful of using the Pin To Baseline feature after pre-execution approvals are complete. Once the first run is executed in the test set, then the risk is removed, because the Pin To Baseline feature will become disabled.
For teams that do not use both baselining and approvals on test sets, then this issue will have no impact.
Workaround: If the issue arises, then the Test Set Designer should revise the test set and re-route for pre-execution approval.
Requirement Managers cannot reorder entities in the Requirements module
Description: A Requirement Manager is unable to reorder requirement records using the toolbar buttons in the Requirements module.
Impact: A Requirement Manager that is not also a Requirement Author will need to request a Requirement Author to make the updates.
Workaround: It is recommended that the Requirement Manager should be assigned Requirement Author permissions, also.
Smart Paste fails when a field marked 'Reset on Copy' does not exist in a Requirement Type
Description: The VERA Smart Paste feature will not work correctly if it encounters a field that is configured to be reset in the new copy, but the field does not actually exist on the record being copied. This most typically will happen if a requirement field is configured to be reset, but the field does not exist in all requirement types.
Impact: When this configuration issue exists, it will prevent the user from completing the Smart Paste action on certain records.
Workaround: Administrators can implement a workaround into their configurations by either excluding the field from the "reset on copy" configuration, or by creating a new record type to correspond with the requirement type that has the special field. Contact Tx3 Support for more assistance.
ALM 12.55 error "You don't have permission to execute this action" appears when user try to cancel run by using "X" button on manual runner
Description: In QC/ALM 12.55, if a user starts a test run in Manual Runner, then selects to cancel the test run without saving, an error message will display and the run will not be cancelled.
Impact: This issue impacts all VERA projects in QC/ALM 12.55. Prior versions of QC/ALM are not impacted.
Workaround: There is no workaround to allow a run to be cancelled without saving in QC/ALM 12.55. The only option is to select "Yes" to save the run, and then select to cancel it using VERA's electronic workflow.
"VERA Signature Verification" does not gracefully support missing user names
Description: The VERA Signature Verification utility will fail to verify an electronic signature if the signature is missing a full name of the signer.
Impact: Organizations that do not have full names configured for their QC/ALM users will not be able to verify the integrity of their electronic signatures using the VERA Signature Verification Utility.
Workaround: Tx3 recommends that full names should be configured for all QC/ALM users that will create electronic signatures. If you have a need to verify the integrity of electronic signatures generated without full names, then please contact Tx3 Support for assistance.
VERA 2.x Does not recognize the ALM Type field for Runs without the prefix
Description: When evaluating approval route rules for test runs, QC/ALM does not recognize the displayed value in the Run Type field. (e.g. MANUAL, BUSINESS-PROCESS).
Impact: This issue only impacts administrators when designing approval route rules. Administrators can use the workaround listed below to mitigate this issue, and users will not be impacted.
Workaround: When configuring approval route rules for test runs, if a rule must reference the run's Type field, then prefix the value with "hp.qc.run." in your Approval Policy.json file. Example: hp.qc.run.MANUAL
Workflow script error when smart deleting a test case which exists in test set
Description: In some cases, an error will display while transitioning between modules after using the Smart Delete feature on a test case entity that was not removed from all test sets prior to deletion.
Impact: This error will be an occasional nuisance to users. It does not prevent the Smart Delete feature from functioning.
Workaround: It is recommended that test cases are removed from all test sets before using Smart Delete. This will prevent the error. Alternatively, the user can refresh their login session after the error occurs.
NOTE: VERA will not allow a test case to be deleted if it has existing test runs. This issue and guidance is limited to test cases that were added to one or more test sets, but that were not yet executed.
Intermittent Error Message when Using Password Encryption Utility
Description: When using the VERA Password Encryption Utility, an intermittent error may display when the utility attempts to access the system clipboard. (COMException: OpenClipboard Failed (Exception from HRESULT: 0x800401D0 (CLIPBRD_E_CANT_OPEN)))
Impact: This issue only impacts administrators using the VERA Tocsa Integration solution. No other users should have a need to use the Password Encryption Utility.
Workaround: When the error displays, retry the encryption operation.
Clipboard error when copying version information text
Description: An error can occur when pressing the "Copy to Clipboard" button in the VERA version information screen. Error message: "OpenClipboard Failed (Exception from HRESULT: 0x800401D0 (CLIPBRD_E_CANT_OPEN)).
Impact: This issue can occur intermittently when using the Smart Copy action in the VERA Action Menu.
Workaround: Try again to see if the issue immediately resolves itself. If it doesn't, try closing other applications that may have a lock on the clipboard.
Cannot make a Test Step field editable when the Edit Step Action is prevented
Description: VERA does not allow a design step field to be configured as editable when the test case itself is in a workflow state that does not allow editing.
Impact: This issue prevents administrators from configuring a business rule allowing a specific design step field (such as a comments field) to be editable by approvers when a test case is routing for approval.
Workaround: Consult with Tx3 Support if you have a business case requiring this functionality. We may be able to identify a workaround configuration for your use case.
Smart Paste fails when the author on a requirement is not a member of the project
Description: Smart Paste can fail if the user in the Author field of the copied Requirement is no longer in the project.
Impact: Users may not be able to copy certain Requirements.
Workaround: If a Requirement cannot be copied, the user should have the project's User Administrator to temporarily re-add the missing user.
Error message contains typo when a task doesn't have an assigned order.
Description: A typo exists in the error message displayed when a task doesn't have an assigned order.
Impact: The error message is slightly less readable then expected.
Workaround: There is no workaround.
CSV Importer: Implement Cancel ability and record counts
Description: The 'Importing Records' progress bar screen in the CSV Data Importer feature is missing a Cancel Button and a displayed count of records.
Impact: Users doing an import of records from a CSV file cannot abort the operation once it is started. (The VERA software requirements indicate this should be possible.)
CSV Importer: Workflow State is not honored by Attachments
Description: The CSV Data Importer feature will allow importing attachments to records in a workflow state where this would normally be prevented (such as 'Routing for Approval' or 'Approved').
Impact: Users might be able to use the CSV Data Importer to import attachments to a record that has already received one or more electronic signatures. (Note: This only applies to requirements and test cases. It also only applies to adding attachments, not removing existing attachments.)
CSV Importer: Updates fail on some fields on a line that contains a value in the Subject field
Description: When using the CSV Data Importer feature to update existing test cases, the update may fail if a Subject field is specified inline with the test reference in the CSV file.
Impact: This issue will cause certain rows of the data import operation to fail while updating existing test cases.
Workaround: The data importer supports specifying the test case Subject field (folder name) on a separate line preceding the test case's line. This technique will prevent the above issue from occurring during an update operation.
CSV Importer: Utility does not validate the file extension before importing
Description: The CSV Data Importer feature will not validate the file extension of a file selected for import
Impact: Users can attempt to import non-CSV files, which will result in a file parsing error.
Workaround: Users will need to restart the wizard if they accidentally try to import a non-CSV file.
Transition Reason doesn't support including Revision Number with a different Label
CSV Data Importer: Missing attachments are uploaded as blank files w/out error
Description: When importing attachments using the CSV Data Importer, if the file path or file name does not exist, then an empty attachment of the expected name is created instead. No error or warning is provided to the user.
Impact: The record will have an empty (0 KB) attachment.
Workaround: After running the CSV Data Importer, the user should verify that no attachments have a size of 0 KB. Alternatively, attachments can be uploaded manually after the records are imported.
CSV Data Importer: Record version numbers are incremented, even when the record is not updated
Description: When using the CSV Data Importer in version-controlled projects, the QC/ALM version number may be incremented even when no changes are made to the record.
Impact: If the user attempts to use the importer to update a record that is locked by the VERA workflow, then the record version number will be incremented even after the update is prevented by VERA. This will give the incorrect appearance that the locked record was modified.
Workaround: Users and auditors can verify and prove that no actual changes were made to the locked record by viewing the record's Audit History.
CSV Data Importer: Req Traceability failures are not clearly reported by the utility
Description: When using the CSV Data Importer to import requirement traceability, if an error occurs while creating a trace link, then the Importer reports that the entire record failed to import even if it is only the traceability portion that failed.
Impact: The user may not realize that the record actually imported unless they search for it in ALM. Furthermore, they may not understand the source of the error message or how to resolve it.
Workaround: When troubleshooting import errors, users should search for imported records my Path and Name. If they discover a record did actually import, they should verify whether traceability may have been the root of the failure and continue troubleshooting from there.
Called tests are not evaluated inside a baseline
Description: Pre-execution approval rules are not correctly enforced when a test case inside a baselined test set contains called tests. The current status of the called tests will be evaluated instead of the baselined status of the called tests.
Impact: This issue only impacts test cases that both a) contain called tests and b) are used inside a test set that is pinned to a baseline. Pre-execution approval enforcement works as expected when using test cases without called tests inside a baseline, and also when using test cases with called tests outside of a baseline.
Workaround: Manual procedures must be used to ensure that all called tests are approved before pinning a test set to a baseline.
Smart Delete does not clear the integration fields for the Test Case or Execution List in Tosca
Issue: When deleting a Tosca test case or Tosca test set in ALM, the corresponding synchronization IDs are not deleted within Tosca.
Impact: This issue only impacts users using Tx3's integration between Micro Focus ALM and Tricentis Tosca.
Workaround: When a synchronized record is deleted from within ALM, manual clean-up must be done in Tosca.
VERA Data Import Utility does not properly handle invalid requirement types
Issue: The VERA Data Import Utility displays a confusing error message when it encounters an invalid requirement type in an import file
Impact: Users will have difficulty troubleshooting import failures if their import file contains requirement types that do not exist in the project.
Workaround: There is no workaround for this issue.
CSV Data Importer: wrong error message when user tries to update status field to value other than Draft
Issue: The VERA Data Import Utility displays a confusing error message when an import operation violates workflow status rules.
Impact: Users will have difficulty troubleshooting import failures if their import file contains records that cannot be imported due to their current workflow state.
Workaround: There is no workaround for this issue.
Only last attachment is added to requirement if there are more than 1 attachment path specified in CSV importer excel sheet
Issue: The VERA Data Import Utility cannot upload more than one attachment for a record. If more than one attachment is specified, only the last attachment is uploaded and no error is displayed.
Impact: Users may not realize that an imported record is missing some expected attachments.
Workaround: Users should only configure their import files to import one attachment per record. Additional attachments must be attached either manually or through additional imports.
Formatting issues in the 'Rich Text" field
Issue: Extra whitespace (line breaks / tabs) is sometimes added to the Rich Text field when it is saved.
Impact: This issue impacts users using the Rich Text field in the Requirements module.
Workaround: Use a regular memo field (with HTML formatting) instead of the Rich Text field.
Unexpected error when using 'Convert to tests' feature in the Requirements module
Issue: An unexpected exception will occur if the "Convert to tests" feature is used before the user has accessed the Test Plan module in the current session. The VERA workflow script will attempt to evaluate the creation rules for Test Cases from within the Requirements Module. In the background, this evaluation logic requires accessing workflow objects from the Test Plan module. However, if the user has not yet navigated to Test Plan within the current login session, then Test Plan's workflow will remain uninitialized.
Impact: Users will be unable to use this feature without using the workaround below.
Workaround: Navigate to the Test Plan module before using the "Convert to Tests" feature in the Requirements module. (Just viewing the Test Plan module is enough. No need to refresh or complete any actions.) Navigating to the Test Plan module causes the Test Plan workflow objects to initialize. They will remain initialized when the user navigates away from Test Plan into the Requirements Module, and "Convert to Tests" will work as documented.
Issues with VERA dialog windows on dual monitors (Intermittent)
Issue: Various issues have been reported with VERA dialog windows when using dual monitors. Some examples:
When entering justification text into the VERA Change Reason dialog in Manual Runner, the "OK" button cannot be pressed.
When approving a test run, the "Approve" button cannot be pressed.
When loading the VERA Action Menu, the buttons do not render.
Impact: Unknown. These issues have only been reported by a small number of users. Most users are able to use dual monitor displays with VERA without issue.
Workaround: Users have reported that dragging the affected dialog window to the other monitor in the dual-monitor display will resolve any observed issues.
Status become editable when a test designer converts a manual script to any other type
Issue: The Status field of a test case will become editable if a test designer converts a manual test to an automated test.
Impact: This issue is related to the Generate Script feature of ALM.
Workaround: Manual process controls must be implemented when using this feature.