Epic Goal

• Automate OpenShift GitOps UI testing using a Go-based framework (ChromeDP). The goal is to replace minimal manual testing with a code-native automation suite that runs alongside our backend tests.

Why is this important?

• Speed: Eliminates manual UI verification during releases.
• Consistency: Uses Go for both backend and UI tests.
• Safety Net: Automatically detects broken pages or failed installs.

Scenarios

ChromeDP Smoke Tests)
Install: Verify the Operator installs successfully via the Console.

1. Login: Automate the SSO login flow and verify redirection.
2. Load: Ensure the Dashboard renders key elements (no white screens).
3. Sync: Verify a user can click "Sync" on an app and see the status change.

1. Other Considerations

• Tooling: ChromeDP (Go) running against Headless Chrome.

• Failure Handling: Must capture screenshots automatically when a test fails.

1. Definition of Ready

• The epic has been broken down into stories.
• Stories have been scoped.
• The epic has been stack ranked.

1. Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project.
• 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.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.