You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an F♯ project being tested via xunit.v3 (tests also written in F♯), breakpoints aren't respected. The test runs with correct output, the debugger attaches to the running test process and shows some threads, but breakpoints aren't hit. When the test starts, my breakpoint goes empty/gray like you expect, and then it seems to get resolved (turns back red), and it even moves a line because of where executable code is, but it never actually pauses execution.
This was working with xunit v2, but I have no idea what the difference is as it might pertain to the debugger.
Expected behaviour
The debugger pauses execution on a breakpoint as expected
Machine info
OS: Windows 11
.NET SDK version: [e.g. 8.0.403]
Ionide version: 7.21.2
I'm happy to gather whatever information might be useful; I just can't post the complete sources.
The text was updated successfully, but these errors were encountered:
Describe the bug
In an F♯ project being tested via xunit.v3 (tests also written in F♯), breakpoints aren't respected. The test runs with correct output, the debugger attaches to the running test process and shows some threads, but breakpoints aren't hit. When the test starts, my breakpoint goes empty/gray like you expect, and then it seems to get resolved (turns back red), and it even moves a line because of where executable code is, but it never actually pauses execution.
This was working with xunit v2, but I have no idea what the difference is as it might pertain to the debugger.
Expected behaviour
The debugger pauses execution on a breakpoint as expected
Machine info
I'm happy to gather whatever information might be useful; I just can't post the complete sources.
The text was updated successfully, but these errors were encountered: