I want to debug my tests, to examine every test to see where exactly is fail. I was using coderush which is awesome tool but my trial period 1month is expired.
Any suggestion is welcome.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to debug my tests, to examine every test to see where exactly is fail. I was using coderush which is awesome tool but my trial period 1month is expired.
Any suggestion is welcome.
As Mark says, if you find a tool really useful, buy it. Personally I use ReSharper to run my tests, but that’s a personal choice.
I also use NCrunch, which is free (and wonderful). I believe you can use that for debugging too.
However, you can debug with the NUnit GUI – just attach the debugger to the process, set breakpoints and run the tests.
However, I’d typically try not to require using the debugger to fix tests. When an assertion fails in a well-designed test, that usually gives enough information to fix the implementation, after a bit of thought. If it doesn’t, that suggests it’s a complicated scenario – which sometimes suggests adding more tests to handle each part of the scenario. But yes, occasionally you will need the debugger…