# Passing parameters to \`test\`

**URL:** <https://discourse.julialang.org/t/passing-parameters-to-test/16314>\
**Category:** General Usage\
**Tags:** testing\
**Created:** [October 14, 2018, 6:27pm UTC](https://discourse.julialang.org/t/passing-parameters-to-test/16314 "2018-10-14T18:27:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![djsegal](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/djsegal/32/13752_2.png) [@djsegal](https://discourse.julialang.org/u/djsegal)\
**Post date:** [October 14, 2018, 6:59pm UTC](https://discourse.julialang.org/t/passing-parameters-to-test/16314/3 "2018-10-14T18:59:58Z")

</div>

Also, might be kind of useful to check out this old post:

> [@Standard ways to run common commands](https://discourse.julialang.org/t/standard-ways-to-run-common-commands/154):
>
> Over the course of developing a project, there are certain commands that get executed all the time. These include running: Tests Subsets of tests The application’s main function How can we introduce standard ways to perform these functions? Also, a standard way to run functions would give: people a nice list of hooks to plug their initialization code. a way to warn people that their packages don’t meet REQUIRE specifications and other stuff

---

_[View the full topic](https://discourse.julialang.org/t/passing-parameters-to-test/16314)._