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/338717 /git.openstack. org/cgit/ openstack/ python- barbicanclient/ commit/ ?id=86d91e4e4e3 9ed0b4b65e393ca 49172fd555ddd0
Committed: https:/
Submitter: Jenkins
Branch: master
commit 86d91e4e4e39ed0 b4b65e393ca4917 2fd555ddd0
Author: hongzhezheng <email address hidden>
Date: Thu Jul 7 16:23:31 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: I5209e5889cfe62 c66dc675c00e3cc af22410f637
Partial-Bug: #1259292