CSIT-662: KWI - KW renaming

 - plus: CSIT-656: Script to rename robot keywords.

Change-Id: Ia69917e406a1b346b80e5ea742f6200c1c9e9d21
Signed-off-by: Tibor Frank <tifrank@cisco.com>

1 files changed, 36 insertions, 36 deletions

diff --git a/tests/func/honeycomb/mgmt-cfg-intip4-intip6-apihc-apivat-func.robot b/tests/func/honeycomb/mgmt-cfg-intip4-intip6-apihc-apivat-func.robot
index edc1713824..dd619efbe7 100644
--- a/tests/func/honeycomb/mgmt-cfg-intip4-intip6-apihc-apivat-func.robot
+++ b/tests/func/honeycomb/mgmt-cfg-intip4-intip6-apihc-apivat-func.robot
@@ -34,11 +34,11 @@
 | | Given Interface state from Honeycomb should be
 | | ... | ${node} | ${interface} | down
 | | And Interface state from VAT should be | ${node} | ${interface} | down
-| | When Honeycomb sets interface state | ${node} | ${interface} | up
+| | When Honeycomb configures interface state | ${node} | ${interface} | up
 | | Then Interface state from Honeycomb should be
 | | ... | ${node} | ${interface} | up
 | | And Interface state from VAT should be | ${node} | ${interface} | up
-| | When Honeycomb sets interface state | ${node} | ${interface} | down
+| | When Honeycomb configures interface state | ${node} | ${interface} | down
 | | Then Interface state from Honeycomb should be
 | | ... | ${node} | ${interface} | down
 | | And Interface state from VAT should be | ${node} | ${interface} | down
@@ -48,7 +48,7 @@
 | | ... | with address and netmask provided.
 | | Given IPv4 address from Honeycomb should be empty | ${node} | ${interface}
 | | And ipv4 address from VAT should be empty | ${node} | ${interface}
-| | When Honeycomb sets interface ipv4 address | ${node} | ${interface}
+| | When Honeycomb sets interface IPv4 address | ${node} | ${interface}
 | | ... | ${ipv4_address} | ${ipv4_mask}
 | | Then IPv4 address from Honeycomb should be
 | | ... | ${node} | ${interface} | ${ipv4_address} | ${ipv4_prefix}
@@ -64,18 +64,18 @@
 | | And IPv4 address from VAT should be
 | | ... | ${node} | ${interface} | ${ipv4_address}
 | | ... | ${ipv4_prefix} | ${ipv4_mask}
-| | When Honeycomb removes interface ipv4 addresses | ${node} | ${interface}
+| | When Honeycomb removes interface IPv4 addresses | ${node} | ${interface}
 | | Then IPv4 address from Honeycomb should be empty | ${node} | ${interface}
 | | And ipv4 address from VAT should be empty | ${node} | ${interface}
 
 | TC04: Honeycomb modifies interface IPv4 address with prefix
 | | [Documentation] | Check if Honeycomb API can configure interfaces for ipv4\
 | | ... | with address and prefix provided.
-| | [Teardown] | Honeycomb removes interface ipv4 addresses | ${node}
+| | [Teardown] | Honeycomb removes interface IPv4 addresses | ${node}
 | | ... | ${interface}
 | | Given IPv4 address from Honeycomb should be empty | ${node} | ${interface}
 | | And ipv4 address from VAT should be empty | ${node} | ${interface}
-| | When Honeycomb sets interface ipv4 address with prefix
+| | When Honeycomb sets interface IPv4 address with prefix
 | | ... | ${node} | ${interface} | ${ipv4_address2} | ${ipv4_prefix}
 | | Then IPv4 address from Honeycomb should be
 | | ... | ${node} | ${interface} | ${ipv4_address2} | ${ipv4_prefix}
@@ -85,24 +85,24 @@
 
 | TC05: Honeycomb modifies IPv4 neighbor table
 | | [Documentation] | Check if Honeycomb API can add and remove ARP entries.
-| | [Teardown] | Honeycomb clears all interface ipv4 neighbors
+| | [Teardown] | Honeycomb clears all interface IPv4 neighbors
 | | ... | ${node} | ${interface}
 | | Given IPv4 neighbor from Honeycomb should be empty
 | | ... | ${node} | ${interface}
-| | When Honeycomb adds interface ipv4 neighbor
+| | When Honeycomb adds interface IPv4 neighbor
 | | ... | ${node} | ${interface} | ${ipv4_neighbor} | ${neighbor_mac}
 | | Then IPv4 neighbor from Honeycomb should be
 | | ... | ${node} | ${interface} | ${ipv4_neighbor} | ${neighbor_mac}
 
 | TC06: Honeycomb modifies interface configuration - IPv6
 | | [Documentation] | Check if Honeycomb API can configure interfaces for ipv6.
