Dating site failure
However, if you get your reports emailed to you (e.g., from a continuous build server) then you want the message to provide enough information so that you will have an idea of what is going on before you even go to the corresponding source code. Like Jon said, it's very easy to fix it (hopefully ;-) ). The message is for me an advice, what could be done to turn it into a green test case.I would like to answer the question without considering, if a message in generel is useful. So I would appreciate if there's an advice given in the message text, how to fix this problem or where to search for the problem.And is useful when you build your application in a CI environment, like Jenkins, and using plugins to analyze error results. I created this website in 1999 to provide western people insight to the recent phenomenon of "Russian brides" from the Russian woman's point of view.I usually find that unit test failures are transient things - I'll rapidly find out what's wrong and fix it.The "finding out what's wrong" usually involves enough detail that a single message isn't going to make much difference.
I designed it to specifically answer the most important questions and clear up myths and cultural misunderstandings.So I guess this is a reiteration of Jon's answer, but too verbose to be a comment.I see this question from two perspectives, First and the most common perspective, which is already being discussed by most of us here: From the perspective of someone who is seeing the logs and trying to fix the error: I believe that both the messages provides equal information.Second perspective is that of someone who is reading/ maintaining/ reviewing the code: As we have been talking since ages about the readability and simplicity of code. We have been made to believe that my code should be simple and self explanatory so that no explicit comments are needed and I strongly agree with it.From this perspective: These messages make it a lot easier to read and go through the code as they serve the dual purpose of documentation as well as error reporting: I don't put a message for the case you cite, unless I'm running a test where I have an array of similar test values that I'm running in a loop and I want to pinpoint exactly which one failed. I agree that providing a message is helpful and I always provide one.