Browse Source
There are two concerns to do this: * assert statement will not be executed when running under optimized mode (even though we don't really do this currently) * unittest.assertXXX provides more detailed message when test fail, for example, assert count == 2 will only have AssertionError, but unittest.assertXXX can tell you the test fail because 1 != 2 This patch replaces assert statement with unittest.assertXXX in our test code. Note, not all assert statements are replaced because some of them are not aiming at the test result. Change-Id: Ida44bf6876e6fa60a4d8213f1cdad6edefb34cab Closes-Bug: #1397883changes/48/228348/1
3 changed files with 9 additions and 9 deletions
Loading…
Reference in new issue