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

Only relevant tests should run on the MR

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • p12n
    • Pipelines Sprint 239, Pipelines Sprint 240, Pipelines Sprint 241, Pipelines Sprint 242, Pipelines Sprint 243, Pipelines Sprint 244, Pipelines Sprint 245, Pipelines Sprint 246, Pipelines Sprint 247, Pipelines Sprint 250, Pipelines Sprint 251, Pipelines Sprint 252, Pipelines Sprint 253, Pipelines Sprint 254

      Story (Required)

      Only relevant tests should run on the MR, now whenever we have a MR on pipelines-5.0-rhel-8 all tests mentioned in the pipelinerun will run.

      we need to run only relevant test, if there is a change in a component we need to run only component specific tests.

       

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

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

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      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

              rbehera-1 Rupali Behera
              rbehera-1 Rupali Behera
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - 4 minutes
                  4m
                  Remaining:
                  Remaining Estimate - 1 minute
                  1m
                  Logged:
                  Time Spent - Not Specified Time Not Required
                  Not Specified