charcircuit on 3 percent of Python codebases we checked had silently failing unit tests

Does unittest cause an exception when the second argument isn't a string? That would catch some of these I'd imagine.

They should make `msg` a keyword-only argument on all the TestCase.assert* statements. It wouldn't be the first breaking change of this type.

Searching for announced breaking changes about arguments to Python included functions...

it does not, it just prints them out in the console

Comments