The font size of the progress bar automatically adjusts itself to fill the largest space you're able to give it - so I'm not sure if I could make it any bigger without redesigning the entire gadget ... although, there is some work I'm expecting to release soon that will involve a more compact version bolted onto the VS status bar. The risk/progress bar itself was a bit of a failed experiment, but the nice thing about experiments is that you learn from them :)

Thanks for the feedback - I'll take a look at it :)

Good thinking - removing those bevels makes an amazing difference... I'll see what I can do here.

Sadly replacing the express tree with a ListView isn't an option. The express tree has a huge range of features that really are necessary to be able to display the tests in a meaningful way. Something that many people aren't aware of is that I actually went through several iterations of the Tests Window before ending up with this layout (this is iteration number 4). I tried a number of different controls (including the listview) and found them all to be either too slow or missing in features that were critical to the layout of the window.

I'm wondering if you might be able to share any details about the sort of information you're using the Tests Window to keep track of while you're coding. It's apparent to me that you're using the window as a way to keep tabs on the status of the NCrunch engine, and there is a feature I have in progress for 1.38b that sits in this general area ... aside from the obvious (knowing when you have a failing test), what are the main pieces of information you are seeking from the Tests Window while you work?

Oh, sorry.. I misunderstood :)

Let me know if you have any more thoughts in this area. I'm keen to find ways of letting people work without needing to keep the Tests Window open, as not everyone has the screen space to do this.