ID | Title | Function Name | Test Steps | Expected Result | Actual Result |
vsg_1 | Verify Ping to all vsg vms success | test_vsg_health | 1. Login to compute node 2. Ping to all vSG VMs | All the vSGs should be reachable |
|
vsg_2 | Verify Ping to specific vSG VM | test_vsg_health_check | 1. Login to compute node 2. Ping to specified vSG VM | vSG should be reachable |
|
vsg_3 | Verify at least one vSG vm and compute node combination exists in setup | test_vsg_for_vcpe |
| At least one compute node and one vSG VM should exists |
|
vsg_4 | Verify accessing to vSG VM | test_vsg_for_login | 1. Login to compute node VM 2. Get all vSGs 3. Verifying login to vSG is success
| Login to vSG VM should success |
|
vsg_5 | Verify default route exists in test client to vcpe instance | test_vsg_for_default_route_through_testclient | 1.Login to head node 2.Get default route output on test client | A default route should exist in test client |
|
vsg_6 | Verify external connectivity via vcpe container from test client | test_vsg_for_external_connectivity_through_testclient |
| External network should be reachable from test client |
|
vsg_7 | Verify external connectivity via vcpe instance from cord-tester | test_vsg_for_external_connectivity |
| Should be able to reach external network from cord-tester via vcpe instance |
|
vsg_8 | Verify external connectivity to google from cord-tester via vcpe instance | test_vsg_for_external_connectivity_to_google | 1. Get dhcp IP to vcpe interface 2. Ping to google | Should be able to reach external network from cord-tester via vcpe instance |
|
vsg_9 | Validate path mtu to google from cord-tester | test_vsg_to_retrieve_content_from_google_to_validate_path_mtu |
| Path mtu should be validated |
|
vsg_10 | Validate path mtu to rediff from cord-tester | test_vsg_to_retrieve_content_from_rediff_to_validate_path_mtu | 1. Get dhcp IP to vcpe interface 2. Get rediff page contents 3. Validate path mtu | Path mtu should be validated |
|
vsg_11 | Validate path mtu to yahoo from cord-tester | test_vsg_to_retrieve_content_from_yahoo_to_validate_path_mtu | 1. Get dhcp IP to vcpe interface 2. Get yahoo page contents 3. Validate path mtu | Path mtu should be validated |
|
vsg_12 | Validate path mtu to facebook from cord-tester | test_vsg_to_retrieve_content_from_facebook_to_validate_path_mtu | 1. Get dhcp IP to vcpe interface 2. Get facebook page contents 3. Validate path mtu | Path mtu should be validated |
|
vsg_13 | Verify external connectivity for invalid host from cord-tester via vcpe instance | test_vsg_for_external_connectivity_to_invalid_host |
| Ping to invalid external host should be failed |
|
vsg_14 | Verify external connectivity with ttl 1 from cord-tester via vcpe instance | test_vsg_for_external_connectivity_with_ttl_1 |
| Ping to external should be failed |
|
vsg_15 | Verify external connectivity from cord-tester withj vcpe instance wan interface toggle | test_vsg_for_external_connectivity_with_wan_interface_toggle_in_vcpe |
| Should be able to ping to external even after interface toggle |
|
vsg_16 | Verify external connectivity from cord-tester withj vcpe instance lan interface toggle | test_vsg_for_external_connectivity_with_lan_interface_toggle_in_vcpe |
| Should be able to ping to external even after interface toggle |
|
vsg_17 | Verify simulating multiple subscribers for same vcpe instance form cord-tester | test_vsg_multiple_subscribers_for_same_vcpe_instace |
| All the subscribe should get dhcp IP |
|
vsg_18 | Verify external connectivity from multiple subscribers of same vcpe instance from cord-tester | test_vsg_for_multiple_subscribers_with_same_vcpe_instance_and_validate_external_connectivity |
| Should be able to reach external network for all subscribers |
|
vsg_19 | Verify subscriber gets dhcp ip after vcpe interface toggles in cord-tester | test_vsg_vcpe_interface_and_validate_dhcp_ip_after_interface_toggle |
| Vcpe Interface should get dhcp IP even after toggle |
|
vsg_20 | Verify external connectivity from cord-tester via vcpe instance after the instance restart | test_vsg_for_external_connectivity_after_restarting_vcpe_instance |
| Should be able to reach external network even after vcpe restart |
|
vsg_21 | Verify external connectivity from cord-tester via vcpe instance after the vSG VM restart | test_vsg_for_external_connectivity_after_restarting_vsg_vm | 1. Get dhcp ip to vcpe interface 2. Ping to external network 3. Restart vSG VM and ping again to external | Should be able to reach external network even after vSG restart |
|
vsg_22 | Verify external connectivity from cord-tester via vcpe instance after the instance paused | test_vsg_for_external_connectivity_with_vcpe_container_paused | 1. Get dhcp ip to vcpe interface 2. Ping to external network 3. Pause vcpe instance and ping again to external | Should be able to reach external network even after vcpe paused |
|
Vsg_firewall_23 | Verify vcpe firewall functionality to deny destination IP | test_vsg_firewall_with_deny_destination_ip |
| Ping to destination IP should fail after adding the rule |
|
vsg_firewall_24 | Verify vcpe firewall functionality to deny destination IP with rule add and delete | test_vsg_firewall_with_rule_add_and_delete_dest_ip | 1. Get dhcp ip to vcpe interface 2. Configure a static route via vcpe interface 3. Add a deny dest ip firewall rule in vcpe instance 4. Ping to destination IP 5. Delete the rule and ping again | Ping to destination IP should fail after adding the rule and delete |
|
vsg_firewall_25 | Verify non-denied IP address can be reachable from cord-tester | test_vsg_firewall_verifying_reachability_for_non_blocked_dest_ip | 1. Get dhcp ip to vcpe interface 2. Configure a static route via vcpe interface 3. Add a deny dest ip firewall rule in vcpe instance 4. Ping to destination IP 5. Ping to non-denied IP | Ping to non-blocked IP should success |
|
vsg_firewall_26 | Verify appending firewall rule in vcpe instance | test_vsg_firewall_appending_rules_with_deny_dest_ip | 1. Get dhcp ip to vcpe interface 2. Configure a firewall rule 3. Append one more rule | Appending firewall rule should get success |
|
vsg_firewall_27 | Verify removing one firewall rule wont impact on remaining rules | test_vsg_firewall_removing_one_rule_denying_dest_ip |
| Removing firewall rule should get success |
|
vsg_firewall_28 | Verify changing firewall rule id wont change functionality | test_vsg_firewall_changing_rule_id_deny_dest_ip |
| Changing firewall rule should get success |
|
vsg_firewall_29 | Verify changing firewall rule action from deny to accept | test_vsg_firewall_changing_deny_rule_to_accept_dest_ip | 1 Get dhcp ip to vcpe interface 2 . Configure deny firewall rule 3. Change the rule to accept | Changing firewall rule should get success |
|
vsg_firewall_30 | Verify firewall rule to deny destination network | test_vsg_firewall_denying_destination_network | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny dest network | Firewall rule should success
|
|
vsg_firewall_31 | Verify firewall rule to deny destination network with subnet modification | test_vsg_firewall_denying_destination_network_subnet_modification | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny dest network 3. Change dest network in firewall rule | Subnet modification in firewall rule should success |
|
vsg_firewall_32 | Verify firewall to deny source IP | test_vsg_firewall_with_deny_source_ip |
| Firewall to deny source IP should be success |
|
vsg_firewall_33 | Verify firewall to deny source IP with rule add and deleted | test_vsg_firewall_rule_with_add_and_delete_deny_source_ip | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny source IP 3. Delete the rule | Deleting a firewall rule should success |
|
vsg_firewall_34 | Verify firewall rule to deny icmp requests type packets | test_vsg_firewall_rule_with_deny_icmp_protocol_echo_requests_type | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny icmp requests messages | Firewall to deny icmp should be success |
|
vsg_firewall_35 | Verify firewall rule to deny icmp reply type packets | test_vsg_firewall_rule_with_deny_icmp_protocol_echo_reply_type | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny icmp reply messages | Firewall to deny icmp should be success |
|
vsg_firewall_36 | Verify firewall rule to change deny rule accept icmp requests type packets | test_vsg_firewall_changing_deny_rule_to_accept_rule_with_icmp_protocol_echo_requests_type | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny icmp requests messages 3. Change the rule to accept | Firewall to deny icmp should be success |
|
vsg_firewall_37 | Verify firewall rule to change deny rule accept icmp reply type packets | test_vsg_firewall_changing_deny_rule_to_accept_rule_with_icmp_protocol_echo_reply_type | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny icmp reply messages 3. Change the rule to accept | Changing firewall rule should get success |
|
vsg_firewall_38 | Verify firewall rule to deny icmp protocol | test_vsg_firewall_for_deny_icmp_protocol | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny icmp protocol | Firewall to deny icmp should be success |
|
vsg_firewall_39 | Verify firewall rule to deny both icmp protocol and destination IP | test_vsg_firewall_rule_deny_icmp_protocol_and_destination_ip | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny icmp protocol and dest IP | Firewall to deny icmp should be success |
|
vsg_firewall_40 | Verify flushing all configured firewall rules | test_vsg_firewall_flushing_all_configured_rules | 1. Get dhcp ip to vcpe interface 2. Configure firewall rules 3. Flush all the rules | All the rules should get deleted after flush |
|
vsg_firewall_41 | Verify firewall rule to deny all IPv4 traffic | test_vsg_firewall_deny_all_ipv4_traffic | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny IPv4 traffic | All the IPv4 traffic should be blocked |
|
vsg_firewall_42 | Verify replacing deny firewall with accept | test_vsg_firewall_replacing_deny_rule_to_accept_rule_ipv4_traffic | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny IPv4 traffic 3. Change the rule to accept | Replacing a rule should get success |
|
vsg_firewall_43 | Verify denying all the traffic coming lan interface on vcpe instance | test_vsg_firewall_deny_all_traffic_coming_on_lan_interface_in_vcpe | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny lan traffic
| All the traffic on lan interface should be dropped |
|
vsg_firewall_44 | Verify denying all the traffic going out on wan interface on vcpe instance | test_vsg_firewall_deny_all_traffic_going_out_of_wan_interface_in_vcpe | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny wan traffic | All the traffic on wan interface should be dropped |
|
vsg_firewall_45 | Verify denying all the traffic flow from lan to wan interface in vcpe instance | test_vsg_firewall_deny_all_traffic_from_lan_to_wan_in_vcpe | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny lan to wan traffic | All the traffic from lan to wan interface should be dropped |
|
vsg_firewall_46 | Verify denying all dns traffic via vcpe instance | test_vsg_firewall_deny_all_dns_traffic | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny dns traffic | All the DNS traffic should be dropped |
|
vsg_firewall_47 | Verify deny all IPv4 traffic with vcpe restart | test_vsg_firewall_deny_all_ipv4_traffic_vcpe_container_restart | 1. Get dhcp ip to vcpe interface 2. Configure firewall rule to deny icmp requests messages 3. Restart vcpe container | After vcpe restart ping to external should work |
|
vsg_nat_48 | Verify vsg nat with modifying destination IP address | test_vsg_nat_dnat_modifying_destination_ip | 1. Get dhcp ip to vcpe interface 2. Configure DNAT rule | DNAT rule should be able to configured |
|
vsg_nat_49 | Verify vsg nat with modifying destination IP address and delete the rule | test_vsg_nat_dnat_modifying_destination_ip_and_delete | 1. Get dhcp ip to vcpe interface 2. Configure DNAT rule 3. Delete the rule | DNAT rule should be able to configured and delete |
|
vsg_nat_50 | Verify vsg nat with modifying destination IP address with modifying the address | test_vsg_nat_dnat_change_modifying_destination_ip_address | 1. Get dhcp ip to vcpe interface 2. Configure DNAT rule 3. Modify the destination IP in the rule | DNAT rule should be able to modify destination IP configured |
|
vsg_xos_subscriber_51 | Verify creating default vcpe instance | test_vsg_xos_subscriber_create_reserved | 1. Create default vcpe in default vSG VM | Default vcpe creation should be success |
|
vsg_xos_subscriber_52 | Verify creating vcpe instance for interfaces created in cord-tester | test_vsg_xos_subscriber_create_all | 1. Create vcpes using XOS for interfaces created in cord-tester | Vcpes corresponding to interfaces created in cord-tester should be created |
|
vsg_xos_subscriber_53 | Verify deleting vcpe instance for interfaces created in cord-tester | test_vsg_xos_subscriber_delete_all | 2. Delete vcpes using XOS for interfaces created in cord-tester | All vcpes should be cleared |
|
vsg_xos_subscriber_54 | Verify creating vcpe instance for 1st interface created in cord-tester | test_vsg_xos_subscriber_create_and_delete | 1. Create vpce for 1st interface in cord-tester using XOS | Should be able to create and delete vcpe by XOS |
|
vsg_xos_subscriber_55 | Verify creating vcpe instance for 2nd interface created in cord-tester | test_vsg_xos_subscriber_2_create_and_delete | Create vpce for 2nd interface in cord-tester using XOS | Should be able to create and delete vcpe by XOS |
|
vsg_xos_subscriber_56 | Verify creating vcpe instance for 3rd interface created in cord-tester | test_vsg_xos_subscriber_3_create_and_delete | Create vpce for 3rd interface in cord-tester using XOS | Should be able to create and delete vcpe by XOS |
|
vsg_xos_subscriber_57 | Verify creating vcpe instance for 4th interface created in cord-tester | test_vsg_xos_subscriber_4_create_and_delete | Create vpce for 4th interface in cord-tester using XOS | Should be able to create and delete vcpe by XOS |
|
vsg_xos_subscriber_58 | Verify creating vcpe instance for 5th interface created in cord-tester | test_vsg_xos_subscriber_5_create_and_delete | Create vpce for 5th interface in cord-tester using XOS | Should be able to create and delete vcpe by XOS |
|
vsg_xos_subscriber_59 | Verify external connectivity from cord-tester via vcpe created by XOS | test_vsg_xos_subscriber_external_connectivity_through_vcpe_instance |
| External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_60 | Verify external connectivity from cord-tester via vcpe without created by XOS | test_vsg_xos_subscriber_external_connectivity_without_creating_vcpe_instance | 1. Do not Create vpce for interface in cord-tester using XOS 2. Ping to external network from the interface | External connectivity via XOS created vcpe should not be success |
|
vsg_xos_subscriber_61 | Verify external connectivity from cord-tester via vcpe after created and removed by XOS | test_vsg_xos_subscriber_external_connectivity_after_remove_vcpe_instance_from_xos | 1. Create vpce for interface in cord-tester using XOS 2. Ping to external network from the interface 3. Remove the vcpe instance and ping again | External connectivity via XOS created vcpe should not be success |
|
vsg_xos_subscriber_62 | Verify external connectivity from cord-tester via vcpe after restarting vcpe created by XOS | test_vsg_xos_subscriber_external_connectivity_after_restart_vcpe_instance | 1. Create vpce for interface in cord-tester using XOS 2. Ping to external network from the interface 3. Restart the vcpe instance and ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_63 | Verify external connectivity from cord-tester via vcpe after stop and start the vcpe created by XOS | test_vsg_xos_subscriber_external_connectivity_after_stop_and_start_vcpe_instance | 1. Create vpce for interface in cord-tester using XOS 2. Ping to external network from the interface 3. Stop and start vcpe instance and ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_64 | Verify creating vcpes in different vSG VMs | test_vsg_create_xos_subscribers_in_different_vsg_vm | 1. Create vcpe instances in different vSG VMs | Should be able to create vcpe in different vSG VMs |
|
vsg_xos_subscriber_65 | Verify external connectivity from cord-tester via vcpe created by XOS if vcpe goes down | test_vsg_xos_multiple_subscribers_external_connectivity_if_one_vcpe_goes_down |
| External connectivity via active vcpe should be success |
|
vsg_xos_subscriber_66 | Verify external connectivity from cord-tester via vcpe created by XOS if vcpe removed and added back | test_vsg_xos_subscriber_external_connectivity_after_vcpe_remove_and_add_again | 1. Create two vcpe instances 2. Ping to external via both vcpes 3. Remove and add one vcpe 4. Ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_67 | Verify external connectivity from cord-tester via vcpe created by XOS if vcpe restarts | test_vsg_xos_multiple_subscribers_external_connectivity_if_one_vcpe_restarts | 1. Create two vcpe instances 2. Ping to external via both vcpes 3. Restart one vcpe 4. Ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_68 | Verify external connectivity from cord-tester via vcpe created by XOS if vcpe pauses | test_vsg_xos_multiple_subscribers_external_connectivity_if_one_vcpe_pause | 1. Create two vcpe instances 2. Ping to external via both vcpes 3. pause one vcpe 4. Ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_69 | Verify external connectivity from cord-tester via vcpe created by XOS if vcpe stops | test_vsg_xos_subscriber_external_connectivity_if_one_vcpe_stops | 1. Create two vcpe instances 2. Ping to external via both vcpes 3. Stop one vcpe 4. Ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_70 | Verify external connectivity from cord-tester via vcpe created by XOS if vSG VM stops | test_vsg_xos_subscriber_external_connectivity_after_vsg_vm_stop | 1. Create two vcpe instances in different vSG VMs 2. Ping to external via both vcpes 3. Stop one vSG VM 4. Ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_71 | Verify external connectivity from cord-tester via vcpe created by XOS if vSG VM restarts | test_vsg_xos_subscriber_external_connectivity_after_vsg_vm_restart | Create two vcpe instances in different vSG VMs 2. Ping to external via both vcpes 3. Restart one vSG VM 4. Ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_72 | Verify external connectivity from cord-tester via vcpe created by XOS if vSG VM stops and starts | test_vsg_xos_multiple_subscribers_external_connectivity_if_two_vsgs_stop_and_start | 1. Create two vcpe instances in different vSG VMs 2. Ping to external via both vcpes 3. Stop two VMs and start 4. Ping again | External connectivity via XOS created vcpe should be success |
|
vsg_xos_subscriber_73 | Verify firewall functionality with XOS created vcpe | test_vsg_xos_subscriber_external_connectivity_with_creating_firewall_rule |
| Firewall functionality should work as per configured |