When you include a test as a step into a higher level test, breakpoints in the inner test don't work.
This is very inconvenient when you want to execute a "tree" of tests and need to stop in one of the nested tests.
Posted on:17 Jan 2019 09:31
Breakpoints will now be respected during quick execution when in nested steps (test as step).
The change will be available with the next major release 2019.R1 (planned for first week of February).
This would be hugely valuable. Any plan to implement change?
Posted on:14 Jul 2017 15:08
Now 4 years old, really need this feature - not having it adds hours to my debugging.
Posted on:10 Jul 2017 13:28
This would be *really* useful.
Posted on:10 Oct 2016 13:41
This issue is more than 2 years old and it hasn't been addressed yet. How much longer is going to take to see this issue fixed?
Posted on:25 Feb 2014 16:18
I echo CTP Tester's comment. This has been a limitation of Test Studio ever since the early versions.
Currently we have to run shared tests standalone in order to debug issues in them. This, in turn, means implementing additional code (in the shared test) to get the application into the expected start state expected by the shared test. This additional code sometimes can be a significant number of lines of code and/or significantly higher running time before we get to the code where we want to debug.