Resilience

No.	Description	Test Case ID	PD	Topology
1	Verify Chaos Base configuration	test_deploy_verify_base_config	Yes
2	Verify Route Scaling time on syncd restart without traffic for 2K routes	test_chaos_route_scaling_time_syncd_2k	Yes
3	Verify Route Scaling time on syncd restart without traffic for 8K routes	test_chaos_route_scaling_time_syncd_8k	Yes
4	Verify Route Scaling time on syncd restart without traffic for 16K routes	test_chaos_route_scaling_time_syncd_16k	Yes
5	Verify Route Scaling time on syncd restart without traffic	test_chaos_route_scaling_time_syncd_32k	Yes
6	Verify Route Scaling time on syncd restart without traffic	test_chaos_route_scaling_time_syncd_64k	Yes
7	Verify Route Scaling time on FRR restart without traffic for 2K routes	test_chaos_route_scaling_time_frr_2k	Yes
8	Verify Route Scaling time on FRR restart without traffic for 8K routes	test_chaos_route_scaling_time_frr_8k	Yes
9	Verify Route Scaling time on FRR restart without traffic	test_chaos_route_scaling_time_frr_16k	Yes
10	Verify Route Scaling time on FRR restart without traffic	test_chaos_route_scaling_time_frr_32k	Yes
11	Verify Route Scaling time on FRR restart without traffic	test_chaos_route_scaling_time_frr_64k	Yes
12	Verfiy Route Scaling time on orchagent restart without traffic for 2k routes	test_chaos_route_scaling_time_orchagent_2k	Yes
13	Verfiy Route Scaling time on orchagent restart without traffic for 8k routes	test_chaos_route_scaling_time_orchagent_8k	Yes
14	Verfiy Route Scaling time on orchagent restart without traffic for 16k routes	test_chaos_route_scaling_time_orchagent_16k	Yes
15	Verify Route Scaling time on orchagent restart without traffic for 32k routes	test_chaos_route_scaling_time_orchagent_32k	Yes
16	Verify Route Scaling time on orchagent restart without traffic for 64k routes	test_chaos_route_scaling_time_orchagent_64k	Yes
17	Verify Route Scaling time on syncd restart with traffic for 2K routes	test_chaos_route_scaling_time_syncd_traffic_2k	Yes
18	Verify Route Scaling time on syncd restart with traffic for 8K routes	test_chaos_route_scaling_time_syncd_traffic_8k	Yes
19	Verify Route Scaling time on syncd restart with traffic for 16k routes	test_chaos_route_scaling_time_syncd_traffic_16k	Yes
20	Verify Route Scaling time on syncd restart with traffic for 32k routes	test_chaos_route_scaling_time_syncd_traffic_32k	Yes
21	Verify Route Scaling time on syncd restart with traffic for 64k routes	test_chaos_route_scaling_time_syncd_traffic_64k	Yes
22	Verify Route Scaling time on FRR restart with traffic for 2k routes	test_chaos_route_scaling_time_frr_traffic_2k	Yes
23	Verify Route Scaling time on FRR restart with traffic for 8k routes	test_chaos_route_scaling_time_frr_traffic_8k	Yes
24	Verify Route Scaling time on FRR restart with traffic for 16k routes	test_chaos_route_scaling_time_frr_traffic_16k	Yes
25	Verify Route Scaling time on FRR restart with traffic for 32k routes	test_chaos_route_scaling_time_frr_traffic_32	Yes
26	Verify Route Scaling time on FRR restart with traffic for 64k routes	test_chaos_route_scaling_time_frr_traffic_64k	Yes
27	Verify Route Scaling time on orchagent restart with traffic with 2k routes	test_chaos_route_scaling_time_orchagent_traffic_2k	Yes
28	Verify Route Scaling time on orchagent restart with traffic with 8k routes	test_chaos_route_scaling_time_orchagent_traffic_8k	Yes
29	Verify Route Scaling time on orchagent restart with traffic with 16k routes	test_chaos_route_scaling_time_orchagent_traffic_16k	Yes
30	Verify Route Scaling time on orchagent restart with traffic with 32k routes	test_chaos_route_scaling_time_orchagent_traffic_32k	Yes
31	Verify Route Scaling time on orchagent restart with traffic	test_chaos_route_scaling_time_orchagent_traffic_64k	Yes
32	Verify Spine failure and re-insertion impact with 2K routes.	test_deploy_spine_failure_insertion_impact_2k	Yes
33	Verify Spine failure and re-insertion impact with 8K routes.	test_deploy_spine_failure_insertion_impact_8k	Yes
34	Verify Spine failure and re-insertion impact with 16K routes.	test_deploy_spine_failure_insertion_impact_16k	Yes
35	Verify Spine failure and re-insertion impact with 32K routes.	test_deploy_spine_failure_insertion_impact_32k	Yes
36	Verify Spine failure and re-insertion impact with 64K routes.	test_deploy_spine_failure_insertion_impact_64k	Yes
37	Verify Link failure: LEAF-SPINE with 2K routes	test_deploy_spine_failure_link_impact_2k	Yes
38	Verify Link failure: LEAF-SPINE with 8K routes	test_deploy_spine_failure_link_impact_8k	Yes
39	Verify Link failure: LEAF-SPINE with 16K routes	test_deploy_spine_failure_link_impact_16k	Yes
40	Verify Link failure: LEAF-SPINE with 32K Routes	test_deploy_spine_failure_link_impact_32k	Yes
41	Verify Link failure: LEAF-SPINE with 64K routes	test_deploy_spine_failure_link_impact_64k	Yes
42	Verify stabilty with Continuous DUT reboot	test_chaos_continuous_reboot	Yes
43	Verify Continuous Route push and withdrawal with traffic for 2K routes	test_deploy_longevity_2k	Yes
44	Verify Continuous Route push and withdrawal with traffic for 8K routes	test_deploy_longevity_8k	Yes
45	Verify Continuous Route push and withdrawal with traffic for 16K routes	test_deploy_longevity_16k	Yes
46	Verify Continuous Route push and withdrawal with traffic for 32K routes	test_deploy_longevity_32k	Yes
47	Verify Continuous Route push and withdrawal with traffic for 64K routes	test_deploy_longevity_64k	Yes
48	Verify Warm Reboot - Device configuration impact with 2K routes	test_deploy_spine_warmreboot_impact_2k	Yes
49	Verify Warm Reboot - Device configuration impact with 8K routes	test_deploy_spine_warmreboot_impact_8k	Yes
50	Verify Warm Reboot - Device configuration impact with 16K routes	test_deploy_spine_warmreboot_impact_16k	Yes
51	Verify Warm Reboot - Device configuration impact with 32K routes	test_deploy_spine_warmreboot_impact_32k	Yes
52	Verify Warm Reboot - Device configuration impact with 64K routes	test_deploy_spine_warmreboot_impact_64k	Yes
53	Verify Stability with high Kernel CPU and observe its impact on the docker containers	test_chaos_high_kernel_cpu_utilization	Yes
54	Verify Routed PCH with 2k routes	test_deploy_impact_lacp_unconfig_2k	Yes
55	Verify Routed PCH with 8k routes	test_deploy_impact_lacp_unconfig_8k	Yes
56	Verify Routed PCH with 16k routes	test_deploy_impact_lacp_unconfig_16k	Yes
57	Verify Routed PCH with 32k routes	test_deploy_impact_lacp_unconfig_32k	Yes
58	Verify Routed PCH with 64k routes	test_deploy_impact_lacp_unconfig_64k	Yes

PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.