suite_leahi

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
duplicate line?

duplicate line?

Since this is being used everywhere, I would recommend defining a global variable(s) so that we can later be flexible to adjust that for all the mouse clicks or watforobject functions

Since this is being used everywhere, I would recommend defining a global variable(s) so that we can later be flexible to adjust that for all the mouse clicks or watforobject functions

Shouldn't this function be defined in a more general location/file? And same comment here to be aware of the translation flexibility for later.

Shouldn't this function be defined in a more general location/file?
And same comment here to be aware of the translation flexibility for later.

Not able to find in your test.py, but these types of texts will change with the translation, and if the text is used as has been defined here, your test will fail in other languages. Just be aware ...

Not able to find in your test.py, but these types of texts will change with the translation, and if the text is used as has been defined here, your test will fail in other languages.
Just be aware and think of a solution to be flexible for later when testing with other languages.

Removed the wait function

Removed the wait function

reason is given has one

reason is given has one

LDT -2174 Treatment Parameters (Create Rx) - SW - 02 - (New Design) - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -22
    • +6
    ./shared/scripts/configuration/utility.py
Removed the function and using setObjectText

Removed the function and using setObjectText

Removed the commented lines

Removed the commented lines

Removed the waitForGUI

Removed the waitForGUI

Remove the delay

Remove the delay

remove and add delay i waitForObjectExists if needed

remove and add delay i waitForObjectExists if needed

remove and add delay i waitForObjectExists if needed

remove and add delay i waitForObjectExists if needed

remove commented out lines

remove commented out lines

used setObjectText() instead

used setObjectText() instead

instead of wait wait for o_vitalCountdown_Text property to be visible

instead of wait wait for o_vitalCountdown_Text property to be visible

responses are only after requests. Manually entering vitals is not a request so a response from FW will never hapen. This test is invalid. Please Update to request first then reject when popup is ...

responses are only after requests. Manually entering vitals is not a request so a response from FW will never hapen. This test is invalid.

Please Update to request first then reject when popup is open and that will satisfy https://devapps.diality.us/cru/LEAHI-TESTSUITES-LDT-2278-1#c25754

When popup is open need to add test to hit measure button adn FW sends rejection and confirm rejection reason is displayed on popup and popup stays open upon rejection

When popup is open need to add test to hit measure button adn FW sends rejection and confirm rejection reason is displayed on popup and popup stays open upon rejection

This never happens because the interval doesnt hit 0 in the test.. I would suggest settings timeout to 5 min and waiting listening in a loop for 5 min to get the request.. look into can_interface.r...

This never happens because the interval doesnt hit 0 in the test.. I would suggest settings timeout to 5 min and waiting listening in a loop for 5 min to get the request.. look into can_interface.register_receiving_publication_function() to listen for a message from UI

Update: 1. You need a test to wait for the timer to countdown all the way and confirm FW is receiving the request. I suggest setting the inerval to 5 min and add a way to wait 5 min max until we r...

Update:

1. You need a test to wait for the timer to countdown all the way and confirm FW is receiving the request. I suggest setting the inerval to 5 min and add a way to wait 5 min max until we receive the Request from UI..
e.g. To listen for a UI message look into can_interface.register_receiving_publication_function().. example in Solution infusion.
2. I would like a test during the timer running to change the interval time and verify the count down updates per the new interval.
e.g. set 30 min and verify the count down is going down to the nearest 30 min interval, Open the vitals interval popup and change to 5 min and confirm then test the countdown udpates to countdown to the nearest 5 min mark

reason

reason

LDT -1456 Ultrafiltration - SW - 02 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

Removed the function and using setObjectText

Removed the function and using setObjectText

Renamed the function has setObjectText

Renamed the function has setObjectText

Renamed the function setObjectText

Renamed the function setObjectText

Renamed the function setObjectText

Renamed the function setObjectText

LDT -2280 Patient Vitals - SW - 02 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -2
    • +2
    ./shared/scripts/configuration/utility.py
Renamed the function setObjectText

Renamed the function setObjectText

Testing the values with rejection reason and with no rejection reason

Testing the values with rejection reason and with no rejection reason