# Debugger doesn't stop at breakpoints when running tests (but does during normal execution)

**URL:** <https://discourse.julialang.org/t/debugger-doesnt-stop-at-breakpoints-when-running-tests-but-does-during-normal-execution/93202>\
**Category:** VS Code\
**Tags:** testing, debugging, vscode\
**Created:** [January 19, 2023, 9:14am UTC](https://discourse.julialang.org/t/debugger-doesnt-stop-at-breakpoints-when-running-tests-but-does-during-normal-execution/93202 "2023-01-19T09:14:15Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![nrontsis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nrontsis/32/38535_2.png) [@nrontsis](https://discourse.julialang.org/u/nrontsis)\
**Post date:** [February 22, 2023, 8:50am UTC](https://discourse.julialang.org/t/debugger-doesnt-stop-at-breakpoints-when-running-tests-but-does-during-normal-execution/93202/7 "2023-02-22T08:50:19Z")

</div>

[This](https://discourse.julialang.org/t/why-is-test-so-meta-programming-heavy/94619/32) is also related, I believe. It appears that the authors of the Julia VSCode plugin are already aware of the limitations in `debugging` while in `@testset`s, and focus is on the [new testitem framework](https://discourse.julialang.org/t/prerelease-of-new-testing-framework-and-test-run-ui-in-vs-code/86355).

---

_[View the full topic](https://discourse.julialang.org/t/debugger-doesnt-stop-at-breakpoints-when-running-tests-but-does-during-normal-execution/93202)._