I'd like to work on this one.

(In reply to Andrew Halberstadt [:ahal] from comment #0)

This means:

1. Use 'assert foo == bar' instead of self.assertEquals(foo, bar)

What about its counterpart self.assertNotEqual(foo, bar)? Should I change it to assert foo!= bar?

Great, thanks for your interest!

Yes exactly, you can use any arbitrary boolean clause in the assert statement. So whatever the semantic meaning of the old function being used, we just need to make sure we do the same thing in the assert.

I could handle most of the assert<relational-operator>() methods, save assertRaises().

In resource 1, pytest.raises helper is discussed as a context manager. I'm considering to replace all occurrences of assertRaises() method in mozilla-central/testing/mozbase/mozinfo/tests/test.py file with pytest.raises helper.

In this process, I'd like to understand what do the second and third arguments to the assertRaises() method signify?
I suppose the second argument is a callable as per 2 isn't it?

Thank you!

Yes, you have it right. The second argument is a function (or other callable), and the 3rd and 4th are the arguments you would pass into that function (if any). So you would convert this:

self.assertRaises(ValueError, func, arg1, arg2=None)

into this:

with pytest.raises(ValueError):
    func(arg1, arg2=None)

Pooja: I'm releasing this bug due to inactivity. If you are still interested in working on it, please work with ahal or myself.

https://hg.mozilla.org/mozilla-central/rev/25b62f114f95