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/338001 /git.openstack. org/cgit/ openstack/ solum/commit/ ?id=adc1b9ddcc7 7d7f8bc1c05c830 f7b0c4a0805b8a
Committed: https:/
Submitter: Jenkins
Branch: master
commit adc1b9ddcc77d7f 8bc1c05c830f7b0 c4a0805b8a
Author: yuyafei <email address hidden>
Date: Wed Jul 6 15:32:06 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
Closes-Bug: #1259292
Change-Id: I608b07f857d9fa 2d401cab35fff6b df2defa6d55