I think you forgot what you told me previously and you're going to tell me to change it again if I don't remind you of why you told me to rename it to MAdjustTreatmentParametersRequest in the first place.
Previously, you complained that there was no Adjust prefix and no RequestData suffix, so I've since updated it to match that.
Please remove sleeps as much as possible. Only keep if it's related to the UI navigation animation. in that case also please use utils.waitForGUI(<sec>).
denali.conf is currently used and if it exists, the treatment parameters are read directly into a QJsonObject on startup denali.csv is currently unused and so I've just deleted it for now (See http://dvm-linux02:8060/cru/#UI-DEN-4598-1CFR-19459)
Could you please explain why added delays? It was/is working without delay. The preferred way is not to slow down the test to have a successful test. I recall we had this conversation. Please remove the sleep functions.
what is the difference between these two? namings show the variable "Treatment_Parameter_Ranges_Path" should be "/media/sd-card/treatment/" and not "/media/sd-card/treatment/denali.conf" and "denali.conf" needs to be removed, right?
Any time we're pulling the safety line, there should be a fault triggered as well - otherwise s/w will be expecting things to continue operating normally and, of course, with safety line pulled they won't - causing a potential slew of alarms that won't make sense.