Trinominal 0 Newbie Poster

Hi,

For .NET developers who uses unit tests to test their code, are you suffering from regression (i.e., unit tests which fails on a regular basis)?

If so, how do you face these issues? Regular debug sessions to find the problem each time a test is being failed? Some other, maybe more sophisticated approaches?

I would like to hear your opinion about the following solution which can find the code changes which caused a certain unit test to fail:

Unit Testing Tool

For those of you who do suffer from regression in unit tests:

1. Would you try it if you were .NET developers?

2. What do you think about this concept of getting the code changes which caused the failure together with the notification that a certain unit test have failed during the latest build?

Regards