GitOps 1.6.7 Release Test Execution

Epic Goal

• Track the test execution effort for the 1.6.7 release test plan

Why is this important?

• Will provide evidence of test coverage and measure total effort

Scenarios

1. https://docs.google.com/spreadsheets/d/1FS6JKFyomjeyx7LE7ne1sM5GxSvCkGKbW8ArnNbj5r8

Acceptance Criteria

• Stories for each permutation to be covered will be created and linked to this story.
• Each story have sizing points
• Each story will be linked to this epic

Done Checklist

Any Gaps will be listed in

• Al stories are set to done.
• Any gaps will be listed in the "Details and Support matrix" tab of the Release 1.6.7, 1.7.4 spreedsheet

Epic Goal

• To test GitOps 1.6.7 before releasing it to the market.

Why is this important?

• We need to validate the release to ensure the quality of the shipped software.

Scenarios

1. OCP regular on AWS/GCP/PSI.

Acceptance Criteria (Mandatory)

• The release candidate for 1.6.7 has been properly validated.
• QE team agrees to the release and is confident about that.

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)