diff options
Diffstat (limited to 'tests/func')
| -rw-r--r-- | tests/func/honeycomb/090_provider_backbone_bridge.robot | 95 |
1 files changed, 22 insertions, 73 deletions
diff --git a/tests/func/honeycomb/090_provider_backbone_bridge.robot b/tests/func/honeycomb/090_provider_backbone_bridge.robot index 65d5217eb8..16791e236b 100644 --- a/tests/func/honeycomb/090_provider_backbone_bridge.robot +++ b/tests/func/honeycomb/090_provider_backbone_bridge.robot @@ -15,6 +15,8 @@ | ${super_if}= | ${node['interfaces']['port1']['name']} *** Settings *** +| Resource | resources/libraries/robot/default.robot +| Resource | resources/libraries/robot/honeycomb/honeycomb.robot | Resource | resources/libraries/robot/honeycomb/provider_backbone_bridge.robot | Variables | resources/test_data/honeycomb/pbb/pbb.py | Documentation | *Honeycomb provider backbone bridge test suite.* @@ -23,111 +25,58 @@ | Force Tags | honeycomb_sanity *** Test Cases *** +# TODO: add verifications once operational data or VPP dump is available. | TC01: Honeycomb sets PBB sub-interface -| | [Documentation] | Honeycomb creates a new PBB sub-interface and checks its\ -| | ... | operational data. +| | [Documentation] | Honeycomb creates a new PBB sub-interface. | | ... -| | Given PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} -| | When Honeycomb creates PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_1_ID} | ${cfg_pbb_sub_if_1} -| | Then PBB sub interface operational data from Honeycomb should be -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} | ${oper_pbb_sub_if_1} +| | Honeycomb creates PBB sub interface | ${node} | ${super_if} +| | ... | ${cfg_pbb_sub_if_1} | TC02: Honeycomb modifies existing PBB sub-interface -| | [Documentation] | Honeycomb modifies an existing PBB sub-interface and\ -| | ... | checks its operational data. +| | [Documentation] | Honeycomb modifies an existing PBB sub-interface. | | ... -| | Given PBB sub interface operational data from Honeycomb should be -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} | ${oper_pbb_sub_if_1} -| | When Honeycomb creates PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_1_ID} | ${cfg_pbb_sub_if_1_mod} -| | Then PBB sub interface operational data from Honeycomb should be -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} -| | ... | ${oper_pbb_sub_if_1_mod} +| | Honeycomb creates PBB sub interface | ${node} | ${super_if} +| | ... | ${cfg_pbb_sub_if_1_mod} | TC03: Honeycomb deletes existing PBB sub-interface -| | [Documentation] | Honeycomb deletes an existing PBB sub-interface and\ -| | ... | checks operational data. +| | [Documentation] | Honeycomb deletes an existing PBB sub-interface. | | ... -| | Given PBB sub interface operational data from Honeycomb should be -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} -| | ... | ${oper_pbb_sub_if_1_mod} -| | When Honeycomb Removes PBB sub interface -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} -| | Given PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} - -| TC04: Honeycomb creates two PBB sub-interface -| | [Documentation] | Honeycomb creates two PBB sub-interfaces on the same\ -| | ... | super interface and checks their operational data. -| | ... -| | Given PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_2_ID} -| | And PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_3_ID} -| | When Honeycomb creates PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_2_ID} | ${cfg_pbb_sub_if_2} -| | And Honeycomb creates PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_3_ID} | ${cfg_pbb_sub_if_3} -| | Then PBB sub interface operational data from Honeycomb should be -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_2_ID} | ${oper_pbb_sub_if_2} -| | And PBB sub interface operational data from Honeycomb should be -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_3_ID} | ${oper_pbb_sub_if_3} +| | Honeycomb Removes PBB sub interface +| | ... | ${node} | ${super_if} | TC05: Honeycomb fails to set wrong destination-address for new PBB sub-interface | | [Documentation] | Honeycomb fails to create a new PBB sub-interface with\ | | ... | wrong value of parameter destination-address, type yang:mac-address. | | ... -| | Given PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} -| | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_wrong_dst_addr} -| | Then PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} +| | Honeycomb fails to create PBB sub interface | ${node} | ${super_if} +| | ... | ${cfg_pbb_sub_if_wrong_dst_addr} | TC06: Honeycomb fails to set wrong source-address for new PBB sub-interface | | [Documentation] | Honeycomb fails to create a new PBB sub-interface with\ | | ... | wrong value of parameter source-address, type yang:mac-address. | | ... -| | Given PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} -| | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_wrong_src_addr} -| | Then PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} +| | Honeycomb fails to create PBB sub interface | ${node} | ${super_if} +| | ... | ${cfg_pbb_sub_if_wrong_src_addr} | TC07: Honeycomb fails to set wrong b-vlan-tag-vlan-id for new PBB sub-interface | | [Documentation] | Honeycomb fails to create a new PBB sub-interface with\ | | ... | wrong value of parameter b-vlan-tag-vlan-id, type uint16, 12 bit\ | | ... | range, range "1..4095". | | ... -| | Given PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} -| | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_wrong_vlan_tag} -| | Then PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} +| | Honeycomb fails to create PBB sub interface | ${node} | ${super_if} +| | ... | ${cfg_pbb_sub_if_wrong_vlan_tag} | TC08: Honeycomb fails to set wrong i-tag-isid for new PBB sub-interface | | [Documentation] | Honeycomb fails to create a new PBB sub-interface with\ | | ... | wrong value of parameter i-tag-isid, type uint32, 24 bit range,\ | | ... | range "1..16777215". | | ... -| | Given PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} -| | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_wrong_i_tag} -| | Then PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} +| | Honeycomb fails to create PBB sub interface | ${node} | ${super_if} +| | ... | ${cfg_pbb_sub_if_wrong_i_tag} | TC07: Honeycomb fails to create new PBB sub-interface without vlan tag | | [Documentation] | Honeycomb fails to create a new PBB sub-interface without\ | | ... | parameter b-vlan-tag-vlan-id. | | ... -| | Given PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} -| | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if} -| | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_no_vlan_tag} -| | Then PBB sub interface operational data from Honeycomb should be empty -| | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID} +| | Honeycomb fails to create PBB sub interface | ${node} | ${super_if} +| | ... | ${cfg_pbb_sub_if_no_vlan_tag} |