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/332729 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=2410ff06afe 2161bb92e11ef36 d8602fc5599d34
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2410ff06afe2161 bb92e11ef36d860 2fc5599d34
Author: liangjingtao <email address hidden>
Date: Wed Jun 22 18:35:21 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.
Change-Id: I85628a1d60fa80 9f80d658ed7d66d bd5d7e03010
Closes-Bug: #1259292