-| | [Teardown] | Honeycomb removes interface ipv6 addresses | ${node}
+| | [Teardown] | Honeycomb removes interface IPv6 addresses | ${node}
 | | ... | ${interface}
 | | Given IPv6 address from Honeycomb should be empty
 | | ... | ${node} | ${interface}
 | | And IPv6 address from VAT should be empty
 | | ... | ${node} | ${interface}
-| | When Honeycomb sets interface ipv6 address
+| | When Honeycomb sets interface IPv6 address
 | | ... | ${node} | ${interface} | ${ipv6_address} | ${ipv6_prefix}
 | | Then IPv6 address from Honeycomb should contain
 | | ... | ${node} | ${interface} | ${ipv6_address} | ${ipv6_prefix}
@@ -111,11 +111,11 @@
 
 | TC07: Honeycomb modifies IPv6 neighbor table
 | | [Documentation] | Check if Honeycomb API can add and remove ARP entries.
-| | [Teardown] | Honeycomb clears all interface ipv6 neighbors
+| | [Teardown] | Honeycomb clears all interface IPv6 neighbors
 | | ... | ${node} | ${interface}
 | | Given IPv6 neighbor from Honeycomb should be empty
 | | ... | ${node} | ${interface}
-| | When Honeycomb adds interface ipv6 neighbor
+| | When Honeycomb adds interface IPv6 neighbor
 | | ... | ${node} | ${interface} | ${ipv6_neighbor} | ${neighbor_mac}
 | | Then IPv6 neighbor from Honeycomb should be
 | | ... | ${node} | ${interface} | ${ipv6_neighbor} | ${neighbor_mac}
@@ -133,13 +133,13 @@
 | TC09: Honeycomb modifies interface configuration - vrf
 | | [Documentation] | Check if Honeycomb API can configure interface\
 | | ... | vrf ID.
-| | [Teardown] | Honeycomb sets interface vrf ID
+| | [Teardown] | Honeycomb sets interface VRF ID
 | | ... | ${node} | ${interface} | ${0} | ipv4
-| | When Honeycomb sets interface vrf ID
+| | When Honeycomb sets interface VRF ID
 | | ... | ${node} | ${interface} | ${1} | ipv4
-| | Then Interface vrf ID from Honeycomb should be
+| | Then Interface VRF ID from Honeycomb should be
 | | ... | ${node} | ${interface} | ${1} | ipv4
-| | And Interface vrf ID from VAT should be
+| | And Interface VRF ID from VAT should be
 | | ... | ${node} | ${interface} | ${1}
 
 | TC10: Honeycomb can configure multiple IP addresses on one interface
@@ -152,15 +152,15 @@
 | | ... | of source and destination IP addresses. Receive an ICMP reply\
 | | ... | for every packet sent.
 | | ...
-| | Given Path for 2-node testing is set
+| | Given Configure path in 2-node circular topology
 | | ... | ${nodes['TG']} | ${nodes['DUT1']} | ${nodes['TG']}
-| | When Honeycomb sets interface ipv4 address with prefix
+| | When Honeycomb sets interface IPv4 address with prefix
 | | ... | ${dut_node} | ${dut_to_tg_if1} | ${ipv4_address} | ${ipv4_prefix}
-| | And Honeycomb adds interface ipv4 address
+| | And Honeycomb adds interface IPv4 address
 | | ... | ${dut_node} | ${dut_to_tg_if1} | ${ipv4_address2} | ${ipv4_prefix}
-| | And Honeycomb sets interface ipv6 address
+| | And Honeycomb sets interface IPv6 address
 | | ... | ${dut_node} | ${dut_to_tg_if1} | ${ipv6_address} | ${ipv6_prefix}
-| | And Honeycomb adds interface ipv6 address
+| | And Honeycomb adds interface IPv6 address
 | | ... | ${dut_node} | ${dut_to_tg_if1} | ${ipv6_address2} | ${ipv6_prefix}
 | | Then IPv4 address from Honeycomb should be
 | | ... | ${dut_node} | ${dut_to_tg_if1} | ${ipv4_address} | ${ipv4_prefix}
@@ -171,16 +171,16 @@
 | | ... | ${dut_node} | ${dut_to_tg_if1} | ${ipv6_address} | ${ipv6_prefix}
 | | And IPv6 address from VAT should contain
 | | ... | ${dut_node} | ${dut_to_tg_if1} | ${ipv6_address} | ${ipv6_prefix}
