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/329764 /git.openstack. org/cgit/ openstack/ glance_ store/commit/ ?id=fd1e846a60c 0e73e641b22af2e d07b91b040c6a2
Committed: https:/
Submitter: Jenkins
Branch: master
commit fd1e846a60c0e73 e641b22af2ed07b 91b040c6a2
Author: yuyafei <email address hidden>
Date: Wed Jun 15 13:26:44 2016 +0800
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: I07b78383ef3873 1140143c91ae3a9 02bea55eebb
Closes-Bug: #1259292