Added the waitForObject while navigating to the pages

Added 60 second snooze

can we remove this and test adding a timeout to mouseClick(waitForObject(hdf)) on line 67 where we actually press the hdf option

we may just need 60 seconds to plot a line can we update to 60 and check if that works

To genarate the graph it will take time so added wait here

Changing to treatement mode HDF option is not displaying in the UI so added wait

Stepnames variable is the list of objects (i.e concentrate,Installation,self tests)

Standard and advanced mode differ by getting the value from the system.conf file

we can make a function to just

def rinsebackrequest_Check():
return rinsebackrequest == 8

if this works better? but well have alot more functions elsewhere. Let us know Behrouz NematiPour but the majority of the test cases do indeed use the lambda

we the lamba because we are using the waitFor() to wait for this condition to be true.

waitFor() calls the lambda multiple times until it returns True or the timeout expires.

please add report to JIRA ticket

is this the same as o_confirmButton_ConfirmButton ?

Nicholas Ramirez Please investigate the Dial-In code.

Thanks for providing the definition of the lambda.
My main question is, why lambda?
What is that condition in this lambda (what is rinsebackrequest == 8)?
If that has a common use case, better to be a function?

Nicholas Ramirez Could you please check why that is, what the difference is between the two, and whether there are any inconveniences with Dial-In we need to take care of?

Does this work?
Have you tested it?
It seems like while all are using equal, they should overwrite the previous one.

It is just a preference; if you can't find a way, that's fine to leave it as it was.

What is 2?
What was 1?

Added the variable for the path

Getting the text from rejection.conf

Added for different test case for this test case it is not used

We have one parent object, and different values are defined by different ID by using findObjectByID

Lambda is used here to pass a condition as a function that can be evaluated repeatedly without writing a full function definition.

Added the separate line for each test cases, using \ getting error

I have updated the step by getting the value from rejections.conf file

storing general configurations folder path in config.py

changed direct file path to dynamic user perspective and storing general configurations folder path in config.py

For TX states does not require the ".value"

For TXStates.RINSEBACK_STOP_INIT_STATE does not require ".value"

In another CR, this is a variable ([1] Request is ....).
After the comment is addressed there, maybe it can be used here.

Please provide an example of what the stepnames variable contains.
How do you ensure that the requested index is always available and that the code does not fail?

Why do we use findObjectByID and do not define it in then names.py?