How to debug

You can launch the debugging process for 3 purposes:

• debug any unit test,
• debug any existing Debug Log file,
• debug any Anonymous Apex file.

When you start debugging, The Welkin Suite turns to the Debug mode, and the Debugger's caret is placed on the first line of the execution flow. In addition, your opened file in the editor is locked when you starting the debugging it. Thanks to this, you can easily avoid any unexpected changes caused by a system process, for example.

Using the Debug panel, you can easily navigate through the execution process: you can Continue or Stop Debugging, or you can execute the debugging process step-by-step and be managing each stage.

Here in the lower part of the TWS window, in the Debug mode, are the necessary panels that help you to get all the important information from the debugging process and solve your issues:

• Breakpoints — a list of all the breakpoints in your project and the ability to manage them,
• Locals — a list of all local variables in the active part of the code and all the information regarding to and depending on them,
• Call stack — all the information about the way of the execution,
• Output — the panel with all system messages about the debugging process.

When the debugging process is finished, you will see the corresponding message in the Output Panel.

The message code 0 (0x0) means that the debugging process was executed without errors. This message concerns only to the debugging process, not to the code execution itself.