# VS Code: clickable paths for unit test failures

**URL:** <https://discourse.julialang.org/t/vs-code-clickable-paths-for-unit-test-failures/130000>\
**Category:** General Usage\
**Tags:** testing, vscode\
**Created:** [June 18, 2025, 6:32pm UTC](https://discourse.julialang.org/t/vs-code-clickable-paths-for-unit-test-failures/130000 "2025-06-18T18:32:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ken\_Williams](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ken_williams/32/5289_2.png) [@Ken\_Williams](https://discourse.julialang.org/u/Ken_Williams)\
**Post date:** [June 18, 2025, 6:32pm UTC](https://discourse.julialang.org/t/vs-code-clickable-paths-for-unit-test-failures/130000/1 "2025-06-18T18:32:31Z")

</div>

In VS Code, having clickable and color-highlighted paths for stack traces is incredibly helpful in the REPL and some other contexts - but unfortunately for unit test failures (when running from the Testing pane), the error output is just plain-text with no highlighting or clickability.

Does anyone have a technique for navigating stack trace output in failing unit tests and getting to various level in the stack for where the error happened?