Describe what should be investigated or refactored
We need to implement journey testing for our applications so that we can have assurance that things are still functional when changes are made to our applications. For SonarQube we should test the following to ensure our integrations are working:
This should be laid out in a way we can port similar naming conventions / patterns to Mattermost and GitLab as well. Once this ticket is completed, similar tickets with more specifics should be created in GitLab's and Mattermost's repos.
Describe what should be investigated or refactored
We need to implement journey testing for our applications so that we can have assurance that things are still functional when changes are made to our applications. For SonarQube we should test the following to ensure our integrations are working:
Links to any relevant code
This imported task will likely be useful for setup: https://github.com/defenseunicorns/uds-common/blob/b2e8b25930c953ef893e7c787fe350f0d8679ee2/tasks/setup.yaml#L33 We should follow the pattern (folder / structure wise) here, but use Playwright or Cypress instead of jest to test the webui (@BillyFigueroa has some context on this and would be good to sync with) https://github.com/defenseunicorns/uds-package-gitlab-runner/tree/main/test
Additional context
This should be laid out in a way we can port similar naming conventions / patterns to Mattermost and GitLab as well. Once this ticket is completed, similar tickets with more specifics should be created in GitLab's and Mattermost's repos.