No, you're not listening. The test tell you nothing. You cannot verify they are working correctly at all.

>I am listening to what you're saying and in most cases I try to adapt the ideas to the scenarios I am working on at the moment. But I think you're judging from some fundamental point of the view and often give too generalized statements that can not be applied to every situation easily. I also can not always throw away what we all have here and start re-factoring and re-writting because you're saying it's not up to the best standards.
>
>The tests I am writing at the moment need to verify if the procedure produces the expected output based on the current database state. Since we're dealing with the database there is no way to guarantee the exact output several months from now. But if the tests now are returning the values I am expecting then I know that the code works. I need to search if there is a way to put some expiration date for the tests because they may not be valid when the database state will change.
>
>BTW, it's good I raised this issue because I ran a quick search and found
>
>http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.testtools.unittesting.timeoutattribute.timeout.aspx
>
>Unfortunately, again .NET documentation doesn't show an example and I need to search more.