Gaps in ALM Run ID sequence

Gaps in ALM Run ID sequence

Problem

Runs appear to be deleted in a VERA configured ALM project.  Here are known ways that runs appear to be deleted:

  1. A user opens a test in ALM.  When a run is started, the Run is created in the database.  If at any time, including if the user passes all steps, the user closes the manual runner by clicking the window x button, the user will be prompted and asked if they want to save the run.  If the user clicks "No", ALM executes a cleanup function that deletes the run in the database and all data associated with the run is lost.  Furthermore, it is possible for  a user in a separate session to route a run for approval that is still open in the manual runner.  If the manual runner is closed without saving, the routed run will be lost from the ALM clean up function.  This phenomenon can also occur if the ALM session crashes while the manual runner is open. While ALM is very customizable, MicroFocus does not provide a way to prevent this from happening.
  2. The Standard VERA template allows for deletion of dry runs.
  3. VERA users think data is lost when there are gaps in RUN ID sequence.

Solution

  1. Testers should be instructed to always use the "End Run" button to exit the manual runner.  They should never use the x window to exit the manual runner.
  2. Testers should be instructed to only have one ALM session connected to a project at a time.
  3. Testers should be instructed to not execute tests through the manual runner using screen share in meeting applications
  4. Test designers should be instructed to try to minimize the number of steps in a test.  Testers should be instructed to end the run after executing the first step, followed by continuing the run if the test has a large number of steps.
    • Related Articles

    • VERA for ALM 2.7 released!

      Today, we are very pleased to announce the latest version of VERA for ALM. The following improvements were made: Customer’s VERA configuration can be updated to allow Test Administrators to correct Test Runs that failed to copy the values of GxP, ...
    • VERA for ALM 2.8 Released!

      Today we are pleased to announce the latest version of VERA for ALM. The following improvements were made: Customer’s VERA configuration can updated to send approval task notifications to approval groups Customer’s VERA configuration can be updated ...
    • VERA for ALM 2.9 Released!

      Today we are pleased to announce the latest version of VERA for ALM. The following improvements were made: Administrator Reassign Task improvements Vera provides a context sensitive list of users to choose instead of having to select a user from the ...
    • VERA for ALM 2.10 Released!

      We are very pleased to announce the latest version of VERA for ALM.  The following improvements were made: We added some new configuration options that can be added to your template: Ability to Prevent Step Execution if evidence is required Support ...
    • VERA for ALM 2.3 Released!

      Today, we are very pleased to announce the latest version of VERA. This VERA 2.3 release supports an integration with Tricentis Tosca for Pre Execution Review and Approval of Tosca Test with VERA in ALM Control Tests in Tosca Trigger Tosca Test ...