This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Test Feedback for Packages
Feed Title: Travis Griggs - Blog
Feed URL: http://www.cincomsmalltalk.com/rssBlog/travis-rss.xml
Feed Description: This TAG Line is Extra
One thing I'd like to know before I publish, is what the test status of a given package is. I've just published a version of ExtraRBForSUnitToo that is a start of that. Here's the simplest thing that probably won't work:
This was actually quick and easy to throw together. But it begs a couple of interesting questions:
Different size icons make the vertical alignment sketchy. Though maybe this is a good way to see packages that are tested vs those that aren't. Putting them side by side was quick and easy. Morphing them together in an overlay or something like that is just not going to work. Putting them at the end, would be a little more difficult, but probably not impossible.
You have to reselect the item to get the icon to change. This is the same behavior as when you publish a package, it's icon does not update until you reselect the item. In both cases, it's not right.
The performance isn't the greatest, especially on Bundles. The problem is that CodeComponent has no compiledMethodsDo:, just an accessor. So you have to gather them all. And then enumerate them. For bundles, its even worse. That said, it makes it a little sluggish, it's not a killer.
I'd like to entertain retooling the test case icons. They're OK, but they don't differentiate the different states very well.
This begs more than ever the question of "when do you invalidate the visual indicators?" The current behavior (as the test methods themselves change) is worse and worse for this kind of a "global" indicator.
Previous Topic
