When a test is running, there doesn't appear to be any easy way of determining exactly what step is executing. I guess Console or Threads might tell you, but it would sure be nice if the current step you're executing was front-and-center, with a little arrow next to it. Kind of like what it looks like when you pause.
We used to do this in SVT - but it used to come at a
cost.It used to take 100% of the machine's CPU to show you the line of code which was getting executed. I do not think it makes sense. No IDE or execution environment will show you with a pointer or arrow which line of code is getting executed unless you are single stepping the line of code in debug mode. It is of limited value because that line or arrow will be changing at 100 steps per second - so you will be mostly seeing screen flash or like in SVT, the arrow was actually behind 1000 steps in painting and only when execution paused or stopped did the arrow actually catch up with the actual line of code.
Actually, threads doesn't do it. It seems to be at least one step behind. It claims I'm still in reboot_console, but I finished that step, and I'm trying to open a different device (according to Console).