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/264006 /git.openstack. org/cgit/ openstack/ python- cinderclient/ commit/ ?id=ea2693b9d9a a65af603814c5eb 44414839216bd5
Committed: https:/
Submitter: Jenkins
Branch: master
commit ea2693b9d9aa65a f603814c5eb4441 4839216bd5
Author: reedip <email address hidden>
Date: Wed Jan 6 12:21:52 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: I817a654733e0f3 886ca85778a49aa 579592f60ff
Closes-Bug: #1259292