Accommodate Valid Range lower/upper args
Valid Range previously accepted a valid_range string argument whose format
was "<lower>..<upper>". The valid_range argument has been deprecated and
replaced by 2 arguments: lower and upper.
Also, Rvalid Range has been renamed to Valid Range.
Instances of Rvalid Range have been altered to accommodate the changes.
Change-Id: If2e8495fb9d2099007b68d4451a8460924fbc999
Signed-off-by: Michael Walsh <micwalsh@us.ibm.com>
diff --git a/redfish/managers/test_managers_bmc_time.robot b/redfish/managers/test_managers_bmc_time.robot
index d4cd332..e0e7e5f 100644
--- a/redfish/managers/test_managers_bmc_time.robot
+++ b/redfish/managers/test_managers_bmc_time.robot
@@ -8,6 +8,7 @@
Resource ../../lib/rest_client.robot
Library ../../lib/gen_robot_valid.py
+Test Setup Printn
Test Teardown Test Teardown Execution
Suite Setup Suite Setup Execution
Suite Teardown Suite Teardown Execution
@@ -72,9 +73,9 @@
${date_time_diff}= Subtract Date From Date ${cli_bmc_time}
... ${expected_date_time} exclude_millis=yes
${date_time_diff}= Convert to Integer ${date_time_diff}
- Rpvars date_time_with_offset expected_date_time cli_bmc_time
+ Rprint Vars date_time_with_offset expected_date_time cli_bmc_time
... date_time_diff max_time_diff_in_seconds
- Rvalid Range date_time_diff 0..${max_time_diff_in_seconds}
+ Valid Range date_time_diff 0 ${max_time_diff_in_seconds}
Verify Set DateTime With Invalid Data Using Redfish