VTreatmentHeparinData.cpp

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
RESOLVED

RESOLVED

Updated.

Updated.

Looks like this needs to be updated

Looks like this needs to be updated

RESOLVED.

RESOLVED.

That is the function signature and doesn't have to have any parameter defined if it is not being used and no argument is passing to it. This way we don't need to use the Q_UNUSED(vData); anymore fo...

That is the function signature and doesn't have to have any parameter defined if it is not being used and no argument is passing to it.
This way we don't need to use the Q_UNUSED(vData); anymore for parameters not being used.

Dereferencing which parameter here? (sorry I have never seen this in the past)

Dereferencing which parameter here? (sorry I have never seen this in the past)

UI-DEN-7820_UI DEV Post Treatment
UI-DEN-7820_UI DEV Post Treatment
RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED. As per our conversation today, these uncovered issues will be addressed as part of the squish migration.

RESOLVED.
As per our conversation today, these uncovered issues will be addressed as part of the squish migration.

done

done

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

This should be #4

This should be #4

done

done

Basically, you're calling waitForObjectExists on a component that will always exist. It will be visible and enabled too, so waitForObject wouldn't help you. What would help you is to wait for the o...

Basically, you're calling waitForObjectExists on a component that will always exist. It will be visible and enabled too, so waitForObject wouldn't help you. What would help you is to wait for the object to exist that distinguishes it from the object being waited for in previous calls to test_state. The dictionary, names.o_treatmentStart_HeparinSection, is not unique with each call, but if you set the buttonText property of that dictionary on each call, then it will be unique. So that property needs to be part of the object you're waiting for in order for repeated calls to waitForObjectExists to be useful. Using the helper function is up to you. I'm just letting you know of its existence and purpose should you choose to use it in the future once it's merged. Hope this clarifies things

DEN-5928: Investigation on the ultrafiltration founded bug Created a Bug for investigation put on next spring. Created a tag on this git commit. Put enough information in the bug description.

DEN-5928: Investigation on the ultrafiltration founded bug

Created a Bug for investigation put on next spring.
Created a tag on this git commit.
Put enough information in the bug description.

Done

Done

done, Sure from now on.

done,
Sure from now on.

done, Sure from now on.

done,
Sure from now on.

I'm not sure I see what's the issue to resolve here since I notice only a helper method for waitForObjectExists of SquishQt. And also I would strongly not want to play with SquishQt APIs so when an...

I'm not sure I see what's the issue to resolve here since I notice only a helper method for waitForObjectExists of SquishQt.
And also I would strongly not want to play with SquishQt APIs so when an error happens or when the test is not working I don't want to debug the helper or wrappers and want to only focus on the test.
Please use simple direct SquishQt API.
You are free to do any sophisticated logic in dialin but please keep the tests as simple as possible (just copy/paste if applicable) and only use SquishQt API unless it's absolutely necessary.

Same comment as above here.

Same comment as above here.