UI-DEN-5638-1 30
- Details
- Objectives
- General Comments 7
- Unresolved
- Resolved
- Number of files included: 41
-
testsuites
0
-
Folder
shared/scripts
0
- File names.py 0 Remove
-
Folder
simulator
0
- File run.py 0 Remove
-
Folder
tst_AlarmCleared
0
- File test.py 0 Remove
-
Folder
tst_AlarmStatusData
0
- File test.py 0 Remove
-
Folder
tst_AlarmTriggered
0
- File test.py 0 Remove
-
Folder
tst_Alarm_Colors
0
- File test.py 0 Remove
-
Folder
tst_CANBusFaultCount
0
- File test.py 0 Remove
-
Folder
tst_ConfirmPrimingBegin
0
- File test.py 0 Remove
-
Folder
tst_CreateTreatment
0
- File test.py 0 Remove
-
Folder
tst_DGDrainPumpData
0
- File test.py 0 Remove
-
Folder
tst_DGHeatersData
0
- File test.py 0 Remove
-
Folder
tst_DGLoadCellReadingsData
0
- File test.py 0 Remove
-
Folder
tst_DGOperationMode
0
- File test.py 0 Remove
-
Folder
tst_DGPressureData
0
- File test.py 0 Remove
-
Folder
tst_DGROPumpData
0
- File test.py 0 Remove
-
Folder
tst_DGReservoirData
0
- File test.py 0 Remove
-
Folder
tst_DGTemperaturesData
0
- File test.py 0 Remove
-
Folder
tst_DGValvesStatesData
0
- File test.py 0 Remove
-
Folder
tst_DebugText
0
- File test.py 0 Remove
-
Folder
tst_HDBloodFlowData
0
- File test.py 9 Remove
-
Folder
tst_HDInletFlowData
0
- File test.py 0 Remove
-
Folder
tst_HDOperationModeData
0
- File test.py 0 Remove
-
Folder
tst_HDOutletFlowData
0
- File test.py 0 Remove
-
Folder
tst_HDPressureOcclusionData
0
- File test.py 0 Remove
-
Folder
tst_HomeScreen
0
- File test.py 0 Remove
-
Folder
tst_Internals
0
- File test.py 0 Remove
-
Folder
tst_ServiceShutdown
0
- File test.py 5 Remove
-
Folder
tst_TreatmentSalineData
0
- File test.py 0 Remove
-
Folder
tst_TreatmentScreen
0
- File test.py 0 Remove
-
Folder
tst_TreatmentStatesData
0
- File test.py 6 Remove
-
Folder
tst_Treatment_Adjustment_BloodDialysate
0
- File test.py 0 Remove
-
Folder
tst_Treatment_Adjustment_Duration
0
- File test.py 0 Remove
-
Folder
tst_Treatment_Adjustment_Saline
0
- File test.py 0 Remove
-
Folder
tst_Treatment_Adjustment_Ultrafiltration
0
- File test.py 0 Remove
-
Folder
tst_Treatment_BloodDialysateFlowRate
0
- File test.py 0 Remove
-
Folder
tst_Treatment_ParametersRange
0
- File test.py 0 Remove
-
Folder
tst_Treatment_PressureOcclusion
0
- File test.py 0 Remove
-
Folder
tst_Treatment_Section_BloodDialysate
0
- File test.py 0 Remove
-
Folder
tst_Treatment_Time
0
- File test.py 0 Remove
-
Folder
tst_Treatment_Ultrafiltration
0
- File test.py 0 Remove
- File requirements.txt 3 Remove
-
Folder
shared/scripts
0
-
Filter
- Only show me content:
- Unfiltered files: dynamically added content
- Filtered files: dynamically added content
- Clear filters
Details
| Participant | Role | Time Spent | Comments | Latest Comment |
|---|---|---|---|---|
|
plucia
(deleted user)
|
Author | 5h 6m | 14 | Nothing has changed about the usage of the SquishQt API, ... |
| Reviewer - Complete | 2h 33m | 16 | Still don't feel comfortable with this solution and haven... | |
| Reviewer - Complete | 9m | |||
| Total | 7h 49m | 30 |
-
Linked issues
Branches in review
| Repository | Branch to review | Branched from |
|---|
General Comments
plucia (deleted user)
As of 12/30/2020, with these changes: Code Coverage: 100% Squish Tests Passin...As of 12/30/2020, with these changes:
Code Coverage: 100%
Squish Tests Passing: 100%
Behrouz NematiPour
It is wrong to create an instance of HDSimulator each time you want to use an...It is wrong to create an instance of HDSimulator each time you want to use any function in that class.
1 - this class has not been defined as a static class, therefore, all the listers in class will be listening for each instance and the question is which one is going to respond, or all will respond, and then we will have multiple responses.
2 -This class not only should have the "cmd_" functions as static
3 - But also it needs to be a singleton class if want to have listers.
The design and usage of the class are not correct.
-
Behrouz NematiPour
marked as
Resolved
27 Jan 21
plucia (deleted user)
Limiting the HDSimulator to static functions prevents you from maintaining an...Limiting the HDSimulator to static functions prevents you from maintaining any state between successive calls and is incompatible with the DenaliCanMessenger. It is an improvement to hold state information and allows us to use the DenaliCanMessenger. Using the DenaliCanMessenger and dialin eliminates the need to maintain duplicated codebases and allows for bidirectional messaging. Your squish folder was doing the same thing as dialin but on a smaller scale.
1 - The test scripts are run in a consecutive manner, not in parallel. Each test should be self contained.
2 - (See statement above). This comment is about dialin, not testsuites.
3 - (See statement above). This comment is about dialin, not testsuites.
Behrouz NematiPour
I don't mean to limit the HDSimulator to static functions, it can have static...I don't mean to limit the HDSimulator to static functions, it can have static and normal methods.
1 - The test scripts are run in a consecutive manner, not in parallel. Each test should be self contained.
I agree in this case but the general implementation and design of HDSimulator lead to that misuse of the class.
plucia (deleted user)
We are in agreement that each test should be self contained. To ensure each t...We are in agreement that each test should be self contained.
To ensure each test is self-contained, each test needs to have a separate instance of HDSimulator.
The design of dialin is not the focus of this review...
Related dialin code review: http://dvm-linux02:8060/cru/DIALIN-DEN-5638-1