diff options
| author |   selias <samelias@cisco.com> | 2017-05-09 12:38:35 +0200 |
|---|---|---|
| committer | Samuel Eliáš <samelias@cisco.com> | 2017-05-17 07:27:59 +0000 |
| commit | a114591eac9f52502048db886da2fb228c62254d (patch) | |
| tree | 24426e7fe44f24e8c9471da885269813214550e9 /resources/libraries/robot/honeycomb/nat.robot | |
| parent | 03bb1e5611946a53f243a3d923c8f2d1aeee079a (diff) | |
CSIT-562 HC Test: Persistence suite rework, part1
- rename keywords that check operational data, to distinguish from keywords
that check configuration data
- modify existing persistence cases so that they don't affect each other
- add feature-specific persistence tests for: Interface Management, L2 bridge
- move Interface Management variables to separate file so they can be reused
- add new tag HC_PERSIST to execute persistence tests separately
- update existing Honeycomb tags to comply with CSIT conventions
More feature-specific tests to be added in part2.
Change-Id: I8657da4bb9e9a3d5261c04f5f1999b2572f605ef
Signed-off-by: selias <samelias@cisco.com>
Diffstat (limited to 'resources/libraries/robot/honeycomb/nat.robot')
| -rw-r--r-- | resources/libraries/robot/honeycomb/nat.robot | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/resources/libraries/robot/honeycomb/nat.robot b/resources/libraries/robot/honeycomb/nat.robot index 17cda4763e..81bffe66d7 100644 --- a/resources/libraries/robot/honeycomb/nat.robot +++ b/resources/libraries/robot/honeycomb/nat.robot @@ -18,7 +18,7 @@ | Documentation | Keywords used to test Honeycomb NAT node. *** Keywords *** -| NAT configuration from Honeycomb should be empty +| NAT Operational Data From Honeycomb Should Be empty | | [Documentation] | Uses Honeycomb API to retrieve NAT operational data\ | | ... | and expects to find only default values. | | ... @@ -28,7 +28,7 @@ | | ... | | ... | *Example:* | | ... -| | ... | \| NAT configuration from Honeycomb should be empty \ +| | ... | \| NAT Operational Data From Honeycomb Should Be empty \ | | ... | \| ${nodes['DUT1']} \| ${default_settings} \| | | [Arguments] | ${node} | ${default_settings} | | ${data}= | Get NAT Oper data | ${node} @@ -120,7 +120,7 @@ | | Configure NAT on interface | | ... | ${node} | ${interface} | ${direction} | ${True} -| NAT interface configuration from Honeycomb should be +| NAT interface Operational Data From Honeycomb Should Be | | [Documentation] | Uses Honeycomb API to retrieve interface operational data\ | | ... | and compares the NAT section against expected settings. | | ... @@ -132,13 +132,13 @@ | | ... | | ... | *Example:* | | ... -| | ... | \| NAT interface configuration from Honeycomb should be \ +| | ... | \| NAT interface Operational Data From Honeycomb Should Be \ | | ... | \| ${nodes['DUT1']} \| GigabitEthernet0/8/0 \| outbound \| | | [Arguments] | ${node} | ${interface} | ${direction} | | ${data}= | Get interface oper data | ${node} | ${interface} | | Variable should exist | ${data['interface-nat:nat']['${direction}']} -| NAT interface configuration from Honeycomb should be empty +| NAT interface Operational Data From Honeycomb Should Be empty | | [Documentation] | Uses Honeycomb API to retrieve interface operational data\ | | ... | and expects to find no data for the given direction. | | ... @@ -150,13 +150,13 @@ | | ... | | ... | *Example:* | | ... -| | ... | \| NAT interface configuration from Honeycomb should be empty \ +| | ... | \| NAT interface Operational Data From Honeycomb Should Be empty \ | | ... | \| ${nodes['DUT1']} \| GigabitEthernet0/8/0 \| outbound \| | | [Arguments] | ${node} | ${interface} | ${direction} | | ${data}= | Get interface oper data | ${node} | ${interface} | | Variable should not exist | ${data['interface-nat:nat']['${direction}']} -| NAT interface configuration from VAT should be +| NAT interface Operational Data From VAT Should Be | | [Documentation] | Uses Honeycomb API to retrieve NAT configured interfaces\ | | ... | and compares with expected settings. | | ... @@ -167,7 +167,7 @@ | | ... | | ... | *Example:* | | ... -| | ... | \| NAT interface configuration from VAT should be \ +| | ... | \| NAT interface Operational Data From VAT Should Be \ | | ... | \| ${nodes['DUT1']} \| ${settings} \| | | [Arguments] | ${node} | ${settings} | | ${data}= | VPP get NAT interfaces | ${node} |