diff options
| author |   selias <samelias@cisco.com> | 2016-10-24 18:15:52 +0200 |
|---|---|---|
| committer |   Peter Mikus <pmikus@cisco.com> | 2016-11-04 08:50:25 +0000 |
| commit | 6bfae6634aa26c2e88dddf49d91245d880b0222b (patch) | |
| tree | fb554021ff68a8d862b5252583f296e681525863 /tests/func/honeycomb/031_vxlan_gpe.robot | |
| parent | b8fe6e5a6c0dc1f9972b7f3919041dedb1427cfd (diff) | |
CSIT-457: Address Honeycomb test failures
- tag all not-implemented features with EXPECTED_FAILING
- add workarounds for known issues with VAT dump commands
- replace hardcoded test data with parametrized
- separate IP neighbor and IP address into two test cases
- support unordered lists with compare_data_structures keyword
Change-Id: I2c683162325cee720ba496489787fa50e9c72b8c
Signed-off-by: selias <samelias@cisco.com>
Diffstat (limited to 'tests/func/honeycomb/031_vxlan_gpe.robot')
| -rw-r--r-- | tests/func/honeycomb/031_vxlan_gpe.robot | 13 |
1 files changed, 4 insertions, 9 deletions
diff --git a/tests/func/honeycomb/031_vxlan_gpe.robot b/tests/func/honeycomb/031_vxlan_gpe.robot index 54347e5725..9c6134b3cb 100644 --- a/tests/func/honeycomb/031_vxlan_gpe.robot +++ b/tests/func/honeycomb/031_vxlan_gpe.robot @@ -44,7 +44,6 @@ | ... | Restart Honeycomb And VPP And Clear Persisted Configuration | ${node} *** Test Cases *** -# TODO: Remove "continue on failure" once VPP bugs (VPP-217, VPP-156) are fixed. | Honeycomb creates VxLAN GPE tunnel | | [Documentation] | Check if Honeycomb API can configure a VxLAN GPE tunnel. | | ... @@ -58,8 +57,7 @@ | | Then VxLAN GPE configuration from Honeycomb should be | | ... | ${node} | ${vxlan_gpe_if1} | | ... | ${vxlan_gpe_base_settings} | ${vxlan_gpe_settings} -| | And run keyword and continue on failure -| | ... | VxLAN GPE configuration from VAT should be +| | And VxLAN GPE configuration from VAT should be | | ... | ${node} | ${vxlan_gpe_if1} | ${vxlan_gpe_settings} | | And VxLAN GPE Interface indices from Honeycomb and VAT should correspond | | ... | ${node} | ${vxlan_gpe_if1} @@ -67,12 +65,10 @@ | Honeycomb removes VxLAN GPE tunnel | | [Documentation] | Check if Honeycomb API can remove VxLAN GPE tunnel. | | ... -| | Run Keyword And Continue On Failure -| | ... | Given VxLAN GPE configuration from Honeycomb should be +| | Given VxLAN GPE configuration from Honeycomb should be | | ... | ${node} | ${vxlan_gpe_if1} | | ... | ${vxlan_gpe_base_settings} | ${vxlan_gpe_settings} -| | Run Keyword And Continue On Failure -| | ... | And VxLAN GPE configuration from VAT should be +| | VxLAN GPE configuration from VAT should be | | ... | ${node} | ${vxlan_gpe_if1} | ${vxlan_gpe_settings} | | When Honeycomb removes VxLAN GPE interface | | ... | ${node} | ${vxlan_gpe_if1} @@ -161,8 +157,7 @@ | | Then VxLAN GPE configuration from Honeycomb should be | | ... | ${node} | ${vxlan_gpe_if6} | | ... | ${vxlan_gpe_base_ipv6_settings2} | ${vxlan_gpe_ipv6_settings2} -| | And run keyword and continue on failure -| | ... | VxLAN GPE configuration from VAT should be +| | And VxLAN GPE configuration from VAT should be | | ... | ${node} | ${vxlan_gpe_if6} | ${vxlan_gpe_ipv6_settings2} | | And VxLAN GPE Interface indices from Honeycomb and VAT should correspond | | ... | ${node} | ${vxlan_gpe_if6} |