If you’re using pytest you just paramaterize the tests and it tells you the exact failing case. Seems to be a basic feature I would be surprised to know doesn’t exist across almost all commonly used frameworks.
But thanks for bringing it up, it seems it also has "subtest" support, which might be easier than interpolating the error message in some cases:
https://docs.python.org/3/library/unittest.html#distinguishi...
Unless you need the library style in order to drive it, switch to pytest. Seriously.
- assert rewriting is stellar, so much more comfortable than having to find the right assert* method, and tell people they're using the wrong one in reviews
- runner is a lot more practical and flexible: nodeids, marks, -k, --lf, --sw, ...
- extensions further add flexibility e.g. timeouts, maxfail, xdist (though it has a few drawbacks)
- no need for classes (you can have them, mind, but if functions are sufficient, you can use functions)
- fixtures > setup/teardown
- parameterized tests