LEAHI-TESTSUITES-LDT-2278

LEAHI-TESTSUITES-LDT-2278

Activity on this page:

Line History

Line history chart not available

Line history chart not available

 

Stats

Commits this week: 0
Total Commits: 3,303
Last Commit: 20 Nov
Commits this week: 0

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 
Today
13 hrs ago

Vendor - TEL - Divya Sree Nidamamidi

Removed the wait function

Removed the wait function

13 hrs ago

Vendor - TEL - Divya Sree Nidamamidi

reason is given has one

reason is given has one

Thursday 11 Dec
4:15 pm

Nicholas Ramirez

instead of wait wait for o_vitalCountdown_Text property to be visible

instead of wait wait for o_vitalCountdown_Text property to be visible

4:11 pm

Nicholas Ramirez

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

3:55 pm

Nicholas Ramirez

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

3:54 pm

Nicholas Ramirez

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

3:46 pm

Nicholas Ramirez

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

3:41 pm

Nicholas Ramirez

reason

reason

4:59 am

Vendor - TEL - Divya Sree Nidamamidi

Renamed the function setObjectText

Renamed the function setObjectText

4:58 am

Vendor - TEL - Divya Sree Nidamamidi

Renamed the function setObjectText

Renamed the function setObjectText

4:27 am

Behrouz NematiPour

3:39 am

Vendor - TEL - Divya Sree Nidamamidi

Renamed the function setObjectText

Renamed the function setObjectText

3:38 am

Vendor - TEL - Divya Sree Nidamamidi

Testing the values with rejection reason and with no rejection reason

Testing the values with rejection reason and with no rejection reason

Wednesday 10 Dec
9:23 am

Nicholas Ramirez

does not match function in stagin please verify and update

does not match function in stagin please verify and update

9:22 am

Nicholas Ramirez

In stagin the function name is setObjectText please update to avoid conflicts

In stagin the function name is setObjectText please update to avoid conflicts

Monday 08 Dec
11:02 pm

Vendor - TEL - Divya Sree Nidamamidi

Added the test case name in suite Conf file

Added the test case name in suite Conf file

4:22 am

Vendor - TEL - Divya Sree Nidamamidi

Renamed the function to match the staging

Renamed the function to match the staging

4:22 am

Vendor - TEL - Divya Sree Nidamamidi

Removed this function and using set_Object_Text() function

Removed this function and using set_Object_Text() function

Friday 05 Dec
2:47 pm

Nicholas Ramirez

Please add the test case to the suite.conf

Please add the test case to the suite.conf

2:44 pm

Nicholas Ramirez

use setObjectText () and remove this

use setObjectText () and remove this

2:43 pm

Nicholas Ramirez

update to setObjectText to match what is in staging

update to setObjectText to match what is in staging

7:23 am

Vendor - TEL - Divya Sree Nidamamidi

Removed all the waits

Removed all the waits

7:23 am

Vendor - TEL - Divya Sree Nidamamidi

As per create treatment test script comment removed this function

As per create treatment test script comment removed this function

7:22 am

Vendor - TEL - Divya Sree Nidamamidi

removed the waits as per suggestion

removed the waits as per suggestion

7:22 am

Vendor - TEL - Divya Sree Nidamamidi

moved this function into utility.py file and changed the name as get_title_text_parameter

moved this function into utility.py file and changed the name as get_title_text_parameter

7:20 am

Vendor - TEL - Divya Sree Nidamamidi

As per previous test script removed this function and using set_property_text method

As per previous test script removed this function and using set_property_text method

7:19 am

Vendor - TEL - Divya Sree Nidamamidi

Moved this function into utility.py file

Moved this function into utility.py file

7:19 am

Vendor - TEL - Divya Sree Nidamamidi

Moved this function into shared file

Moved this function into shared file

7:18 am

Vendor - TEL - Divya Sree Nidamamidi

Moved this into config.py file

Moved this into config.py file

Wednesday 03 Dec
11:06 am

Nicholas Ramirez

Please add a test to automatically send BP data... 1. Measure Vitals Button -> press button then send data from fw and the field will automatically populate on popup 2. When timer expires... 1. Tes...

Please add a test to automatically send BP data...
1. Measure Vitals Button -> press button then send data from fw and the field will automatically populate on popup
2. When timer expires...
1. Test No rejection reason after expiration FW receives request then FW sends Vitals data and the vitals section on the main treatment screen will update with those values.
2 . Test With a rejection reason when time expires then the vitals popup will automaticallly popup and test that the popup appears if request is rejected