Debugging with breakpoints is a powerful technique that you can use to find a source of the problem in your applications. However, it is also useful to check its execution line by line. Of course, such a task can be accomplished by placing a breakpoint in each line, but this may be cumbersome for a developer. For this reason, this recipe will show you how to debug the application with step-by-step debugging.
To complete this recipe, you need the project with two pages, represented by the MainPage
and ProductsPage
classes. It is necessary to pass a category identifier while navigating from MainPage
to ProductsPage
. You should start the debugging of the project and stop it at any breakpoint.
To perform the step-by-step debugging, you need to perform the following steps:
To execute a single line and stop in the following line, press F10 or click on the Step Over icon in the toolbar. As a result, the next line will be marked with the yellow background, as shown in the following screenshot.
To step into a method that is called within the line, where debugging has stopped, press F11 or click on the Step Into icon in the toolbar.
To go to the line where the cursor is currently located, press Ctrl + F10 or choose the Run To Cursor option from the context menu of the line with the cursor.
The values of variables can be checked in a few ways, such as by placing the cursor over the name of the variable. However, when you want to see the values of a few variables in the following iterations within a loop, it is much more convenient to pin tooltips with their current values so they are automatically refreshed in each iteration. You can pin the tooltip by placing the cursor over the name of the variable and then pressing the pin icon. The exemplary result is shown in the preceding screenshot.
The Breakpoint-based debugging recipe
The Executing code while debugging recipe
The Logging information while debugging recipe
The Creating a unit test and Running a set of tests recipes in Chapter 9, Testing and Submission