If I were seeing a lot of action, I wouldn't be wondering...
And if I'm running this for the first time, I probably won't have a progress bar.
It can be really hard to tell that iTest is doing anything. As I said, the only reliable indicator is that the green triangle has turned into a red square. In all that screen real estate, not exactly something that jumps out!
Interestingly, we're working now on an updated execution model for our next release. And our plan is to further integrate into Eclipse's standard model for executions (of any kind).
In this new model, there will be the difference between "run" and "debug". Run will run things exactly as they would run when executed in a back-office (headless) regression. That means that they'll run at full speed and without any UI stuff. Debug will be similar to what we have today -- in the sense that you can use breakpoints, single-step, etc. In the Eclipse model, there is a view that shows you a list of all of the running processes that have been launched. But in Eclipse's case, they also don't attempt to show you where you are in the middle of execution until you pause.
I recognize that, especially for former FanfareSVT users who were used to seeing that pointer move through the steps in a test case as it is executing, it can be frustrating not being able to see where you are in real time. The problem with the FanfareSVT model is that it limits you to a single thread. iTest is inherently multi-threaded, and then you face the question of how to show progress across a possibly large number of threads.
So perhaps we can consider an additional view that will list progress in real time for each of the threads, so that you can see what each thread is doing -- even while the threads are running.
No one has followed this question yet.