I’m a big adept of testing, unit testing and Test Driven Development (TDD). So for me it is very important to have an IDE that really integrates very well with a testing workflow.
While getting to know Komodo better for this review I spent many hours tweaking and using it on some of my pet projects.
The features in Komodo that are supposed to help you running your test suites don’t really have to offer much above a minor GUI layer above standard testing tools. The output generated by Komodo when a test plan is run comes straight from the output of your testing framework.
The support for testing frameworks in PyCharm is excellent. The output of your testing framework is analysed and displayed in a useful manner: you can easily hide all passed tests and just focus on the tests that failed during the last execution. PyCharm also analyses your test suites and allows you to seamlessly switch between running a complete suite or a single test case.
PyCharm offers builtin support for Coverage, a popular tool to measure the amount of code that is supported by your testcases. Using coverage you can easily measure how complete your test coverage is and what parts of your code are untested.
Further features include the possibility to auto-run tests when your code changes (a life saver if you really want to use TDD) and the ability to import and export test results.
I was really bummed out by the lack of features offered by Komodo. Compared to PyCharm it almost seems like support for modern testing frameworks was an afterthought (or no thought at all). PyCharm makes testing however a first class citizen of it’s IDE feature set.