Story (Required)

• 
  Set up the chosen testing framework with proper configuration, directory structure, and initial test utilities/helpers for the GitOps Console Plugin. Implement fixture pattern for test data (inspired by gitops-operator). Focus on creating a foundation for basic, reliable tests.

Background and Approach (Required)

• 
  Install and configure testing framework (based on spike recommendation), create test directory structure (e.g., `cypress/` or equivalent), set up test configuration files, create test utilities and helpers for common operations, set up test data fixtures/mocks using fixture pattern (create reusable fixtures for Application, Rollout, ApplicationSet resources - JSON/YAML format), configure test environment setup/teardown (support both mock and real cluster modes), configure authentication handling (mock mode: no auth needed, real cluster mode: support kubeconfig/service accounts), and add test scripts to package.json.

Out of Scope

• <Defines what is not included in this story.>

Dependencies

•  Spike: GITOPS-8541

Acceptance Criteria (Mandatory)

• Testing framework installed and configured
• Test directory structure follows best practices
• Test utilities/helpers created for common operations (e.g., login, navigation)
• Test fixtures created for common resources (Application, Rollout, ApplicationSet)
• Test environment supports both mock and real cluster modes
• Authentication handling configured for both modes
• Test scripts added to package.json 
• Documentation for running tests added to README (including how to switch between mock and cluster modes)

  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.