Several of our tests run for many hours. Naturally, we'd like to make them less time consuming and improve the turnaround for our user community.
It would be great if there was a tool which could identify what area's in each test was the biggest resource consumers (time, diskspace, etc). It would be a kind of "test profiler" in other words.
Does TC have such a capability, or an anyone offer any suggestions?