Correctly space expected_status 74/111074/1
authorRobert Varga <robert.varga@pantheon.tech>
Tue, 26 Mar 2024 17:35:30 +0000 (18:35 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Tue, 26 Mar 2024 17:35:30 +0000 (18:35 +0100)
The single space we have here gets escaped, leading to a test failure.
Fix that up.

Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Change-Id: Ia1a52820dc728a6ecccc1e989aa05f89a8eac06d

csit/libraries/PrefixCounting.robot

index abac3ff9dd4b84daf4462b68aa109763f581a2b5..bd32c943f48dd261836089e0d3e8fe1295e6371f 100644 (file)
@@ -35,7 +35,7 @@ Get_Ipv4_Topology
     ...
     ...    Contrary to Utils.Get_Data_From_URI, this does not Log the (potentially huge) content.
     [Arguments]    ${session}=operational    ${topology}=example-ipv4-topology
-    ${response} =    RequestsLibrary.GET On Session    ${session}    url=${PC_NW_TOPOLOGY}=${topology}?content=nonconfig expected_status=any
+    ${response} =    RequestsLibrary.GET On Session    ${session}    url=${PC_NW_TOPOLOGY}=${topology}?content=nonconfig    expected_status=any
     IF    ${response.status_code} != 200
         Fail    Get on ${topology} returned status code ${response.status_code} with message: ${response.text}
     END