David Anthoff
David Anthoff
Hm, I'm confused, to be honest :) In particular, I don't understand > I am using @testitem inside Pluto such that I run the content only when being inside Pluto...
Ah, ok. To be honest, I think that just sounds like a different test framework, and it might be better to just keep these separate? It sounds like the semantics...
If we can make this work, great! But I think `let` just doesn't provide the level of separation between different test items that we assume right now, really the design...
Couldn't you just replace the `begin` `end` block that is passed to the macro with a `let` block in the macro if you want to do that? Or even better,...
You could still just put it into a `let` block in your macro, right?
I'm going to close this for now. In my mind the module-per-testitem is really core to the design.
Quick brain dump on my current thinking for this: # Test snippet The first case is simply code that we want to reuse at the global scope inside a `@testitem`....
I hadn't thought about that, could you open a new issue that tracks that?
We create a new module every time you run a test, and I think they stick around... I think (but not sure) there is no way in Julia to unload...
So I don't think we can fix this: when you send a macro like `@run_package_test` to the VS Code REPL it _also_ sends the file in which that was written...