Add Test Plans to the Test Queue: Design creates inefficiencies and risk of data integrity errors by combining add and update capabilities

[mcking65]

This feature combines use cases that are fundamentally different from one another:

1. Add entries for test plan runs to the test queue for a draft test plan that has not been previously executed.
2. Update the version of test plan being used by existing entries in the test queue.
3. Add entries to the test queue in response to a new browser version.
4. Add entries to the test queue in response to a new AT release.

For use case 1, when adding for the first time, the admin needs to ensure that one or more entries are created in the test queue for each AT covered by the plan. The current design makes this difficult because:

1. The admin can't see which AT are in the plan. They must know this ahead of time.
2. The admin must repeat the operation separately for each AT, keeping track of which have already been added.

For use case 2, when updating the version of the test plan used by existing entries in the test queue, the admin needs to ensure that all existing entries in the queue are updated. The admin must keep track of which entries exist and which have been updated.

Responding to new browser and AT releases is something we will likely need to partially automate, and that could be in response to adding the new version numbers to the system.

It is likely the best way to resolve this issue is not to redesign the existing add experience but to instead add contextual actions to the appropriate places in the app and then sunset the current add experience. This will most likely be in the test plan summary table.

[stalgiag]

Hi @mcking65 - thank you for flagging this and I agree with your assessment.

I would like to make sure my reading of this is correct. My understanding is that the "risk of data integrity errors" mentioned in the title of this issue refers to the current UI's reliance on admins manually tracking which entries exist and which have been updated. The to-do for this issue is to do a round of UX Design to create new contextual actions for adding test plans to the test queue . Any data validation implementation needed to ensure integrity when adding test plans to the test queue will be tracked in other issues. Is my understanding correct?

tagging @ccanash for tracking.

[ccanash]

This was addressed with new changes to the test queue.