{"id":10,"date":"2007-07-28T16:29:00","date_gmt":"2007-07-28T22:29:00","guid":{"rendered":"https:\/\/www.chrisedwards.dreamhosters.com\/blog\/2007\/07\/28\/code-smell-using-the-debugger\/"},"modified":"2010-06-14T22:36:08","modified_gmt":"2010-06-15T04:36:08","slug":"code-smell-using-the-debugger","status":"publish","type":"post","link":"http:\/\/architester.com\/blog\/2007\/07\/28\/code-smell-using-the-debugger\/","title":{"rendered":"Code Smell: Using the Debugger"},"content":{"rendered":"

When you have a lot of code to look through to find an error, you often times use a debugger. You use the debugger to step through code to find out where it is failing. This is a code smell.<\/p>\n

CODE SMELL: If you find yourself using the debugger, your tests are not fine-grained enough.<\/em><\/p>\n

Using a debugger indicates that your tests are a poor targeting system for errors. They have failed to find the error and you have had to fall back to another system to locate it. Refine your tests by breaking them into smaller units that test less code. That way, you have a smaller “probable failure zone” to look in when you get a failure. Ditch that debugger!<\/p>\n","protected":false},"excerpt":{"rendered":"

When you have a lot of code to look through to find an error, you often times use a debugger. You use the debugger to step through code to find out where it is failing. This is a code smell. CODE SMELL: If you find yourself using the debugger, your tests are not fine-grained enough. […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,8,1],"tags":[36,71],"class_list":["post-10","post","type-post","status-publish","format-standard","hentry","category-test-driven-development","category-testing","category-uncategorized","tag-tdd","tag-testing"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t