|
|
|
Re: Strange behaviour of text assertion [message #1444664 is a reply to message #1444651] |
Tue, 14 October 2014 11:25 |
|
I expect your tests to be failed with this text. Does your test fail with this text? What does it mean "commands are not working correctly"?
Did you add that verifications by assertion and verification mode while recording? If you did, could you please attach screenshot when you add that verifications.
Yours sincerely,
Olga.
[Updated on: Tue, 14 October 2014 12:01] Report message to a moderator
|
|
|
|
Re: Strange behaviour of text assertion [message #1445203 is a reply to message #1444741] |
Wed, 15 October 2014 05:40 |
|
Could you please attach Widget Details (how to get it) and Execution Details.
It is possible that message appears in control text after verification is done. Please try adding a long enough delay before assertion. Usually this is not required as RCPTT waits for background jobs to complete before proceeding, but hardware interaction might introduce additional complications.
wait 10000
get-property text | contains "WARNING:" | verify-false
Yours sincerely,
Olga.
|
|
|
|
|
Re: Strange behaviour of text assertion [message #1446891 is a reply to message #1446845] |
Fri, 17 October 2014 13:12 |
|
Fix doesn't work because considered text doesn't appear in 80 sec. Is it expected behavior?
If it is, you should add longer delay and ensure that launch timeout is long enough.
Also you can use the following snippet to wait just enough for the text to appear. Please choose enough time and delay for your situation.
try -times 20 -delay 500 -command { get-property text | equals "" | verify-false}
get-property text | contains "WARNING:" | verify-false
If you could attach widget details, it would help us to make cases like this working out of the box without manual delays
Yours sincerely,
Olga.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04287 seconds