Test Pane should show what's actually happening
Currently the test pane only shows the output that specific commands write, but if a command isn't writing anything, there's no way to know where in the script the problem is occurring. Similarly with issues, if something is endlessly looping, there's no way to know what or if it's just very slow.
The test pane should either be a proper step through of the script (highlighting the running command along with the output) or show it like the commands were typed into the PowerShell window itself.
Thanks for posting this suggestion!
There are a couple of existing features that may get you most of what you are looking for.
1. While we do not have a debug mode where you can step through your runbook and see output, we do have an Add-On for the ISE and you can debug your runbooks in the ISE. http://www.powershellgallery.com/packages/AzureAutomationAuthoringToolkit/0.2.3.1
2. If you are using graphical runbooks, there are settings that you can turn on to show exactly what is happening and what command ran with it by turning on additional logging. Select your graphical runbook > Settings > Logging and Tracing > turn on Verbose and change Trace Level to detailed to get the level of detail you are looking for.
3. For scripts, you can set your verbose preference to continue (instead of silentlycontinue) in your runbook to debug and write to the verbose stream. $VerbosePreference = ‘Continue’ in your runbook. You may be interested in this article as well to learn more about controlling streams: https://azure.microsoft.com/en-us/blog/azure-automation-controlling-runbook-streams-for-testing-and-troubleshooting/. If you are using the portal authoring pane to test your runbooks, this is the suggested way to test.
It would be great to hear your feedback on whether or not these solutions fit your needs once you have a moment to test. Please post back your comments so we can make sure that the authoring user experience fits your needs. Thanks!
Adrian Walker commented
It's a "TEST" pane. Verbose should be on by default.