The states that need .value come from the td_defs that inherit from DialinEnum, and the ones that don't have .value come from the ui_defs, which are simple classes, so they don't need .value since those do not support metadata.
The UI_defs seem to be what I think aren't maintained anymore and last time updated was the 21 months ago.

Anything we want shall be available in the td_defs.
as an example:

# TDTreatmentStates.TREATMENT_RINSEBACK_STATE sub states
@unique
class TDTreaRinsebackStates(DialinEnum):
    RINSEBACK_STOP_INIT_STATE           = 0                     # Start state (stopped) of the rinseback sub-mode state machine
    RINSEBACK_RUN_STATE                 = 1                     # Rinseback running state of the rinseback sub-mode state machine
    RINSEBACK_PAUSED_STATE              = 2                     # Rinseback paused state of the rinseback sub-mode state machine
    RINSEBACK_STOP_STATE                = 3                     # Rinseback stopped (done) state of the rinseback sub-mode state machine
    RINSEBACK_RUN_ADDITIONAL_STATE      = 4                     # Additional rinseback volume (10 mL) state of the rinseback sub-mode state machine
    RINSEBACK_RECONNECT_PATIENT_STATE   = 5                     # Rinseback patient reconnect state of the rinseback sub-mode state machine
    NUM_OF_RINSEBACK_STATES             = 6                     # Number of rinseback sub-mode states

We should follow the same rule in the simulators and plugins.

Nicholas Ramirez I still need your feedback and correct me if I am wrong.

Nicholas Ramirez Please investigate the Dial-In code.

Oh, what is the interval of the lambda call?
I have never used it this way.
Not sure if that is a good or bad idea.
Did we check the performance, or if it blocks the test?
Nicholas Ramirez Resolve if you are fine with the implementation.

RESOLVED

Thank you for the details.
I will leave this to Nicholas Ramirez to decide, and let's discuss if needed.
We need to implement a Rejection reason test case and test all the reason IDs passed and the mapped texts displayed to the user in every situation.

RESOLVED.

same as:
https://devapps.diality.us/cru/LEAHI-TESTSUITES-LDT-3153-1#c29805

remove the Path.home() and use the /home/denali/
On the device, it is not even in the home folder, so the path will be entirely different.

on the VM:

conf_path = "/home/denali/Public/luis/config/configurations/" + Alarms/Rejections.conf

on the device, there MAY be something like this:

conf_path = "/opt/leahi/config/configurations/" + Alarms/Rejections.conf

I am allowing a tolerance of 2 seconds between the expected time and the UI-displayed time.

Added to suite conf

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 ?

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