Story (Required)

As a GitOps Developer or QE trying to fix a default I want the CPaaS/Plumbing triggered est to execute the argocd e2e tests. When argocd e2e tests fail, releasing the built should be blocked. In other words, argocd e2e tests are gating.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer's experience?>

Background (Required)

This is a must have in order to fully automate testing for z-stream. Argocd e2e tests must be executed and it should not require human interaction.

<Describes the context or background related to this story>

The argocd e2e tests run successfully locally but there are failure when running in Plumbing Tekton pipeline tests.

Out of scope

<Defines what is not included in this story>

Approach (Required)

Include argocd e2e tests as part of the Plumbing triggered tests.

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

• Trouble shoot from the logs

• Determine the difference between running locally and in Plumbing

  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>

• Argocd e2e tests are included as part of the CPaaS/Plumbing triggered tests
• All Argocd e2e tests that run successfully by hand pass.

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

• Acceptance criteria are met