Use CI job to iterate test report JSON to generate list of test cases executed and their results

Related to https://gitlab.com/gitlab-org/quality/team-tasks/issues/187

Should we just add one more job in our QA pipelines to parse the JUnit Test Report JSON and create/update the issues in this repo?

Or should this be a standalone job running periodically?

I think running them as part of the pipeline is a better choice - We need to be careful not to keep any upstream job (if any) waiting for too long.

• Updated the related issue in the matching Project through our API gitlab-org/gitlab-qa!397 (merged)
  • Uniquely identify testcases by filename and full test name
  • Each issue represents one example (i.e., an it block. Therefore one spec file might have multiple issues)
• Automatically label issues with context::result labels to have them displayed in our issue boards
• Update the master, nightly, and staging/canary/prod pipelines
  • Nightly https://gitlab.com/gitlab-org/quality/nightly/-/merge_requests/53
  • Staging/canary/prod gitlab-org/quality/pipeline-common!38 (merged)
  • The jobs for master are actually in gitlab-qa, but so are the jobs for MRs, which we don't want to report. So the configuration will be a little tricky. gitlab-org/gitlab-qa!401 (merged)
• Add an API access token as GITLAB_QA_PRODUCTION_ACCESS_TOKEN to the quality group settings. The token is also saved in 1Password under the gitlab-qa user for gitlab.com under the label gitlab.com api token for test reporting reporting-tests-in-issues
• Switch from reporting in my personal project to https://gitlab.com/gitlab-org/quality/testcases/ after confirming that issues are created as expected.
  • Nightly: https://gitlab.com/gitlab-org/quality/nightly/-/merge_requests/54
  • pipeline-common: gitlab-org/quality/pipeline-common!39 (merged)