Prevent duplicate report entries on the Test Queue

[howard-e]

Address #1377

[ChrisC]

@howard-e I haven't pulled this down to test yet but looking over the code, it seems like this will just return an existing test plan run if one already exists for the matching AT version. Is that correct?

If so, I think it might be a more useful experience for the user if we block the process and instead let the user know that the test plan run for that version already exists, and that they can't add again.

It would also be great if there were smaller localized tests here, either at the service level on the server side or on the component side. (Looks like there's already some component tests with mocks here...)

[howard-e]

@howard-e I haven't pulled this down to test yet but looking over the code, it seems like this will just return an existing test plan run if one already exists for the matching AT version. Is that correct?

Correct

If so, I think it might be a more useful experience for the user if we block the process and instead let the user know that the test plan run for that version already exists, and that they can't add again.

Good thought! I can add this approach to the PR. Was initially thinking preventing on the gql layer is helpful to prevent any chance of it happening through a query (accidental or otherwise).

It would also be great if there were smaller localized tests here, either at the service level on the server side or on the component side. (Looks like there's already some component tests with mocks here...)

I can certainly expand those!

[ChrisC]

Good thought! I can add this approach to the PR. Was initially thinking preventing on the gql layer is helpful to prevent any chance of it happening through a query (accidental or otherwise).

I like that. It seems if we could prevent on the gql layer then maybe we could even prevent the AT version even showing up in the dropdown as an option to add to the test queue, if that version is already in the queue?