I am pleased to see you found some time to explore our forums as well and I will be happy to provide some additional information on the topic.
At first I would like to confirm that the request to implement breakpoints also for nested tests
is completed and available in the product since the beginning of this year. So, you will be able to use the Visual Debugger
against that parent test which only contains test as steps - set a breakpoint in the nested test, ensure you have set the debugger options
to stop in quick execution mode and run the test.
In addition to that you can use the partial execution options from the step context menu Run
... -> To Here, From Here, Selected steps
. So following the example you described, you can go for the following sequence of actions:
- open that parent test with two tests as steps
- here, you can either choose the first, or the second, depending on the current needs and then Run
... -> To Here
- this will trigger the test execution in the listed order and will run the steps until any of these fails, or the last step is executed. Then the recorded will be attached to the browser in its current state.
- here you can continue recording new steps - these will get recorded in the active test in the Test Studio project.
- or you can open any other test, which contains steps against that current state of the page and execute any of its steps using Run
... -> From Here, or Selected Steps.
- to get back to the example - let's the quick execution fails on the last step of the first sub-test, you can open that sub test in the Test Studio project and work directly on it and its elements against the current active recording session. Once you fixed that error, you can open the second sub-test to be active in the Test Studio project and continue the execution using Run
... -> From Here
again using the same active recording session.
I hope this will be useful for you as well. However, if you need any further assistance, please do not hesitate to get back to me.