Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-8546

Application Details Page Tests

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 8
    • False
    • Hide

      None

      Show
      None
    • False

      Story (Required)


      • Create functional verification tests for the Application Details Page, including Overview and Deployment History tabs.

      Background and Approach (Required)


      • Create tests for: Application details page loads correctly, Overview tab displays application information, Deployment History tab displays deployment history, tab navigation works correctly, application status displays correctly, resource information displays correctly, external links (ArgoCD) work correctly (if applicable), and empty states display correctly. Use test fixtures for Application resources and related data.

      Out of Scope

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

      Dependencies

      • <Describes what this story depends on. Dependent stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      • Test file created for Application Details Page
      • Test fixtures used for Application and related resources
      • Overview tab tests pass
      • Deployment History tab tests pass
      • Tab navigation tests pass
      • All test scenarios pass reliably in both mock and real cluster modes
      • Tests handle various application states
        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.

              rh-ee-atali Atif Ali
              rh-ee-atali Atif Ali
              Tangerine
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: