# How to debug exception triggered by unit test in VSCode

**URL:** <https://discourse.julialang.org/t/how-to-debug-exception-triggered-by-unit-test-in-vscode/90438>\
**Category:** VS Code\
**Tags:** debugger\
**Created:** [November 18, 2022, 11:39am UTC](https://discourse.julialang.org/t/how-to-debug-exception-triggered-by-unit-test-in-vscode/90438 "2022-11-18T11:39:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [November 20, 2022, 6:12pm UTC](https://discourse.julialang.org/t/how-to-debug-exception-triggered-by-unit-test-in-vscode/90438/2 "2022-11-20T18:12:26Z")

</div>

It appears that pressing `Step-Into (F11)` and then `Continue (F5)` when at the original call stack of the above screenshot brings us to the line of `f` that originally creates the exception.

For this to work “BREAKPOINTS → All Exceptions” has to be enabled.

Is this expected behaviour?

---

_[View the full topic](https://discourse.julialang.org/t/how-to-debug-exception-triggered-by-unit-test-in-vscode/90438)._