Test: condition editing for exception breakpoints

[isidorn]

Refs: #111227

• anyOS @sbatten
• anyOS @alexr00

Complexity: 3

Authors: @weinand, @isidorn

Create Issue

---

We have added a new debugger feature to edit conditions for exception breakpoints. Currently no "real" debug adapter supports this but some extensions plan to jump on this soon.

In order to be able to test the new feature, we've enhanced Mock Debug to support the feature in the following way:

If a line contains the word exception or the pattern exception(name) an exception is thrown.
To make the debugger stop when an exception is thrown, two "exception options" exist in the BREAKPOINTS view:

• Named Exception: if enabled and configured with a condition (e.g. xxx) the debugger will break on the exception(xxx) pattern.
• Other Exceptions: if enabled the debugger will break on the word exception and the exception(...) pattern if not matched by "Named Exception".

Just install Mock Debug version 1.45.2.

Then create a markdown file in VS Code, e.g. this readme.md:

The first line.

If a line contains the word exception or the pattern exception(name) an exception is thrown.

Another named exception(foo).

Open this file in VS Code, set a breakpoint on the first line, and start debugging by pressing the Debug button in the editor's toolbar.

Once debugging has started and you've hit the breakpoint verify:

• The BREAKPOINTS view shows two exception options:
  
• You can use the context menu action Edit Condition... on "Named Exception" to get an inline input box where you can enter a condition
• "Other Exceptions" does not provide the context menu action
• Once an exception breakpoint has a condition it is rendered next to it. Hover over the condition also shows it
• After pressing the Continue button you should break on the exceptions
• If you reload VS Code or restart the debug session the exception breakpoint condition is preserved
• You can edit the condition again to remove it

Please note: Focus on the UX experience; whether the condition is actually respected correctly by Mock debug is not important.