Common standard for assertEqual usage in neutron unit testing
This BP comes to define a standard usage of assertEqual() function in Neutron unit testing code.
Neutron Unit Testing code uses assertEqual() function in all it's unit testing modules and classes.
The signature of this function is assertEqual(self, expected, observed, message='')
Values for comparison should be in order of expected value comes first, actual value comes after.
There is no standard of using this function in Neutron unit testing.
Function is called in both ways, assertEqual(
while the second case seems to be preferable.
Neutron unit testing code should have standard usage of assertEqual() function
that fits its assertEqual(
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Evgeny Fedoruk
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Armando Migliaccio
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Bug #1259292: Some tests use assertEqual(observed, expected) , the argument order is wrong | Fix Released |
Sprints
Whiteboard
As per the discussion on the linked bug, the amount of effort for changing the whole Unit Test framework is too high , when compared to the output.Therefore, it is currently frozen.