-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right way to pass LocalPreferences.toml to VSCode test environment? #86
Comments
I have the same problem. What I did (as a workaround) was to put the preferences inside [deps]
...
Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40"
TestItemRunner = "f8b46487-2199-4994-9208-9a1283c18c0a"
TestItems = "1c621080-faea-4a02-84b6-bbd5e436b8fe"
[preferences.MyPkg]
variable = something This is not ideal, as it cannot be .gitignore'd, but is the only solution I found to work for the VSCode tests and also |
Thanks! TIL you can set Preferences in the Project.toml. |
There was a bug in the VS Code extension runner where it didn't pick up your local env. I just fixed that in the prerelease of VS Code. I'm not sure whether that will also fix this issue here, but worth trying. Could you give it a shot? |
I just tried the VS Code extension 1.114.1 (pre-release), and I am still observing the same problem ( |
Ok, this is actually an upstream problem: JuliaTesting/TestEnv.jl#59 |
It seems like the VSCode test runner is unaware of the LocalPreferences.toml in my base directory. Is there any way I should be declaring it? I tried putting it in
test/
too but no luck.For the record,
test/LocalPreferences.toml
works if I'm running withPkg.test()
. But the VSCode test runner doesn't seem to use it?The text was updated successfully, but these errors were encountered: