Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-8248

[Results CLI] Unit test improvements

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Tekton CLI
    • None
    • Results CLI - unit test improvements
    • False
    • Hide

      None

      Show
      None
    • False
    • In Progress
    • 40% To Do, 0% In Progress, 60% Done
    • Release Note Not Required

      Epic Goal

      • Goal is to improve unit tests for the Results CLI so that it is able to test multiple scenarios and does not mock the function, instead calls the actual function.

      Why is this important?

      1. Required as unit tests are critical part of code and testing the actual function help us to track the bugs early in the development cycle

      Scenarios

      1. ...

      Acceptance Criteria (Mandatory)

      • Should have unit tests covering all the commands and the functionalities
      • Unit tests should test actual functions not the mock functions

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              diagrawa Divyanshu Agrawal
              diagrawa Divyanshu Agrawal
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: