# When to migrate to 1.2-style test-specific dependencies

**URL:** <https://discourse.julialang.org/t/when-to-migrate-to-1-2-style-test-specific-dependencies/28205>\
**Category:** Internals & Design\
**Tags:** question\
**Created:** [August 30, 2019, 11:07am UTC](https://discourse.julialang.org/t/when-to-migrate-to-1-2-style-test-specific-dependencies/28205 "2019-08-30T11:07:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [August 30, 2019, 11:07am UTC](https://discourse.julialang.org/t/when-to-migrate-to-1-2-style-test-specific-dependencies/28205/1 "2019-08-30T11:07:59Z")

</div>

Are the semantics for [test-specific dependencies with `test/Project.toml`](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Test-specific-dependencies-in-Julia-1.2-and-above-1) still being finalized?

Who should migrate at this point? (eg adventurous users who don’t mind if things break or change, or more conservative ones who just like the new feature, etc)

Does using this feature implicitly mean dropping CI support for 1.0 or 1.1?

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [August 30, 2019, 11:18am UTC](https://discourse.julialang.org/t/when-to-migrate-to-1-2-style-test-specific-dependencies/28205/2 "2019-08-30T11:18:25Z")

</div>

> [@Tamas\_Papp](#):
>
> Are the semantics for [test-specific dependencies with `test/Project.toml`](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Test-specific-dependencies-in-Julia-1.2-and-above-1) still being finalized?

Yes, as stated in the note in the docs the interaction between `Manifest.toml` and `test/Manifest.toml` are not quite finalized. I would consider this feature beta until we have solved [Proposal for "sub-projects". · Issue #1233 · JuliaLang/Pkg.jl · GitHub](https://github.com/JuliaLang/Pkg.jl/issues/1233).

> [@Tamas\_Papp](#):
>
> Who should migrate at this point? (eg adventurous users who don’t mind if things break or change, or more conservative ones who just like the new feature, etc)

Feel free to try it out, it should work, and in particular it is very useful to easily simulate the test-environment, e.g. [Making test dependencies available at the REPL · Issue #1008 · JuliaLang/Pkg.jl · GitHub](https://github.com/JuliaLang/Pkg.jl/issues/1008)

> [@Tamas\_Papp](#):
>
> Does using this feature implicitly mean dropping CI support for 1.0 or 1.1?

No, Julia 1.0 and 1.1 will still use `[targets]`, but then you will have to maintain both `test/Project.toml` and `[targets]` then.

---

<div class="post-metadata">

**Author:** ![ssfrr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ssfrr/32/3736_2.png) [@ssfrr](https://discourse.julialang.org/u/ssfrr)\
**Post date:** [August 30, 2019, 6:29pm UTC](https://discourse.julialang.org/t/when-to-migrate-to-1-2-style-test-specific-dependencies/28205/3 "2019-08-30T18:29:32Z")

</div>

I wasn’t aware this change was happening - just want to say it seems like a very slick way to go. I like that when writing your tests you just plop yourself into the `MyPkg/test` environment and then you can add/remove packages easily from the `pkg>` prompt, and run code from Juno, etc. Seems very simple and understandable.

---

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [August 30, 2019, 7:11pm UTC](https://discourse.julialang.org/t/when-to-migrate-to-1-2-style-test-specific-dependencies/28205/4 "2019-08-30T19:11:19Z")

</div>

FYI, I wanted to use `test/Project.toml` in Julia \< 1.2 so I wrote [Run.jl](https://tkf.github.io/Run.jl/dev/). I find other sub-projects like `docs/Project.toml` and `benchmarks/Project.toml` pretty useful too.