leahi-testsuites

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-2821 Edit Treatment Parameters During Treatment - SW - 02 - Edit Treatment Parameters During Treatment - Q&R - 15: SIT - Software Integration Tests - Squish Qt

pushing functional way to handle testing received value to fw

    • -15
    • +13
    /suite_leahi/tst_edit_parameters/test.py
LDT-2821 Edit Treatment Parameters During Treatment - SW - 02 - Edit Treatment Parameters During Treatment - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -1
    • +36
    /suite_leahi/shared/scripts/names.py
    • -0
    • +512
    /suite_leahi/tst_edit_parameters/test.py
LDT-3062 Service - SW - 02 - Feature Configurations - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -6
    • +3
    /suite_leahi/tst_feature_options/test.py
LDT-3062 Service - SW - 02 - Feature Configurations - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -4
    • +5
    /suite_leahi/tst_feature_options/test.py
changed as per comment mouseClick(utility.findChildByText(main_menu_container, "Treatment"))

changed as per comment mouseClick(utility.findChildByText(main_menu_container, "Treatment"))

LDT-2743 Service - SW - 02 - Service - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -2
    • +10
    /suite_leahi/tst_feature_options/test.py
instead of this can we use a wait for object .. mouseClick(waitForObject(settings_menu_object, 2000))

instead of this can we use a wait for object .. mouseClick(waitForObject(settings_menu_object, 2000))

is this check needed? can we just click update to remove the if statement and use waitForObject? Ex. mouseClick(waitForObject(settings_menu_object, 2000))

is this check needed? can we just click update to remove the if statement and use waitForObject?

Ex. mouseClick(waitForObject(settings_menu_object, 2000))

LDT-3062 Service - SW - 02 - Feature Configurations - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -4
    • +6
    /suite_leahi/tst_feature_options/test.py
LDT-2743 Service - SW - 02 - Service - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -40
    • +53
    /suite_leahi/shared/scripts/names.py
Merge branch 'staging' into feature/LDT-2741-Service

    • -70
    • +221
    /suite_leahi/shared/scripts/names.py
Merge branches 'feature/LDT-2741-Service' and 'feature/LDT-2741-Service' of bitbucket.org:diality-cloud/leahi-testsuites into feature/LDT-2741-Service

LDT-2743 Service - SW - 02 - Service - Q&R - 15: SIT - Software Integration Tests - Squish Qt

suite_leahi/tst_service_export_logs/testdata/data_1.tsv edited online with Bitbucket

Added test.verify as per comment

Added test.verify as per comment

Added test.verify as per comment

Added test.verify as per comment

Added test.verify as per comment

Added test.verify as per comment

Now I am verifying Heparin containers are visible or not in create rx screen

Now I am verifying Heparin containers are visible or not in create rx screen

For me all test cases getting passed

For me all test cases getting passed

LDT-3062 Service - SW - 02 - Feature Configurations - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -2
    • +5
    /suite_leahi/tst_feature_options/test.py
LDT-3062 Service - SW - 02 - Feature Configurations - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -66
    • +116
    /suite_leahi/tst_feature_options/test.py
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

LDT -3016 End of Treatment - SW - 02 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -23
    • +26
    /suite_leahi/shared/scripts/names.py
    • -1
    • +0
    /suite_leahi/tst_end_of_treatment/test.py
in addition to testing the heparin tab in main tx you need to test the heparin parameters in the create rx screen are visible depending if heparin is enabled

in addition to testing the heparin tab in main tx you need to test the heparin parameters in the create rx screen are visible depending if heparin is enabled

please update throughout for testing bools use test.verify

please update throughout for testing bools use test.verify

for testing booleans please use test.verify()

for testing booleans please use test.verify()

for testing booleans please use test.verify()

for testing booleans please use test.verify()

this seems to fail here because if we enter TREATMENT_DIALYSIS_STATE then the Blood Prime screen is not going to show and thus failing the squish test case

this seems to fail here because if we enter TREATMENT_DIALYSIS_STATE then the Blood Prime screen is not going to show and thus failing the squish test case