CSIT-562 HC Test: Persistence suite rework, part1
[csit.git] / tests / func / honeycomb / mgmt-cfg-nsh-apihc-apivat-func.robot
1 # Copyright (c) 2016 Cisco and/or its affiliates.
2 # Licensed under the Apache License, Version 2.0 (the "License");
3 # you may not use this file except in compliance with the License.
4 # You may obtain a copy of the License at:
5 #
6 #     http://www.apache.org/licenses/LICENSE-2.0
7 #
8 # Unless required by applicable law or agreed to in writing, software
9 # distributed under the License is distributed on an "AS IS" BASIS,
10 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
11 # See the License for the specific language governing permissions and
12 # limitations under the License.
13
14 *** Variables***
15 | ${super_if}= | ${node['interfaces']['port1']['name']}
16
17 *** Settings ***
18 | Resource | resources/libraries/robot/default.robot
19 | Resource | resources/libraries/robot/honeycomb/nsh.robot
20 | Resource | resources/libraries/robot/honeycomb/honeycomb.robot
21 | Resource | resources/libraries/robot/honeycomb/vxlan_gpe.robot
22 | Variables | resources/test_data/honeycomb/nsh.py
23 | Variables | resources/test_data/honeycomb/vxlan_gpe.py
24 | Documentation | *Honeycomb NSH test suite.*
25 | Suite Teardown | Run Keyword If Any Tests Failed
26 | ... | Restart Honeycomb and VPP | ${node}
27 # disabled pending NSH version 17.04
28 #| Force Tags | honeycomb_sanity | honeycomb_odl
29
30 *** Test Cases ***
31 | TC01: Honeycomb can configure NSH entry
32 | | [Documentation] | Check if Honeycomb can configure an NSH entry.
33 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
34 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
35 | | Then NSH entry from Honeycomb should be
36 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
37
38 | TC02: Honeycomb can remove NSH entry
39 | | [Documentation] | Check if Honeycomb can remove an existing NSH entry.
40 | | Given NSH entry from Honeycomb should be
41 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
42 | | When Honeycomb removes NSH entry | ${node} | entry1
43 | | Then NSH Operational Data From Honeycomb Should Be empty | ${node}
44
45 | TC03: Honeycomb can configure new NSH entry
46 | | [Documentation] | Check if Honeycomb can configure an NSH antry after one\
47 | | ... | has been deleted.
48 | | [Teardown] | Honeycomb removes NSH entry | ${node} | entry2
49 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
50 | | When Honeycomb adds NSH entry | ${node} | entry2 | ${nsh_entry2}
51 | | Then NSH entry from Honeycomb should be
52 | | ... | ${node} | entry2 | ${nsh_entry2_oper}
53
54 | TC04: Honeycomb can configure multiple NSH entries at the same time
55 | | [Documentation] | Check if Honeycomb can configure an NSH entry when one\
56 | | ... | already exists.
57 | | [Teardown] | Honeycomb clears NSH configuration | ${node}
58 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
59 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
60 | | And Honeycomb adds NSH entry | ${node} | entry2 | ${nsh_entry2}
61 | | Then NSH entry from Honeycomb should be
62 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
63 | | And NSH entry from Honeycomb should be
64 | | ... | ${node} | entry2 | ${nsh_entry2_oper}
65
66 | TC05: Honeycomb can configure NSH map
67 | | [Documentation] | Check if Honeycomb can configure an NSH map.
68 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
69 | | And Honeycomb creates VxLAN GPE interface
70 | | ... | ${node} | ${vxlan_gpe_if1}
71 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
72 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
73 | | And Honeycomb adds NSH map | ${node} | map1 | ${nsh_map1}
74 | | Then NSH map from Honeycomb should be | ${node} | map1 | ${nsh_map1_oper}
75
76 | TC06: Honeycomb can remove NSH map
77 | | [Documentation] | Check if Honeycomb can remove an existing NSH map.
78 | | Given NSH entry from Honeycomb should be
79 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
80 | | And VxLAN GPE Operational Data From Honeycomb Should Be
81 | | ... | ${node} | ${vxlan_gpe_if1}
82 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
83 | | And NSH map from Honeycomb should be | ${node} | map1 | ${nsh_map1_oper}
84 | | When Honeycomb removes NSH map | ${node} | map1
85 | | Then NSH map from Honeycomb should not exist | ${node} | map1
86 | | And NSH entry from Honeycomb should be
87 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
88
89 | TC07: Honeycomb can modify existing NSH map
90 | | [Documentation] | Check if Honeycomb can configure an NSH map after one\
91 | | ... | has been deleted.
92 | | [Teardown] | Honeycomb removes NSH map | ${node} | map1_edit
93 | | Given NSH map from Honeycomb should not exist | ${node} | map1_edit
94 | | And NSH entry from Honeycomb should be
95 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
96 | | And VxLAN GPE Operational Data From Honeycomb Should Be
97 | | ... | ${node} | ${vxlan_gpe_if1}
98 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
99 | | When Honeycomb adds NSH map | ${node} | map1_edit | ${nsh_map1_edit}
100 | | Then NSH map from Honeycomb should be
101 | | ... | ${node} | map1_edit | ${nsh_map1_edit_oper}
102 | | And NSH entry from Honeycomb should be
103 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
104
105 | TC08: Honeycomb can configure multiple NSH maps at the same time
106 | | [Documentation] | Check if Honeycomb can configure and NSH map when one\
107 | | ... | already exists.
108 | | [Teardown] | Run Keywords
109 | | ... | Honeycomb clears NSH configuration | ${node} | AND
110 | | ... | Honeycomb removes VxLAN GPE interface
111 | | ... | ${node} | ${vxlan_gpe_if1} | AND
112 | | ... | Honeycomb removes VxLAN GPE interface
113 | | ... | ${node} | ${vxlan_gpe_if2}
114 | | Given NSH map from Honeycomb should not exist | ${node} | map2
115 | | And NSH entry from Honeycomb should be
116 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
117 | | And VxLAN GPE Operational Data From Honeycomb Should Be
118 | | ... | ${node} | ${vxlan_gpe_if1}
119 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
120 | | And Honeycomb creates VxLAN GPE interface
121 | | ... | ${node} | ${vxlan_gpe_if2}
122 | | ... | ${vxlan_gpe_base_settings2} | ${vxlan_gpe_settings2}
123 | | When Honeycomb adds NSH map | ${node} | map1 | ${nsh_map1}
124 | | And Honeycomb adds NSH map | ${node} | map2 | ${nsh_map2}
125 | | Then NSH map from Honeycomb should be
126 | | ... | ${node} | map1 | ${nsh_map1_oper}
127 | | And NSH map from Honeycomb should be
128 | | ... | ${node} | map2 | ${nsh_map2_oper}

©2016 FD.io a Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation. Linux is a registered trademark of Linus Torvalds.
Please see our privacy policy and terms of use.