Story (Required)

The point of the story is to make sure that the test namespace is clened after each acceptance testing scenario is finished. The benefits of this feature would be:

• to save resources
• to ensure no inter-scenario dependencies or interferences
• to ensure repeatability of the scenarios execution - every scenario starts with a clean namespace
• to ensure that we can run any sub-set of the scenarios in any order
• to ensure any new scenarios would not unintentionally affect the existing scenarios

Background (Required)

Currently all the acceptance testsing scenarios are executed in sequence each introducing couple resources to the test namespace. That might lead to a situation (especially in case of constrained environments such as GitHub Workflow nodes) where all the resources occupying the namespace spend the available node resources (memory) before all the scenarios are executed preventing the rest of the scenarios to run and ultimatelly failing the remaining scenarios. Additionally, some of the scenarios might implicitely and unintentionally depend on a state of the cluster left by the run of some of the previous scenario which introduces unintentional inter-scenario dependency that might cause the scenario to fail, if executed standalone or as part of the scenario sub-set executed in a different order etc.

Glossary

<List of new terms and definition used in this story>

Out of scope

<Defines what is not included in this story>

In Scope

<Defines what is 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.>

Edge Case

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

Acceptance Criteria

The acceptance testing framework is capable of cleaning the test namespace after each scenario is finished
The cleaning of the test namespace is configurable and enabled by default
The cleaning of the test namespace is skipped when scenario fails

INVEST Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Legend

Unknown
Verified
Unsatisfied