Activity leahi-testsuites/suite_leahi/tst_end_of

10:09 am

Nicholas Ramirez

More
Re: LEAHI-TESTSUITES-LDT-3670-1
commented on review

all these changes should be in tst_create_treatment test case. We need to update the existing one with the new design not just create a nmew t estcase

11:05 am

Dara Navaei

More
LEAHI-TESTSUITES-LDT-3670-1
started review

LEAHI-TESTSUITES-LDT-3670_SW Misc & Enhc - SW - 02 - New Design - CreateRx - Q&R

9:22 am

Behrouz NematiPour

More
LEAHI-TESTSUITES-LDT-3014-1
finished reviewing

9:37 am

Vendor - TEL - Divya Sree Nidamamidi

Added the comment line in names.py file

10:20 am

Nicholas Ramirez

More
Re: LEAHI-TESTSUITES-LDT-3014-1
replied to Vendor - TEL - Divya Sree Nidamamidi

please leave a comment above describng why the visible property is being left in

3:24 am

Vendor - TEL - Divya Sree Nidamamidi

changed the code as per your suggestion to the check the advanced mode property in the file system.conf

3:23 am

Vendor - TEL - Divya Sree Nidamamidi

changed the code to check the heparinsyringepump value

3:23 am

Vendor - TEL - Divya Sree Nidamamidi

For confirm button in create rx page we are using the visible property. If i remove the visible property not able to click on the element

11:16 am

Nicholas Ramirez

More
Re: LEAHI-TESTSUITES-LDT-3014-1
commented on review

this will work but can be updated to be more flexible and take into account if HeparinSringePump is set to enabled or disabled.. I suggest checking the system.conf first specfically the HeparinSyri...

this will work but can be updated to be more flexible and take into account if HeparinSringePump is set to enabled or disabled.. I suggest checking the system.conf first specfically the HeparinSyringePump and if it is set to 1 then the 3 heparin parameters are visible.

IF HeparinSyringePump is set to 0 then heparin is defeatured and those 3 heparin parameters are not visible and will fail to find and set those values.

11:13 am

Nicholas Ramirez

More
Re: LEAHI-TESTSUITES-LDT-3014-1
commented on review

this way will not be flexible. We are removing 2 of the pre treatment steps so this case will fail in a future staging build. A better way to check if the steps are shorter or longer is to check if...

this way will not be flexible. We are removing 2 of the pre treatment steps so this case will fail in a future staging build. A better way to check if the steps are shorter or longer is to check if we are in advanced mode.

I suggest checking the system.conf file specifically AdvancedMode if it is set to 0 then we are in standard mode = more steps if AdvancedMode is set to 1 then advanced mode is enabled and we will see the shorter amount of steps

10:52 am