tags:

views:

212

answers:

2

I've been using nosetests for the last few months to run my Python unit tests.

It definitely does the job but it is not great for giving a visual view of what tests are working or breaking.

I've used several other GUI based unit test frameworks that provide a visual snap shot of the state of your unit tests as well as providing drill down features to get to detailed error messages.

Nosetests dumps most of its information to the console leaving it the developer to sift through the detail.

Any recommendations?

+1  A: 

I've used Trac + Bitten for continuous integration, it was fairly complex setup and required substantial amount of time to RTFM, set up and then maintain everything but I could get nice visual reports with failed tests and error messages and graphs for failed tests, pylint problems and code coverage over time.

Bitten is a continuous integration plugin for Trac. It has the master-slave architecture. Bitten master is integrated with and runs together with Trac. Bitten slave can be run on any system that communicate with master. It would regularly poll master for build tasks. If there is a pending task (somebody has commited something recently), master will send "build recipe" similar to ant's build.xml to slave, slave would follow the recipe and send back results. Recipe can contain instructions like "check out code from that repository", "execute this shell script", "run nosetests in this directory". The build reports and statistics then show up in Trac.

Pēteris Caune
+1  A: 

You can use rednose plugin to color up your console. The visual feedback is much better with it.

nailxx