tst_end_of_treatment

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
This file is added in Create treatement and removed the file in this branch

This file is added in Create treatement and removed the file in this branch

I do not see the updated test case and remove this test case "tst_new_design_createrx" from the project

I do not see the updated test case and remove this test case "tst_new_design_createrx" from the project

please remove this test case from this branch and review as its not part of this feature

please remove this test case from this branch and review as its not part of this feature

this will always pass please use the lambda way..The updates to this test case are included in this branch. code review https://devapps.diality.us/cru/#LEAHI-TESTSUITES-LDT-3814-1CFR-86614 Can we ...

this will always pass please use the lambda way..The updates to this test case are included in this branch. code review https://devapps.diality.us/cru/#LEAHI-TESTSUITES-LDT-3814-1CFR-86614

Can we revert all the changes to this branch and just use the other one to avoid conflicts

can we remove the duplicate

can we remove the duplicate

Test script is updated in create rx test script

Test script is updated in create rx test script

test script is updated in create rx feature

test script is updated in create rx feature

Report is attached in jira

Report is attached in jira

yes same object

yes same object

the update to this file should be part of this branch https://devapps.diality.us/cru/LEAHI-TESTSUITES-LDT-3670-1

the update to this file should be part of this branch

https://devapps.diality.us/cru/LEAHI-TESTSUITES-LDT-3670-1

remove file

remove file

why is this test case part of this feature? It should stay isolated in https://devapps.diality.us/cru/LEAHI-TESTSUITES-LDT-3946-1#details

why is this test case part of this feature? It should stay isolated in https://devapps.diality.us/cru/LEAHI-TESTSUITES-LDT-3946-1#details

please add report to JIRA ticket

please add report to JIRA ticket

is this the same as o_confirmButton_ConfirmButton ?

is this the same as o_confirmButton_ConfirmButton ?

File is removed

File is removed

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

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

what is this file for? can we remove it

what is this file for? can we remove it

LEAHI-TESTSUITES-LDT-3670_SW Misc & Enhc - SW - 02 - New Design - CreateRx - Q&R
LEAHI-TESTSUITES-LDT-3670_SW Misc & Enhc - SW - 02 - New Design - CreateRx - Q&R
LEAHI-TESTSUITES-LDT-3447_Water, Dialysate, and Blood Sampling - SW - 02 - Water sample & Dialysate Checks - Q&R
LEAHI-TESTSUITES-LDT-3447_Water, Dialysate, and Blood Sampling - SW - 02 - Water sample & Dialysate Checks - Q&R
Added the comment line in names.py file

Added the comment line in names.py file

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

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

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

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

changed the code to check the heparinsyringepump value

changed the code to check the heparinsyringepump value

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

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

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.

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

remove the visible property

remove the visible property

Removed the duplicate objects

Removed the duplicate objects