After Silk Test Workbench encounters a playback error, the Silk Test Workbench Playback Error dialog box opens and provides the option to enter Debug mode. In Debug mode, playback is suspended, which allows you to diagnose and fix any playback errors using the Silk Test Workbench debugging features.
In this section of the lesson, you will learn how to debug the error that occurred during playback of the modular test in the previous section.
In Debug mode, playback is suspended. This allows you to fix the error by either editing the properties of the step incurring the error, deleting the step, disabling the step, or copying and pasting a step from another visual test before resuming playback.Silk Test Workbench enters Debug mode and displays the AddAccount visual test with the step incurring the error highlighted in yellow.
Step Into is useful for detailed analysis of a test, and lets you see the effect of each step on variable usage and test application interaction.
Using Step Over at a step other than one that plays back another visual test or script has the same effect as using Step Into. Only the next step executes before playback suspends and re-enters debug mode.
Use Step Out when playback is suspended at a step in a visual test or code line that has been inserted in another visual test, and you want to playback the remaining visual test or script and return to the original visual test. When playback executes the remainder of the inserted script or visual test, it suspends and re-enters debug mode at the next sequential line in the original visual test.
Use Run To Cursor to playback the visual test or script and stop playback at a point just before a run-time error occurs. This lets you stop playback at a specific line or statement without having to insert breakpoints. Once playback stops, you can continue using one of the other debug options.
Next, you learn how to monitor the values of variables used in the visual test.