This feeling is the actual problem, not unittest’s naming conventions. The solution is not to revise unittest but to nudge the ecosystem towards pytest while keeping unittest for backwards compatibility. It’s mostly a social problem.
It is widely agreed upon by now that the “batteries included” principle has become more of a bottleneck than a feature. The challenge today is encouraging the use of certain third-party libraries in spite of their “unofficial” status. A similar situation exists with urllib vs requests and to a lesser extent re vs regex.