> > One assert per test > Was meant to make a failed test instantly communicate what's wrong with the unit under test. As frameworks evolve and our practices a

> > One assert per test > Was meant to make a failed test instantly communicate what's wrong with the unit under test. As frameworks evolve and our practices around them change, it's absolutely fine to come up with new rules. To put a finer point on that then, you're saying the rule is obsolete if your test framework allows assert statements to accept message strings?