Hi Joseph,

Thank you for your question.

This is not the bug in the debug engine.

This message informs you that the debugging process for your unit test is finished. It has gone through your test and if there are other tests in the same class, you should launch debug process for them separately.

The code 0 (0x0) means that this process was finished without errors.

If you have more questions - feel free to ask, we will be glad to answer them.

Regards,

Kate

Hi Kate, 

Thank you for the quick response! Ok, that helped. I figured it out now. There were two things that were throwing me off:

1. If you use the "Step Over" debug command the breakpoints in methods are not causing the debugger to break. you have to use the "Continue" debug command. This is different than how standard Visual Studio Debugger works. (And I prefer the standard way)
2. Even though the test method ended on an error (System.DmlException: Insert failed) the debugger gave no indication that there was an error or what type of error it was. I realize now that the exit code of the debugger is referring to errors in the debugger and not in the test method, but it would be helpful if the debugger displayed the exception that occurred in the code.

Thank you again! I really am enjoying using it! 

Joseph

Hi again Joseph,

Thank you for your contribution.

1. This is really the bug. Our team will fix it and we will release this fix as soon as possible.

2. You understand everything correct. Currently the Apex Retrospective Debugger returns the error related to the debugger process. Your suggestion is very useful and it is already present on our agenda. Our team will implement this during the work on the improvements of the debugger.

We appreciate all your comments!

Regards,

Kate

Hi Joseph,

I want to inform you that our team released the new version of The Welkin Suite yesterday. This is 0.28.2 version.

The issue related to the missed breakpoints in the methods is solved.

In addition, we've implemented the tracking of exceptions in your custom executed code. You have an ability to get information about all the handled and unhandled errors which are caught during the Debugging process.

Please let us know if you will have new issues or suggestions.

Thank you,

Kate