Re: Run tests with "auto-prove"

"The idea of it is that if you're working in "my-code/lib/Foo/Bar/", you don't want to chdir all the way back to "my-code/" before you run your test suite."

Why? Just run two terminals -- one to run tests and run to edit. There are so many better ways to solve the problem of running your test suite while you "jump around" inside the source tree -- pushd and popd come to mind as well. I am curious as to how much time it took you to write this and contrast with how much time this actually saves you.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Comment on Re: Run tests with "auto-prove" Select or Download Code

Replies are listed 'Best First'.
Re^2: Run tests with "auto-prove" by tobyink (Canon) on Feb 29, 2012 at 23:07 UTC
Who says I'm even running one terminal? I often run auto-prove straight from my text editor. Many text editors and IDEs allow you to launch external commands like compilers, syntax checkers, etc.	[reply]
Re^3: Run tests with "auto-prove" by Anonymous Monk on Mar 01, 2012 at 18:27 UTC
`alias autoprove="pushd /path/to/dist; prove -Ilib t; popd"`	[reply] [d/l]