You can find many good blog posts on what to name your tests. We
present instead an appropriate strategy for when and how to
think about test naming. - Don't sweat the initial name. A bit
of thought about what you're testing is essential, but don't
expend much time on the name yet. Type in a name, quickly. Use
AAA or Given-When-Then to help derive one. It might be terrible
--we've named tests "DoesSomething" before we knew exactly what
they needed to accomplish. We've also written extensively long
test names to capture a spewn-out train of thought. No worries--
you'll revisit the name soon enough. - Write the test. As you
design the test, you'll figure out precisely what the test needs
to do. You pretty much have to, otherwise you aren't getting
past this step! :-) When the test fails, look at the combination
of the fixture name, test method name, and assertion message.
These three should (eventually) uniquely and clearly describe
the intent of the test. Make any obvious corrections, like
removing redundancy or