# Best practice: modules and scripts for publishing

**URL:** <https://discourse.julialang.org/t/best-practice-modules-and-scripts-for-publishing/25375>\
**Category:** General Usage\
**Created:** [June 17, 2019, 5:02pm UTC](https://discourse.julialang.org/t/best-practice-modules-and-scripts-for-publishing/25375 "2019-06-17T17:02:31Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ffevotte](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ffevotte/32/6587_2.png) [@ffevotte](https://discourse.julialang.org/u/ffevotte)\
**Post date:** [August 22, 2019, 11:54am UTC](https://discourse.julialang.org/t/best-practice-modules-and-scripts-for-publishing/25375/7 "2019-08-22T11:54:36Z")

</div>

> [@BioTurboNick](#):
>
> Haven’t settled on how to run it though. I’m hesitant to use “runtests.jl” and `Pkg.test()` for anything other than unit testing.

I used to rely on `Pkg.test()`, which had the nice property of taking care of test-specific dependencies (or, in this case, use-case-specific dependencies, as opposed to dependencies required by the code under the ` src/` dir). However, I don’t think I would recommend (ab)using `Pkg.test()` any more for running plain use cases (as opposed to unit tests), especially since I [recently realized](https://discourse.julialang.org/t/benchmarking-and-pkg-test/27719) that `Pkg.test()` did a lot more than what I initially thought. In particular, it sets `--check-bounds=yes` , which is a very sensible thing to do for tests, but impacts the performance for “regular” use cases.

---

_[View the full topic](https://discourse.julialang.org/t/best-practice-modules-and-scripts-for-publishing/25375)._