Table of Contents
Moving through the debugging process often leads you to other test methods or files, so you have a way with complicated the nesting levels. To find where you are now and what was your path, for instance, what operation called the current test, you can use the Call stack panel in the right bottom corner in the Debug mode.
In this panel, you can see all the information about calls:
- Name — the name of the string. It consists of the file name and the number of the line with this string.
- Language — the language of the string.
You can manage, which data related to the call, should be displayed, using the context menu of the panel.
Navigation through the call stack
You can use any item in the Call stack panel to navigate to it in the code.
All the strings are displayed in descending historical order — this means that your current position is at the top of this list. It's marked by a yellow arrow in the left margin. If you double-click on any item where you want to move, the code in the editor will be focused on this part (and the necessary line in the code will be highlighted).
At the same time, near this string in the Call stack panel, you will see a grey arrow.
This option allows you to make clear what caused the moving to a deeper level. When you move to the previous level (using the Step out option), the call stack removes the deeper levels from the list.
The context menu of the Call stack panel
You can resume the execution of your code from the exact statement to the selected statement using the Call stack panel. To do this, right-click on the necessary line in the Call stack panel and select the Go To Source Code option.
In addition, you are able to set a breakpoint at the line with the call from the Call stack panel.
However, you might notice, that some parts of execution flow do not appear in the Call stack panel. See more about this in the Known limitations section.
In this section:
This also may be useful: