After working with this a little more, I'm finding that I'm still limited as to what I can do using separate files as part of the "Test as Step" feature/functionality.
As I noted in my last response, the "Run to Here" functionality works only on the Main script (i.e., it doesn't work if you've set that on a separate file that's being used in a "Test as Step" capacity). This is understandable, and am guessing due to the lack of persistence of "Run to Here" commands.
I am surprised that Breakpoints don't work on "Test as Step" files, given their persistence (i.e., they exist until the breakpoint is removed). In my case, I have a "main" script that calls a "Test as Script" file which contains a breakpoint. The main test successfully calls the Test as Script file, but when the line containing the breakpoint is executed, the breakpoint is ignored and the script continues to run to completion or until an error is encountered. Is this a bug, or is there a way for Test Studio to recognize the breakpoint in "Test as Step" files?
Also, I've found that files saved and run as "Test as Step" don't exihibit the same behaviors found when running a single, self-contained test file, or a "Main" file that contains "Test as Step" commands the references separate files. In the attached screenshot, I show how the editor window looks when showing the execution of the main file. It has a yellow header and icons showing the status of the run (Pass|Fail|Not Run). When I click down into the "Test as Step" lines, the subsequent edit windows don't render the headers or icons, making the debugging process more difficult than need be. The user can open the log file and work through that, but it would make for a more consistent user experience and assist with script debugging.
The screenshot illustrates the current behavior and how it might look if these elements were to cascade through all files or "Test as Step" commands.
1. The Pass|Fail|Not Run icons are not rendered as part of the test pass in the editing windows.
2. The yellow header showing the count of lines and lines executed is not rendered for these files.