@ venkatamahesh:
That's not a bug, it's a best practice in my opinion. When you do the
refactoring of such unit tests you don't need a bug number to verify a patch
set which changes that. A bug report should represent a failure in behavior.
Would be cool if you still work on the refactoring but for tracking purposes
I'm closing this bug report.
** Changed in: nova
Status: New => Invalid
** Tags added: testing
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1514402
Title:
Change assertEqual(True/False,A) to assertTrue/False(A)
Status in OpenStack Compute (nova):
Invalid
Bug description:
assertEqual(True/False, A)
Change to
assertTrue/False(A)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1514402/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
