Test: data breakpoints access types

[yannickowow]

Refs: #113922

• anyOS @gregvanl
• anyOS @alexr00

Complexity: 3
Authors: @yannickowow, @isidorn, @weinand

Create Issue

---

1. Clone https://github.com/microsoft/vscode-mock-debug, yarn and hit F5 to start running mock-debug in a new window out of source
2. New window opens with a test.md file. Press F5 now you are debugging the test.md file with mock-debug out of source.

Verify the following:

• You can see data breakpoints actions in the VARIABLES view context menu (Break When Value Is Read, Break When Value Changes, Break When Value Is Accessed)
• Data breakpoints get shown in the breakpoints view once you add them via these context menu actions
• Once a data breakpoint is set for a local mock debug variable, and the name of that variable appears in the .md file concatenated with "_" + accessType value, the breakpoint gets hit. For example for variable local_i you need local_i_read to appear in test.md for the read data breakpoint to be hit
• Data breakpoints can be disable / enabled / removed like all other breakpoints

Example 1

• Right click on local_i
• Select Break When Value is Read
• Right click on local_f
• Select Break When Value Is Accessed
• Continue execution
• Expect debuggee stops at each line containing local_i_read
• Expect debuggee stops at each line containing local_f_readWrite
• Finish debuggee

Example 2

• Disable breakpoint on local_i
• Continue execution
• Expect debuggee does not stop at line containing local_i_read
• Expect debuggee stops at each line containing local_f_readWrite

[alexr00]

Tested using Windows.

[gregvanl]

Tested on Linux Debian