diff options
author | pmikus <pmikus@cisco.com> | 2016-08-26 09:48:22 +0100 |
---|---|---|
committer | Tibor Frank <tifrank@cisco.com> | 2016-10-03 06:41:59 +0000 |
commit | e87a07f056891f328b22e97f03f4c3ca5231d681 (patch) | |
tree | 3db7f54a97b99a6e6588de41ac9cc6c47894537a /tests/func/honeycomb | |
parent | 19c91adadd57bfc4e7514993b2a711a826d52e04 (diff) |
INMARSAT-54 Honeycomb configures PBB
- CRUD tests usinf Honeycomb REST API
Change-Id: I4885cd0feb26f8ef56beb0d8848772ea2d42cb3a
Signed-off-by: Tibor Frank <tifrank@cisco.com>
Diffstat (limited to 'tests/func/honeycomb')
-rw-r--r-- | tests/func/honeycomb/090_provider_backbone_bridge.robot | 133 |
1 files changed, 133 insertions, 0 deletions
diff --git a/tests/func/honeycomb/090_provider_backbone_bridge.robot b/tests/func/honeycomb/090_provider_backbone_bridge.robot new file mode 100644 index 0000000000..65d5217eb8 --- /dev/null +++ b/tests/func/honeycomb/090_provider_backbone_bridge.robot @@ -0,0 +1,133 @@ +# Copyright (c) 2016 Cisco and/or its affiliates. +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at: +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +*** Variables*** +| ${super_if}= | ${node['interfaces']['port1']['name']} + +*** Settings *** +| Resource | resources/libraries/robot/honeycomb/provider_backbone_bridge.robot +| Variables | resources/test_data/honeycomb/pbb/pbb.py +| Documentation | *Honeycomb provider backbone bridge test suite.* +| Suite Teardown | Run Keyword If Any Tests Failed +| ... | Restart Honeycomb And VPP And Clear Persisted Configuration | ${node} +| Force Tags | honeycomb_sanity + +*** Test Cases *** +| TC01: Honeycomb sets PBB sub-interface +| | [Documentation] | Honeycomb creates a new PBB sub-interface and checks its\ +| | ... | operational data. +| | ... +| | 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} + +| TC02: Honeycomb modifies existing PBB sub-interface +| | [Documentation] | Honeycomb modifies an existing PBB sub-interface and\ +| | ... | checks its operational data. +| | ... +| | 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} + +| TC03: Honeycomb deletes existing PBB sub-interface +| | [Documentation] | Honeycomb deletes an existing PBB sub-interface and\ +| | ... | checks operational data. +| | ... +| | 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} + +| 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} + +| 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} + +| 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} + +| 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} + +| 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} |