Although this blog is very loosely associated with testing, I still think it is important enough to warrant my attention. In his blog, Erik Dietrich outlines a list of criteria for “what is reasonable to expect from your IDE.”
- BUILDING THE SOFTWARE – His first criteria is that the IDE should be able to easily build your software. Additionally, the IDE should alert you of any problems and make it easy for you to locate those problems. Ideally, the IDE would even suggest solutions to those problems.
- INTEGRATED DEBUGGER – Another essential aspect for an IDE is an integrated debugger. The debugger should allow you to go through your code line by line and see the behavior of your code at runtime.
- PLUGINS AND CUSTOMIZATION – Any effective IDE or text editor relies on plugins. Plugins and customization make you more productive and enhance the the coding experience.
- AUTOMATED REFACTORING – Here is the aspect that relates this blog to software testing. Dietrich explains that he is a huge proponent of TDD. A major factor in TDD is refactoring, and he suggests that an IDE that automates refactoring removes much more human error from the TDD process. Not only does it remove error, but it is also much more efficient.
- INTELLISENSE/NAVIGATION – The last criteria is pretty self-explanatory. An IDE should make navigating your code easy, and offer type-ahead support.
From the blog cs443 – TayNock's Blog by taynock and used with permission of the author. All other rights reserved by the author.

