Don't use deprecated TestCase assertions like self.assertEquals. Use their modern counterpart instead like self.assertEqual.
For historical reasons, some TestCase methods had one or more aliases that are now deprecated.
Use the standardised assertions so the code is simpler, easier to read, and more future-proof (because an implication of deprecation is it will eventually be removed).
| Deprecated | Standardised |
|---|---|
assertEquals | assertEqual |
failUnlessEqual | assertEqual |
failIfEqual | assertNotEqual |
assertNotEquals | assertNotEqual |
failUnless | assertTrue |
assert_ | assertTrue |
failIf | assertFalse |
failUnlessRaises | assertRaises |
failUnlessAlmostEqual | assertAlmostEqual |
assertAlmostEquals | assertAlmostEqual |
assertNotAlmostEquals | assertNotAlmostEqual |
failIfAlmostEqual | assertNotAlmostEqual |
assertRegexpMatches | assertRegex |
assertNotRegexpMatches | assertNotRegex |
assertRaisesRegexp | assertRaisesRegex |
If our GitHub code review bot spots this issue in your pull request it gives this advice:
1 | + | class TestFeature(unittest.TestCase): | |
2 | + | def test_feature(self): | |
3 | + | self.assertEquals(int('1'), 1) |
Don't use deprecated TestCase assertions like self.assertEquals. Use their modern counterpart instead like self.assertEqual.
- | self.assertEquals(int('1'), 1) |
+ | self.assertEqual(int('1'), 1) |



