summaryrefslogtreecommitdiffstats
path: root/robot/resources/vid/teardown_vid.robot
diff options
context:
space:
mode:
authorDR695H <dr695h@att.com>2019-07-29 17:18:49 -0400
committerDR695H <dr695h@att.com>2019-07-29 17:18:49 -0400
commit63e3c4bfd4d38e02e355019bb0ce2d7410481c4b (patch)
treec81bf20779eff19bdfb5a975e14340282a3503f3 /robot/resources/vid/teardown_vid.robot
parentc0cf6a4765212cc66e364fa0eb43a2447366ce5b (diff)
dont use outdated locator
Issue-ID: TEST-174 Change-Id: Iddff8eaec3300c3dc9485a18f46fe57296c8835c Signed-off-by: DR695H <dr695h@att.com>
Diffstat (limited to 'robot/resources/vid/teardown_vid.robot')
-rw-r--r--robot/resources/vid/teardown_vid.robot5
1 files changed, 2 insertions, 3 deletions
diff --git a/robot/resources/vid/teardown_vid.robot b/robot/resources/vid/teardown_vid.robot
index 46f5a33a..d5f7fb5a 100644
--- a/robot/resources/vid/teardown_vid.robot
+++ b/robot/resources/vid/teardown_vid.robot
@@ -50,8 +50,7 @@ Delete Next VID Entity
# If we don't wait for this control to be enabled, the submit results in a 'not found' pop-up (UnexpectedAlertPresentException)
Select From List By Label //select[@ng-model='selectedCustomer'] ${customer}
- Click Button button=Submit
-
+ Click On Button When Enabled //button[contains(text(),'Submit')]
# When Handle VID Alert detects a pop-up. it will return FAIL and we are done
# Return from Keyword is required because FAIL is inored during teardown
${teardown_status}= Catenate PASS
@@ -89,7 +88,7 @@ Delete Next VID Entity
Handle VID Alert
[Documentation] When service instance has been deleted, an alert will be triggered on the search to end the loop
... The various Alert keywords did not prevent the alert exception on the Click ELement, hence this roundabout way of handling the alert
- Run Keyword And Ignore Error Click Element button=Submit
+ Run Keyword And Ignore Error Click On Button When Enabled //button[contains(text(),'Submit')]
${status} ${t}= Run Keyword And Ignore Error Handle Alert
Return From Keyword If '${status}' == 'FAIL'
Fail ${t}