This post originated from an RSS feed registered with Agile Buzz by James Robertson. Original Post: SUnit Test Runner Feed Title: David Buck - Blog Feed URL: http://www.cincomsmalltalk.com/rssBlog/buck-rss.xml Feed Description: Smalltalk can do that Latest Agile Buzz Posts Latest Agile Buzz Posts by James Robertson Latest Posts From David Buck - Blog

I know that TestRunner is the long-time standard for running testcases. Thankfully, the new VisualWorks browser has a goodie that allows you to run tests straight from the browser. In VisualAge there is Jeff O'Dell's SUnit Browser but that's very difficult to get hold of. (I did manage it recently, but it wasn't an easy download from the Internet).

I find TestRunner annoying for several reasons. First, it's impossible to tell it to run one particular testcase unless that testcase has already failed. I can't develop a single testcase and run only that one until I get it working. This is extremely frustrating.

With TestRunner, you also can't run a testcase in "debug" mode unless that testcase has already failed. I have to run testcases twice - once to make them fail and once to debug why they failed. If the problem is intermittent, it may fail the first time but not the second.

I'm surprised that TestRunner has been used for so long with so few complaints. I have my own test case browser for VisualWorks in the Public Store Repository. Lately, I've switched to using the RBSUnitExtensions package instead. Perhaps TestRunner should be pulled out of SUnit and replaced with a better GUI or at least suggestions on how to get a better one. As is, it makes TDD more cumbersome than it should be and may discourage people too quickly.