Check cluster status after rejoin

[integration/test.git] / csit / libraries / NicKeywords.robot

diff --git a/csit/libraries/NicKeywords.robot b/csit/libraries/NicKeywords.robot
index c2fd846acc23c12e37f461d8105cd321bb0846cc..bea1085fc998826d730044314ceff16df14f5004 100644 (file)
--- a/csit/libraries/NicKeywords.robot
+++ b/csit/libraries/NicKeywords.robot
@@ -6,8 +6,8 @@ Library           Collections
 Library           json
 Library           RequestsLibrary
 Variables         ../variables/Variables.py
-Resource          ./Utils.robot
-Resource          Scalability.robot
+Resource          Utils.robot
+Resource          MininetKeywords.robot
 
 *** Variables ***
 ${switches}       2
@@ -34,7 +34,7 @@ Start NIC VTN Rest Test Suite
 
 Stop NIC VTN Rest Test Suite
     [Documentation]    Stop Nic VTN Renderer Test Suite
-    Stop Mininet    ${mininet_conn_id}
+    Stop Mininet And Exit    ${mininet_conn_id}
 
 Fetch Intent List
     [Documentation]    Check if VTN Renderer feature is installed.
@@ -81,7 +81,7 @@ Remove Intent From Karaf Console
     ${output}=    Issue Command On Karaf Console    intent:remove ${id}
     Should Contain    ${output}    Intent successfully removed
     ${output}=    Issue Command On Karaf Console    log:display | grep "Removed VTN configuration associated with the deleted Intent: "
-    # The below log statements has changed an info to trace mode in Beryllium, and in future release will roll back the same.
+    #The below log statements has changed an info to trace mode in Beryllium, and in future release will roll back in same.
     #Should Contain    ${output}    Removed VTN configuration associated with the deleted Intent    ${id}
 
 Mininet Ping Should Succeed
@@ -94,6 +94,6 @@ Mininet Ping Should Succeed
 Mininet Ping Should Not Succeed
     [Arguments]    ${host1}    ${host2}
     [Timeout]    2 minute
-    Write    ${host1} ping -c 10 ${host2}
+    Write    ${host1} ping -c 3 ${host2}
     ${result}    Read Until    mininet>
     Should Not Contain    ${result}    64 bytes