# How do I activate the test environment of a package?

**URL:** <https://discourse.julialang.org/t/how-do-i-activate-the-test-environment-of-a-package/86740>\
**Category:** Package Management\
**Created:** [September 3, 2022, 7:09pm UTC](https://discourse.julialang.org/t/how-do-i-activate-the-test-environment-of-a-package/86740 "2022-09-03T19:09:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jlperla](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jlperla/32/34332_2.png) [@jlperla](https://discourse.julialang.org/u/jlperla)\
**Post date:** [September 6, 2022, 4:30pm UTC](https://discourse.julialang.org/t/how-do-i-activate-the-test-environment-of-a-package/86740/4 "2022-09-06T16:30:36Z")

</div>

> [@ufechner7](#):
>
> Try [GitHub - JuliaTesting/TestEnv.jl: Activate your test enviroment, so you can use your test dependencies in the REPL](https://github.com/JuliaTesting/TestEnv.jl)

Yup, this is the winner for sure, and doesn’t require **any** non-dev tool packages in your global environment. [How to use VSCode and REPL to write and test a package? - #4 by jlperla](https://discourse.julialang.org/t/how-to-use-vscode-and-repl-to-write-and-test-a-package/78818/4) writes up what I found to be the easiest workflow. If a package doesn’t have a `test/Project.toml` but has it embedded in the main Project file, I think TestEnv is still supposed to work.

---

_[View the full topic](https://discourse.julialang.org/t/how-do-i-activate-the-test-environment-of-a-package/86740)._