search

defenseunicorns / uds-package-gitlab

🏭 UDS GitLab Zarf Package
Apache License 2.0
5 stars 3 forks source link

Add Journey Testing for GitLab #130

Closed Racer159 closed 1 month ago

Racer159 commented 1 month ago

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 GitLab we should test the following to ensure our integrations are working:

  1. Sign-in through SSO (Keycloak)
  2. Creating a repo (Database / Gitaly)
  3. Navigate to a file / api with %2F in the URL (Istio)
  4. Upload a file (Object Storage)

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

Additional context

This should be laid out in a way we can port similar naming conventions / patterns across our applications.

marshall007 commented 1 month ago

@Racer159 do you have an example of (3) Navigate to a file / api with %2F in the URL? I know I have seen that happen myself, but in poking around today I wasn't able to find a case where that happens.

Racer159 commented 1 month ago

Here is the issue we ran into: https://github.com/defenseunicorns/uds-core/issues/288 - I think the simplest is the namespace%2Fproject endpoints in the API