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

Argo CD Agent Chaos testing: propose high level implementation plan

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Argo CD Agent
    • None
    • GitOps Scarlet Sprint 18, GitOps Scarlet Sprint 19, GitOps Scarlet Sprint 20, GitOps Scarlet Sprint 21, GitOps Scarlet Sprint 22, GitOps Scarlet Sprint 23

      The goal of this story is to fill in final implementation details in our plan for this epic, before we start implementing them.

      This allows us to ensure that stakeholders agree on 'WHAT we are testing' and 'HOW we are testing it', before we actually implement it.

      As part of the parent epic, I have brainstormed some examples which can be the basis for this.

      Acceptance Criteria:

      • Create a google doc which:
        • Describes the specific proposed network/process conditions we will using chaos testing to test.
        • Describes the specific tools we will use to implement those.
        • Describes the changes we need to make to test/dev environment to enable those.
        • Describes any additional E2E tests that we need to implement.
      • Provide a link to Google doc to team on #gitops-dev Slack (and CC stakeholders) to gather review comments.
      • Once the contents of the google doc are approved, create child stories for epic.

              jpitman63 John Pitman
              jgwest Jonathan West
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: