Honeycomb interface state management test

[csit.git] / resources / libraries / robot / honeycomb / honeycomb.robot

diff --git a/resources/libraries/robot/honeycomb.robot b/resources/libraries/robot/honeycomb/honeycomb.robot
similarity index 65%
rename from resources/libraries/robot/honeycomb.robot
rename to resources/libraries/robot/honeycomb/honeycomb.robot
index 98b8e23..7418078 100644 (file)
--- a/resources/libraries/robot/honeycomb.robot
+++ b/resources/libraries/robot/honeycomb/honeycomb.robot
@@ -17,14 +17,15 @@
 | Library | resources/libraries/python/HTTPRequest.py
 
 *** Keywords ***
-| Setup Honeycomb service
+| Setup Honeycomb service on DUTs
 | | [Documentation] | *Setup environment for honeycomb testing*
 | | ...
 | | ... | _Setup steps:_
 | | ... | - 1. Login to each honeycomb node using ssh
 | | ... | - 2. Startup honeycomb service
 | | ... | - 3. Monitor service startup using HTTP GET request loop
-| | ... | Expected sequence of HTTP replies: connection refused -> 404 -> 401 -> 503 -> 200 (pass)
+| | ... | Expected sequence of HTTP replies:
+| | ... | connection refused -> 404 -> 401 -> 503 or 500 -> 200 (pass)
 | | ... | - 4. Configure honeycomb nodes using HTTP PUT request
 | | ...
 | | ... | _Used global constants and variables:_
@@ -32,37 +33,27 @@
 | | ... | - HTTPCodes - HTTP protocol status codes
 | | ... | - ${nodes} - dictionary of all nodes in topology.YAML file
 | | ...
-| | Start Honeycomb on all DUTs | ${nodes}
-| | Wait until keyword succeeds | 3min | 10sec | Check honeycomb startup state | ${nodes}
-| | &{Header}= | Create dictionary | Content-Type=application/xml
-| | Add VPP to honeycomb network topology | ${nodes} | ${header}
+| | [Arguments] | @{duts}
+| | Start honeycomb on DUTs | @{duts}
+| | Wait until keyword succeeds | 4min | 20sec
+| | ... | Check honeycomb startup state | @{duts}
 
-| Stop honeycomb service
+| Stop honeycomb service on DUTs
 | | [Documentation] | *Cleanup environment after honeycomb testing*
 | | ...
 | | ... | _Teardown steps:_
 | | ... | - 1. Login to each honeycomb node using ssh
 | | ... | - 2. Stop honeycomb service
 | | ... | - 3. Monitor service shutdown using HTTP GET request loop
-| | ... | Expected sequence of HTTP replies: 200 -> 404 -> connection refused (pass)
+| | ... | Expected sequence of HTTP replies:
+| | ... | 200 -> 404 -> connection refused (pass)
 | | ...
 | | ... | _Used global constants and variables:_
 | | ... | - RESOURCES_TPL_HC - path to honeycomb templates directory
 | | ... | - HTTPCodes - HTTP protocol status codes
 | | ... | - ${nodes} - dictionary of all nodes in topology.YAML file
 | | ...
-| | Stop honeycomb on all DUTs | ${nodes}
-| | Wait until keyword succeeds | 1m | 5s | Check honeycomb shutdown state | ${nodes}
-
-| Honeycomb checks VPP node configuration
-| | [Documentation] | *Check configuration of honeycomb nodes*
-| | ...
-| | ... | _Arguments:_
-| | ... | - None
-| | ...
-| | ... | _Return value:_
-| | ... | - None
-| | ...
-| | ${reply}= | Get configured topology | ${nodes}
-| | :FOR | ${item} | IN | @{reply}
-| | | Should match regexp | ${item} | ^DUT\\d{1,2}$
\ No newline at end of file
+| | [Arguments] | @{duts}
+| | Stop honeycomb on DUTs | @{duts}
+| | Wait until keyword succeeds | 2m | 10s
+| | ... | Check honeycomb shutdown state | @{duts}