Will gladly read some considered advice on this matter, probably no one
runs them as often as I do. 

Actually, I accepted the tests more or less as given. Some peeks have
led me to believe quite a bit of cruft has accumulated there, too -
suggestions/changesets welcome on this, too.

Some of the slowness, for example, comes from BrowserEnvironments, which
perform a global test that runs over the whole image. And that is done
many times (#universalTestFor). 

Alternatives?

Daniel

David Farber <dfarber at numenor.com> wrote:
> 
> Dean -- I think you are overstating the case against unit tests.
>  At the other end of the
>      spectrum, there is something /seriously/ wrong with the fact that it
>      takes over an /hour/ to run the Refactoring Browser tests. But slow
>      tests are better than no tests.
> 
> david
>