# Make fixing tests easier

**URL:** <https://discourse.julialang.org/t/make-fixing-tests-easier/101610>\
**Category:** VS Code\
**Created:** [July 14, 2023, 9:46am UTC](https://discourse.julialang.org/t/make-fixing-tests-easier/101610 "2023-07-14T09:46:23Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Impressium](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/impressium/32/19575_2.png) [@Impressium](https://discourse.julialang.org/u/Impressium)\
**Post date:** [July 14, 2023, 9:46am UTC](https://discourse.julialang.org/t/make-fixing-tests-easier/101610/1 "2023-07-14T09:46:23Z")

</div>

Hi all 🙂

I’m currently fixing lot’s of tests. It’s quite annoying xD

To questions:

- is there any UI to polish and sort the stack traces
- is there a setting in the test PKG to enable debug mode. So that at every error one only gets on stack trace with the current state of all the variables at that point? If not would that be a feature that we want to have?

Cheers

---

<div class="post-metadata">

**Author:** ![gdalle](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdalle/32/27854_2.png) [@gdalle](https://discourse.julialang.org/u/gdalle)\
**Post date:** [July 14, 2023, 10:02am UTC](https://discourse.julialang.org/t/make-fixing-tests-easier/101610/2 "2023-07-14T10:02:40Z")

</div>

Vis-à-vis stack traces, Julia 1.10 is substantially nicer than 1.9 thanks to shorter type printing. I would suggest you install the latest alpha version with [juliaup](https://github.com/JuliaLang/juliaup) and work on it. For even more conciseness, you can use [AbbreviatedStackTraces.jl](https://github.com/BioTurboNick/AbbreviatedStackTraces.jl).

Can’t help you with debug mode for tests, but I know that the [testitem](https://github.com/julia-vscode/TestItemRunner.jl) framework for VSCode makes it much faster to run and debug individual tests

---

<div class="post-metadata">

**Author:** ![oxinabox](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oxinabox/32/206603_2.png) [@oxinabox](https://discourse.julialang.org/u/oxinabox)\
**Post date:** [July 14, 2023, 11:40am UTC](https://discourse.julialang.org/t/make-fixing-tests-easier/101610/3 "2023-07-14T11:40:41Z")

</div>

using [TestEnv.jl](https://github.com/JuliaTesting/TestEnv.jl/) to interactively run tests in the REPL (vs-code or otherwise) is I find often a better way to fix tests.  
Since then you can inspect state like the current value of all variables interactively.

And you don’t need to run all tests to get to the one (or part of one) you are working on.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [July 14, 2023, 4:55pm UTC](https://discourse.julialang.org/t/make-fixing-tests-easier/101610/4 "2023-07-14T16:55:08Z")

</div>

Adding support for the full debugger and the ability to inspect state (i.e. variables) of individual test item runs are both things on my list that would be cool for test items in VS Code, but no promises when I will get to actually implementing that 🙂 If you had a choice, which one would you prefer first?

---

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [July 14, 2023, 5:17pm UTC](https://discourse.julialang.org/t/make-fixing-tests-easier/101610/5 "2023-07-14T17:17:33Z")

</div>

+1 for TestItems.jl, I think it is underappreciated.

---

<div class="post-metadata">

**Author:** ![mrufsvold](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mrufsvold/32/31600_2.png) [@mrufsvold](https://discourse.julialang.org/u/mrufsvold)\
**Post date:** [July 14, 2023, 6:21pm UTC](https://discourse.julialang.org/t/make-fixing-tests-easier/101610/6 "2023-07-14T18:21:36Z")

</div>

Deeeeebugger! That would be such a game changer. Also, thank you for all your work ☺

---

<div class="post-metadata">

**Author:** ![Impressium](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/impressium/32/19575_2.png) [@Impressium](https://discourse.julialang.org/u/Impressium)\
**Post date:** [July 16, 2023, 7:11am UTC](https://discourse.julialang.org/t/make-fixing-tests-easier/101610/7 "2023-07-16T07:11:06Z")

</div>

If I had the choice I would choose the debugger 🙂