Sure, not a biggie. Like most things its a matter of balance: I need to read a test anyway to figure out what its doing for code review, I need to read a test to fix it when it stops working. A title just doesn't need to explain everything that might be going on a test because I have so much context from: where the test exists, the file its in, the class its in and the actual contents of the test. As a result I rarely read the test name.

There's work in writing a long test name and the maintenance in keeping it relevant as things change. The best part is when you decorate or add mocks and find that now you are over 80 chars. The most important thing is that we've got a test and covers the right things. If a long test name helps you, go for it.