RESOLVED

RESOLVED

RESOLVED.
As per our conversation today, these uncovered issues will be addressed as part of the squish migration.

done

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

This should be #4

done

Basically, you're calling waitForObjectExists on a component that will always exist. It will be visible and enabled too, so waitForObject wouldn't help you. What would help you is to wait for the object to exist that distinguishes it from the object being waited for in previous calls to test_state. The dictionary, names.o_treatmentStart_HeparinSection, is not unique with each call, but if you set the buttonText property of that dictionary on each call, then it will be unique. So that property needs to be part of the object you're waiting for in order for repeated calls to waitForObjectExists to be useful. Using the helper function is up to you. I'm just letting you know of its existence and purpose should you choose to use it in the future once it's merged. Hope this clarifies things

DEN-5928: Investigation on the ultrafiltration founded bug

Created a Bug for investigation put on next spring.
Created a tag on this git commit.
Put enough information in the bug description.

Done

done,
Sure from now on.

done,
Sure from now on.

I'm not sure I see what's the issue to resolve here since I notice only a helper method for waitForObjectExists of SquishQt.
And also I would strongly not want to play with SquishQt APIs so when an error happens or when the test is not working I don't want to debug the helper or wrappers and want to only focus on the test.
Please use simple direct SquishQt API.
You are free to do any sophisticated logic in dialin but please keep the tests as simple as possible (just copy/paste if applicable) and only use SquishQt API unless it's absolutely necessary.

Same comment as above here.

Please get with SYS Engineering and SeanN of FW to get to the bottom of this. Once you got an answer, please remove comment.

"notices" instead of "notice"

"change" instead of "chane", also replace "I'm" with "I am", basically no informal language in code comments, only formal language.

"change" instead of "chane", also replace "I'm" with "I am", basically no informal language in code comments, only formal language.

Thanks for the comment.
I replied to the same comment.

I agree, but I wanted to keep this naming consistent with Tx, Uf only in two letters.

isSalineBolusInProgress is clearer

Same comment about waitForObjectExists as in here: http://dvm-linux02:8060/cru/#UI-DEN-5736-1CFR-20566

The object being waited for will always exist.

Instead, the buttonText should be added to the object that is being waited for. e.g.

 
your_var = names.o_treatmentStart_heparinSection
your_var["buttonText"] =  "{} DELIVERY".format(vText) 
waitForObjectExists(your_var)

To address this problem, in my current Dialin Branch I've created a dict_update convenience function that allows you to add or update a dictionary's key and value. It will return a new dictionary object without modifying the original. The default python update call modifies the original and doesn't return a new object. So, using dict_update allows a simple one-liner for situations like these.

Once merged with my branch, you can use

ui.utils.dict_update

and this operation can be simplified to a one-liner:

waitForObjectExists(dict_update(names.o_treatmentStart_heparinSection, "buttonText", "{} DELIVERY".format(vText)))