We have both ways of ordering the parameters actual, expected result of the assertEqual() method.

While the Python implementation uses indifferent names (first, second - code) all examples use the order actual followed by expected (python doc – basic-example).

self.assertEqual('foo'.upper(), 'FOO')
self.assertEqual(s.split(), ['hello', 'world'])

I think it would be better to be consistent within this track. As I personally don't have any preferences I would just follow the official python documentation examples and default to self.assertEqual(actual, expected).

@rootulp @pheanex do you have any opinions about this?