Fix argument order for assertEqual to (expected, observed)
assertEqual expects that the arguments provided to it should be (expected, observed).
If a particluar order is kept as a convention, then it helps to provide a cleaner
message to the developer if Unit Tests fail.
The following patch fixes this issue
Reviewed: https:/ /review. openstack. org/264029 /git.openstack. org/cgit/ openstack/ python- solumclient/ commit/ ?id=6559731fb33 bddccb364ab8430 f6b41b1447f76f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6559731fb33bddc cb364ab8430f6b4 1b1447f76f
Author: reedip <email address hidden>
Date: Wed Jan 6 14:38:55 2016 +0900
Fix argument order for assertEqual to (expected, observed)
assertEqual expects that the arguments provided to it should be (expected, observed).
If a particluar order is kept as a convention, then it helps to provide a cleaner
message to the developer if Unit Tests fail.
The following patch fixes this issue
TrivialFix
Change-Id: I164dd6b2b820e4 ca26bf3406f591c a786893f279
Closes-Bug: #1259292
Closes-Bug: #1277104