Receive following error when submitting runs for approval: Index was out of range. Must be non-negative and less than the size of the collection, Parameter name: index

Receive following error when submitting runs for approval: Index was out of range. Must be non-negative and less than the size of the collection, Parameter name: index

If you receive this error please check the "Testers" (Not "Tester") and confirm:

1) That the "Testers" field is not populated

2) Username in "Testers" field is no longer assigned to the project.

If either one of these cases is true (Testers field is not populated or user is no longer assigned in the project) please follow the steps below as a workaround:

Description: When creating a new manual test run, sometimes the Testers field is not initialized and remains blank.

Impact: When the Testers field is blank, the tester(s) will not be prompted to provide a Tester signature when the run is routed for approval.

Workaround:

Scenario 1: When the issue is true, the run can be withdrawn from approval, the tester can select "Continue Manual Run", "Begin Run", and "End Run". This will add their ID to the Testers field, and they will be assigned an approval task the next time the run is routed for approval.

Scenario 2: ????When the issue is true, the run can be withdrawn from approval, a new user/tester can select "Continue Manual Run", "Begin Run", and "End Run". This will add the new ID to the Testers field, and they will be assigned an approval task the next time the run is routed for approval.


    • Related Articles

    • How to Prevent or Fix Dry Runs created in Ready for Execution Test Set

      Problem: Rarely, dry runs (i.e. runs with the Draft Run field set to Y) can be created in formal test sets. This is due to an ALM feature that automatically marks runs created from a "Checked Out" test case as Draft Run = Y.  Prevention/Mitigation: ...

    • Test Set - Dry Runs

      What are Dry Runs?  Test Set Designers can designate a Test Set for Dry Runs. Dry Run Test Sets will ONLY produce informal executions (Dry Run executions). Once a Test Set is put into Dry Run Status, there is no way to reverse the action. Dry Run ...

    • 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, ...

    • 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: 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 ...

    • 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 ...