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/338627 /git.openstack. org/cgit/ openstack/ networking- infoblox/ commit/ ?id=a52b6364fa5 d812f512837282b 884ce7995bd54b
Committed: https:/
Submitter: Jenkins
Branch: master
commit a52b6364fa5d812 f512837282b884c e7995bd54b
Author: hongzhezheng <email address hidden>
Date: Wed Jul 6 20:10:42 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: I197f2d781317b0 f0f4b9dce1cd6a4 38a9b6a7622
Partial-Bug: #1259292