Purpose of Epic

• <Mandatory> <KR1> Identify additional features and test cases within CNV domain and initiate work on them.
• <Mandatory> <KR1> Propose the inclusion of a chaos component or label for bugs reported during Chaos testing to enhance visibility of efforts in this area.
• <Mandatory><KR2> Incorporate Chaos testing into the Release checklist for both Y stream and Z streams.
• <Mandatory> <KR2>Consider making Chaos testing mandatory/blocker for Y stream and optional/non-blocker for Z streams, and also for sprintly builds.
• <Spike><Optional><KR3> Determine the necessary tools and processes required for Chaos testing, including bug reporting procedures.
• <Spike><Optional> <KR3>Conduct research on the Chaos framework, specifically krknChaos.