Test: noDebug and compact debugSessionOptions flags finalized

[isidorn]

Refs: #99743
Refs: #100852

• anyOS: @weinand

Complexity: 3

Create Issue

---

We have finalized the new noDebug and compact flag to the debugSessionOptions API. So get a VS Code starter extension that only uses the final api (not proposed), call the startDebugging api and pass the DebugSessionOptions such that you can verify the noDebug and compact flag work as expected:

• if noDebug is present and set to true, no breakpoints should be hit when running the program
• if noDebug is set to false, breakpoints should be respected and hit
• if noDebug is not set the sessions should respect whatever was set to its parent session (if it exists).
• if noCompact is present and set to true, the session shuold never be compacted with it's parent session
• if noCompact is set to false or not set at all the session should be compacted with it's parent session
• When sessions are compacted they are displayed as one element in the CALL STACK view

Note: a simple way to use the startDebugging api is to simply pass the workspace folder and the name of an already existing launch configuration in your launch.json.

[weinand]

Both flags work fine.