-| | And Honeycomb sets interface state | ${dut_node} | ${dut_to_tg_if1} | up
-| | And Honeycomb adds interface ipv4 neighbor | ${dut_node} | ${dut_to_tg_if1}
+| | And Honeycomb configures interface state | ${dut_node} | ${dut_to_tg_if1} | up
+| | And Honeycomb adds interface IPv4 neighbor | ${dut_node} | ${dut_to_tg_if1}
 | | ... | ${ipv4_neighbor} | ${neighbor_mac}
-| | And Honeycomb adds interface ipv4 neighbor | ${dut_node} | ${dut_to_tg_if1}
+| | And Honeycomb adds interface IPv4 neighbor | ${dut_node} | ${dut_to_tg_if1}
 | | ... | ${ipv4_neighbor2} | ${neighbor_mac2}
-| | And Honeycomb adds interface ipv6 neighbor | ${dut_node} | ${dut_to_tg_if1}
+| | And Honeycomb adds interface IPv6 neighbor | ${dut_node} | ${dut_to_tg_if1}
 | | ... | ${ipv6_neighbor} | ${neighbor_mac}
-| | And Honeycomb adds interface ipv6 neighbor | ${dut_node} | ${dut_to_tg_if1}
+| | And Honeycomb adds interface IPv6 neighbor | ${dut_node} | ${dut_to_tg_if1}
 | | ... | ${ipv6_neighbor2} | ${neighbor_mac2}
-| | And Vpp nodes ra suppress link layer | ${nodes}
+| | And Suppress ICMPv6 router advertisement message | ${nodes}
 | | Then Ping and Verify IP address | ${nodes['TG']}
 | | ... | ${ipv4_neighbor} | ${ipv4_address}
 | | ... | ${tg_to_dut_if1} | ${tg_to_dut_if1_mac}
@@ -201,15 +201,15 @@
 | TC11: Honeycomb fails to configure two IPv4 addresses from the same subnet
 | | [Documentation] | Check if Honeycomb can configure two IPv4 addresses in\
 | | ... | the same subnet onto a single interface. It should not be possible.
-| | [Teardown] | Honeycomb removes interface ipv4 addresses | ${node}
+| | [Teardown] | Honeycomb removes interface IPv4 addresses | ${node}
 | | ... | ${interface}
 | | [Tags] | EXPECTED_FAILING
 # VPP API does not configure the second address, but returns success. VPP-649
-| | When Honeycomb sets interface ipv4 address with prefix
+| | When Honeycomb sets interface IPv4 address with prefix
 | | ... | ${node} | ${interface} | 192.168.0.1 | ${9}
-| | Then Honeycomb fails to add interface ipv4 address
+| | Then Honeycomb fails to add interface IPv4 address
 | | ... | ${node} | ${interface} | 192.168.0.2 | ${9}
-| | And Honeycomb fails to add interface ipv4 address
+| | And Honeycomb fails to add interface IPv4 address
 | | ... | ${node} | ${interface} | 192.232.0.2 | ${9}
 
 | TC12: Honeycomb fails to configure two IPv6 addresses from the same subnet
@@ -217,19 +217,19 @@
 | | ... | the same subnet onto a single interface. It should not be possible.
 | | [Tags] | EXPECTED_FAILING
 # VPP API does not configure the second address, but returns success. VPP-649
-| | [Teardown] | Honeycomb removes interface ipv6 addresses | ${node}
+| | [Teardown] | Honeycomb removes interface IPv6 addresses | ${node}
 | | ... | ${interface}
-| | When Honeycomb sets interface ipv6 address
+| | When Honeycomb sets interface IPv6 address
 | | ... | ${node} | ${interface} | 10::FF10 | ${64}
-| | Then Honeycomb fails to add interface ipv6 address
+| | Then Honeycomb fails to add interface IPv6 address
 | | ... | ${node} | ${interface} | 10::FF11 | ${64}
-| | And Honeycomb fails to add interface ipv6 address
+| | And Honeycomb fails to add interface IPv6 address
 | | ... | ${node} | ${interface} | 10::FFFF | ${64}
 
 | TC13: Honeycomb can configure unnumbered interface
 | | [Documentation] | Check if Honeycomb can configure an unnumbered interface\
 | | ... | on a physical interface, borrowing the IP address of 'local0'.
-| | Given Honeycomb sets interface ipv4 address | ${node}
+| | Given Honeycomb sets interface IPv4 address | ${node}
 | | ... | local0 | ${ipv4_address} | ${ipv4_prefix}
 | | When Honeycomb adds unnumbered configuration to interface
 | | ... | ${node} | ${interface} | local0