UI-DEN-4690

RESOLVED.

RESOLVED.

Fair, not related to story. RESOLVED.

Fair, not related to story.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED

RESOLVED

Please refer to the newer code review after the max revision has been changed which has all the latest commits. http://192.168.10.132:8060/cru/UI-DEN-4690-2-1 Seems like it has appeared here as well.

Please refer to the newer code review after the max revision has been changed which has all the latest commits.
http://192.168.10.132:8060/cru/UI-DEN-4690-2-1
Seems like it has appeared here as well.

"*** Off the subject ***" This is not related to the story and is a code coverage of another story. Regardless it was decided to manually test the CANBus at that moment since it could be better tes...

"*** Off the subject ***"
This is not related to the story and is a code coverage of another story.
Regardless it was decided to manually test the CANBus at that moment since it could be better tested with more accurate results which all of those test couldn't be achieved manually and took a long time to test because 10 or 100 of thousands of frames tested and wasn't reasonable to do it each time automatically on server with virtual CANBus and had to be tested on a real physical CANBus.
I hope this is enough information!

DISABLE_CRC is only for development debugging purposes. and is not part of this function definition. Will be defined/enabled in case for debugging.

DISABLE_CRC is only for development debugging purposes.
and is not part of this function definition.
Will be defined/enabled in case for debugging.

I think if it's not false (false if the vData of type QByteArray is not sufficient regarding vAction) then it would be true, right ?!

I think if it's not false (false if the vData of type QByteArray is not sufficient regarding vAction) then it would be true, right ?!

"*** Off the subject **" There are tests (manually/automatically) for that and the application quits properly. If terminates by SquishCoco or being killed in the terminal may not have time to clea...

"*** Off the subject **"

There are tests (manually/automatically) for that and the application quits properly.
If terminates by SquishCoco or being killed in the terminal may not have time to clean up correctly.
When shuts down by user within the UI by user quits nicely and clean.

"
** Also please don't check "Needs resolution" for every comment you make, it happened many times regardless of mentioning it multiple times ***"

"*** Off the subject ***" At the time of testing application with SquishCoco, observed that Coco can't safely quit application and terminates the application and don't call the correct quit method ...

"*** Off the subject ***"
At the time of testing application with SquishCoco, observed that Coco can't safely quit application and terminates the application and don't call the correct quit method of the application and that makes sense since the Squish Coco is another application and will immediately terminate the UI application and don't know how to properly quit the UI application.
So UI application can't safely quit the threads.
Therefore some threading features has been manually tested.
The quitThread in each class is basically should name moveThread (move to main thread).

I hope this is enough information !

Added http://192.168.10.132:8060/cru/UI-DEN-4690-2-1#CFR-18398 line 203

Added
http://192.168.10.132:8060/cru/UI-DEN-4690-2-1#CFR-18398
line 203

How is framFlags related to this function? The return type is FrameCount and as it says it is the count of frames that had an error as the function comment says.

How is framFlags related to this function?
The return type is FrameCount and as it says it is the count of frames that had an error as the function comment says.

Added http://192.168.10.132:8060/cru/UI-DEN-4690-2-1#CFR-18400 line 152

Added
http://192.168.10.132:8060/cru/UI-DEN-4690-2-1#CFR-18400
line 152

added. please refer to http://192.168.10.132:8060/cru/UI-DEN-4690-2-1#CFR-18381 line 44

added.
please refer to http://192.168.10.132:8060/cru/UI-DEN-4690-2-1#CFR-18381
line 44

Added

Added

It is all documentations and Doxygenization. If you see otherwise is because the file names changed and the code review takes it as a new file and marks all the file content as to be reviewed. Let ...

It is all documentations and Doxygenization.
If you see otherwise is because the file names changed and the code review takes it as a new file and marks all the file content as to be reviewed.
Let me know if otherwise.

what docstring, where in the code?

what docstring, where in the code?

What do you mean by : "if init() changes, this function will behave differently, but it won't be reflected in the documentation" the function document says the same thing: "returns the return value...

What do you mean by :
"if init() changes, this function will behave differently, but it won't be reflected in the documentation"
the function document says the same thing:
"returns the return value of the init() method"
so if init() changes this function return changes because it's an overloaded method of the init() function.

Missing details and description

Missing details and description

Should indicate the return type and what is returned when. if init() changes, this function will behave differently, but it won't be reflected in the documentation

Should indicate the return type and what is returned when. if init() changes, this function will behave differently, but it won't be reflected in the documentation

The docstrings need to include information about when true and false are returned

The docstrings need to include information about when true and false are returned