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

Improve image-updater unit test coverage

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • Improve image-updater unit test coverage
    • False
    • None
    • False
    • SECFLOWOTL-121 - Image Updater: Stabilize upstream project
    • 0% To Do, 0% In Progress, 100% Done
    • GitOps Tangerine - Sprint 3256

      Goal (Required)

      As a developer using image-updater, I expect a high level of quality and good unit test coverage.

      The current unit test coverage is around 55% as reported in Codecov Report in github actions CI run. We should aim for 80% unit test coverage.

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      This epic focuses on unit test coverage and so will not include e2e tests.

      Approach (Required)

      • look at the current state of unit test coverage, and come up with a test plan
      • start adding unit tests in pkgs with the lowest coverage, and gradually expand to cover all packages.

      Dependencies

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

      Acceptance Criteria (Mandatory)

      aim at unit test coverage of 80%;

      new unit tests are reviewed and merged into upstream image-updater project;

      all tests passing without any regression.

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: