I actually side with Ralph on this one. It is very satisfying to see  
the test runner turn green. With tests in the image that you cannot  
fix, you will never get this satisfaction.

You should get used to using the bug tracker. If you have a little  
time to spare, go there, pick an issue that looks interesting or  
easy, fix it. Or better yet, write a test for it if there is none,  
run it, then fix it, and enjoy the soothing green of the test run.  
It'll make you smile :)

- Bert -

On Jan 29, 2007, at 18:11 , Keith Hodges wrote:

> Dear Goran,
>
> I am with you on this one. Having broken tests visible, but  
> correctly categorised is key to getting things sorted IMHO. I dont  
> think that hiding things away on mantis is not visible enough.
>
> You might like to try my improvements to TestRunner and SUnit which  
> implement these changes. You can try it by executing.
>
> Installer fixBug: 5639.
>
> best regards
>
> Keith
>> Ok, IMHO this is all about classification of tests. Perhaps  
>> someone has
>> already proposed the following but how about:
>>
>> - If there is a bug and someone authors a test to show it and it  
>> enters
>> the image (lets ignore *that* particular question for 3 seconds -  
>> many of
>> course argue that it should not enter the image unless accompanied  
>> with a
>> fix), why not mark it as "has never worked" - or something along  
>> those
>> lines?
>>
>> That way we can keep all *working* (not marked) tests green and at  
>> the
>> same time have a list of non working tests (those marked) that  
>> typically
>> are all red. When something is fixed and turned green we remove the
>> marker.
>>
>> Sure, this may be a daft idea :), just wanted to mention it.
>>
>> regards, Göran
>