tst_patient_vitals

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Updated the method

Updated the method

Updated the test.compare values

Updated the test.compare values

Updated the method

Updated the method

Modified the script when rejection reason is 1 it will hit the measure button

Modified the script when rejection reason is 1 it will hit the measure button

Added the method to check the integrated BP cuff value from system,conf file if it is disable enable the value from UI check_bp_cuff_enabled

Added the method to check the integrated BP cuff value from system,conf file if it is disable enable the value from UI
check_bp_cuff_enabled

may need to update the test.compares.

may need to update the test.compares.

This can be updated to     def verify_automatic_vitals_noRejection_Reason(): MAX_WAIT = 5 * 60 * 1000 # 5 minutes in seconds test.verify(waitFor( lambda: vitalsrequest == True, M...

This can be updated to

    def verify_automatic_vitals_noRejection_Reason():  

    MAX_WAIT = 5 * 60 * 1000  # 5 minutes in seconds
    
    test.verify(waitFor( lambda: vitalsrequest == True, MAX_WAIT), "UI Sending the request to FW")
    td.td_vitals_adjustment_response(vRejectionReason=0)
    td.td_vitals(systolic = 80, 
        diastolic   = 60, 
        heartRate   = 140 )

            
    blood_pressure  = waitForObjectExists(names.o_treatmentHome_bloodPressure_LabelValue).topText
    test.compare("70"+"/"+"50", blood_pressure,"Blood pressure value should be ->"+str("80"+"/"+"60"))
    heart_rate = waitForObjectExists(names.o_treatmentHome_heartBeat_LabelValue).topText
    test.compare("120", heart_rate,"Heart Rate value should be ->"+str(120))
update method to     # handler for messages from UI to FW def handle_patient_vitals_request( message, timestamp = 0.0): """ Called when the user requests to firmware from UI @return: No...

update method to

    # handler for messages from UI to FW
def handle_patient_vitals_request( message, timestamp = 0.0):
    """
    Called when the user requests to firmware from UI
    @return: None
    """
    global vitalsrequest
    vitalsrequest = True
initialize request variable vitalsrequest = None

initialize request variable

vitalsrequest = None

this test is not added to test the measure button i do not see qhewre o_measureVitalsButton_TouchRect is pressed other than the place its not needed

this test is not added to test the measure button i do not see qhewre o_measureVitalsButton_TouchRect is pressed other than the place its not needed

One issue encountered is the if BP Cuff is disabled then teh measure button will also be disabled. So as prep one thing to do before running the tests is to verify the bp cuff is enabled or change ...

One issue encountered is the if BP Cuff is disabled then teh measure button will also be disabled. So as prep one thing to do before running the tests is to verify the bp cuff is enabled or change the variable in teh system.conf

It is removed

It is removed

Modified the step as per suggestion

Modified the step as per suggestion

verify_vitals_pop_up_is_opened_automatically_after_an_interval need to be placed before checking the request in test.verify(waitFor("'vitalsrequest == True'", 1000), "UI Sending the request to FW")

verify_vitals_pop_up_is_opened_automatically_after_an_interval need to be placed before checking the request in test.verify(waitFor("'vitalsrequest == True'", 1000), "UI Sending the request to FW")

this should be removed. We need to wait for UI to send the request. Here you are manually sending the request where the timer does not countdown to 0 to send it.

this should be removed. We need to wait for UI to send the request. Here you are manually sending the request where the timer does not countdown to 0 to send it.

can we change to just click the arrow button just once as we do not care about what is being set. We only care about the bp measurement parameter

can we change to just click the arrow button just once as we do not care about what is being set. We only care about the bp measurement parameter

Updated the test report in jira

Updated the test report in jira

Added as per the suggestion

Added as per the suggestion

Updated the test cases as per your suggestion

Updated the test cases as per your suggestion

updated

updated

Test script is updated as per suggestion

Test script is updated as per suggestion

Test script is updated as per suggestion

Test script is updated as per suggestion

sorry "reasom" is mispelled.. should be "reason"

sorry "reasom" is mispelled.. should be "reason"

Removed the wait function

Removed the wait function

reason is given has one

reason is given has one

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