The combination of this startup.jl and the develop.jl script will allow you to "virtually" add Revise to your project (without actually touching your Project or Manifest), and using it to quickly develop and run tests.
Run julia in this root folder and include("update.jl"). It will copy and REPLACE (WARNING!!) your startup.jl and the develop.jl script.
Append-to or replace your ~/.julia/config/startup.jl with the one from this repo.
Make the folder ~/.julia/scripts/ and (re)place develop.jl in it.
Start julia in the project/environment folder you're developing, or activate it, so typically run julia --project=., if your terminal is already there.
Then, first thing, run activate_dev(). It makes a new test environment in your temp folder and activates it. It will be based upon the current Manifest and Project, but will add Revise and the [test] dependencies as well. Also, it will call using Revise for you and move the current dir to the test folder in your project.
Now, you can directly call include("runtests.jl") rather than test YourPackage - the latter will need to recompile the lot from scratch every time, but the former will, thanks to Revise, only recompile the bits that changed! Your tests will run WAY faster (the second+ time you run them) and still will truly test you latests changes!
Now you can develop FAST! And temporarily and quickly uncomment/comment bits and pieces in your runtests.jl while you're still in the hacking stage! And any test function defined in runtests.jl stay available at the REPL while working our your code.
- Make
update.jlnot forcefully replacestartup.jlbut add (and replace) only a part of thestartup.jl. E.g. by adding/replacing a recognizable code block. - This tool does not yet recognize a Project.toml and/or Manifest.toml in the
/testsubfolder of a project. It should. - Any
[compat]blocks should also be copied and would currently cause an issue.