Daniel Barkalow [off-list ref] writes:
Of course, a patch to clean up the user experience could have a hunk that
makes the test expect that the UI is cleaned up. It's not like we can't
change our tests to accompany improvements in behavior, and I'd argue that
those hunks give a useful example of the improvement.
Ok.
The point of adding these tests (and parts of tests) is that I'd forgotten
to maintain some of the important information while writing
builtin-checkout, and there wasn't a test that it was provided. While some
of the output is arbitrary informative text, there's a certain amount of
generated information there that shouldn't get lost or be incorrect.
Fair enough.