TestEnv.jl
TestEnv.jl copied to clipboard
JuliaTesting
Activate your test enviroment, so you can use your test dependencies in the REPL
The test_env path is very cryptic. It would be great, if it could include `testenv` or some other explicit name, which makes it easy to check, whether we have already...
I think you can hook into / modify the package mode REPL, so it would be pretty awesome if I could put TestEnv in my startup.jl then have: ``` pkg>...
I would _love_ to use this in the VS Code extension, but the current model of having separate branches for different Julia versions won't work for us: we can only...
On Julia v1.8.0-RC1 I run into this (using the release-1.8 branch of TestEnv) when TestEnv is in my default "v1.8" instead of my active environment: ```julia julia> TestEnv.activate() ERROR: TypeError:...
On Julia 1.8-beta3, I always get the following warning: ``` julia> using TestEnv; TestEnv.activate() ┌ Warning: The project dependencies or compat requirements have changed since the manifest was last resolved....
I find this would solve my own use case related to #38 that creates a shared environment from a path with a little bit more code creating the `PackageSpec` and...
in v1.6: ```jl julia> TestEnv.activate() ┌ Warning: Could not use exact versions of packages in manifest, re-resolving └ @ TestEnv ~/.julia/packages/TestEnv/0IT5L/src/activate_set.jl:60 "/var/folders/hx/1h0bbkfd18d4n1qrnwmrl4j00000gn/T/jl_HNWFMu/Project.toml" julia> TestEnv.activate() ERROR: type Nothing has no field...
I think it would be much more convenient if one can pass a path instead of an available package name to create the test environment since `path` is a more...
I find currently because this package only registered on versions before 1.8, if a package CI uses this package on nightly then it would fail, any idea about setting up...
> Completely agree. Presumably the fact that it isn't hit in the existing tests means that a chunk of code doesn't get tested :( _Originally posted by @willtebbutt in https://github.com/JuliaTesting/TestEnv.jl/pull/28#discussion_r686808022_
Metadata
Owner
Metadata
Activate your test enviroment, so you can use your test dependencies in the REPL