-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
3
-
False
-
-
False
-
-
-
GitOps Scarlet Sprint 27
Story (Required)
Background and Approach (Required)
- We added 'behavioural' E2E tests to argocd-operator repo as part of https://issues.redhat.com/browse/GITOPS-8163
For this issue we just want to port those same tests so they ALSO run as part of gitops-operator E2E tests.
Acceptance Criteria (Mandatory)
- Port Argo CD Agent tests from argocd-operator E2E to gitops-operator
- There SHOULD be minimal changes required between the two.
- You may find it easier to use 'meld'/'beyond compare' or similar tool to copy changes between the two repos.
- I wrote up steps to do this, here: https://github.com/argoproj-labs/argocd-operator/tree/master/hack/sync-e2e-tests
- You don't need to follow these steps, you can also just do it manually if you want. (e.g. comparing what changed in each file)
- E2E tests passing on gitops-operator
Definition of Done
- Code Complete:
- All code has been written, reviewed, and approved.
- Tested:
- Unit tests have been written and passed.
- Ensure code coverage is not reduced with the changes.
- Integration tests have been automated.
- System tests have been conducted, and all critical bugs have been fixed.
- Tested and merged on OpenShift either upstream or downstream on a local build.
- Documentation:
- User documentation or release notes have been written (if applicable).
- Build:
- Code has been successfully built and integrated into the main repository / project.
- Midstream changes (if applicable) are done, reviewed, approved and merged.
- Review:
- Code has been peer-reviewed and meets coding standards.
- All acceptance criteria defined in the user story have been met.
- Tested by reviewer on OpenShift.
- Deployment:
- The feature has been deployed on OpenShift cluster for testing.