Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
this is a good test for each test main function, but needs to be one time t the top of the main function. And I believe if that fails you need to exit and do not continue to the rest of the test. ...

this is a good test for each test main function, but needs to be one time t the top of the main function.
And I believe if that fails you need to exit and do not continue to the rest of the test.

make a checkblock and return if fails.

if there is no = in the line then we do not have index 1 nd the code will fail. please first split check the size then get the index if exitsts.

if there is no = in the line then we do not have index 1 nd the code will fail.
please first split check the size then get the index if exitsts.

please just add test case to the end and not remove all the prior ones

please just add test case to the end and not remove all the prior ones

removed all post treatment steps

removed all post treatment steps

updated as per comment

updated as per comment

No, it will not affect others test cases. Initially this was def setObjectText(obj, text): but divya changed to setObjectText(text, obj): So I changed back original because It was affecting my test...

No, it will not affect others test cases. Initially this was def setObjectText(obj, text): but divya changed to setObjectText(text, obj): So I changed back original because It was affecting my test scripts and I informed her about this

will this affect other test cases that have the parameters in the previous order? If so leave as is to avoid that

will this affect other test cases that have the parameters in the previous order? If so leave as is to avoid that

just add and not replace test case list

just add and not replace test case list

no need to test post treatment only pre treatment .. remove all post treatmetn steps

no need to test post treatment only pre treatment .. remove all post treatmetn steps

LEAHI-TESTSUITES-LDT-3188_Pre-Treatment - SW - 02 - Foundation - Q&R
LEAHI-TESTSUITES-LDT-3188_Pre-Treatment - SW - 02 - Foundation - Q&R
added an empty line as per comment

added an empty line as per comment

change line of code as per comment

change line of code as per comment

After removing this line of code, test script got failed one time, So I keep this line of code

After removing this line of code, test script got failed one time, So I keep this line of code

change to mouseClick(waitForObject(utility.findChildByText(main_menu_container, config.PRESCRIPTIONS)), 2000 )

change to mouseClick(waitForObject(utility.findChildByText(main_menu_container, config.PRESCRIPTIONS)), 2000 )

remove this line

remove this line

updated as per comment

updated as per comment

updated as per comment

updated as per comment

Now updated to first Standby then click on Settings menu, then Service Mode as already logged with password before, then click on feature configuration option td_simulator.td_operation_mode(TDOpMod...

Now updated to first Standby then click on Settings menu, then Service Mode as already logged with password before, then click on feature configuration option
td_simulator.td_operation_mode(TDOpModes.MODE_STAN.value, 0)
headerbar_container = waitForObject(names.o_mainMenu_MainMenu, 3000)
mouseClick(utility.findChildByText(headerbar_container, config.SETTINGS))

td_simulator.td_operation_mode(TDOpModes.MODE_SERV.value, 0)
device_settings_grid = waitForObject(names.o_DeviceSettingsGrid, 3000)
mouseClick(utility.findChildByText(device_settings_grid, config.FEATURE_CONFIGURATIONS))

mouseClick(waitForObject(utility.findChildByText(post_treatment, config.AUTO_EJECT), 2000))

mouseClick(waitForObject(utility.findChildByText(post_treatment, config.AUTO_EJECT), 2000))

mouseClick(waitForObject(utility.findChildByText(pre_treatment, config.NEXT), 2000))

mouseClick(waitForObject(utility.findChildByText(pre_treatment, config.NEXT), 2000))

This is part of the issue for the intermittent fails. You are forcing the opmode to service which changes the screen to device settings. But the bottom menu is on the wrong index. Correct navigatio...

This is part of the issue for the intermittent fails. You are forcing the opmode to service which changes the screen to device settings. But the bottom menu is on the wrong index. Correct navigation is first goingto standby then pressing the bottom menu option for settings. Then enter password then finally change opmode to service.

At present all English text-only content are maintained in config,py file

At present all English text-only content are maintained in config,py file

made changes as per comment

made changes as per comment

Now moved all text to config file and in script using as config.THAT_TEXT

Now moved all text to config file and in script using as config.THAT_TEXT

changed function name and code

changed function name and code

removed passwordCharacter, echoMode, checkable from object properties

removed passwordCharacter, echoMode, checkable from object properties

added all options as function comment for user reference

added all options as function comment for user reference

removed data_1.tsv file from branch

removed data_1.tsv file from branch

Add timeout_ms=3000 as default for utility get_object_from_names function, removed timeout_ms=3000 from all function calls in all the test scripts

Add timeout_ms=3000 as default for utility get_object_from_names function, removed timeout_ms=3000 from all function calls in all the test scripts