21d9945ba9
Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test).
20 lines
608 B
Plaintext
20 lines
608 B
Plaintext
# "make test" sets up the dummy add-on scripts required for these tests
|
|
|
|
#XXX these don't obey shelltest -w, always running the hledger executable in PATH
|
|
|
|
# 14. flags after an add-command are handled by the add-on
|
|
PATH=$PATH:. hledger addon --help
|
|
>>> /hledger-addon/
|
|
>>>=0
|
|
|
|
# 15. add-on flags which are not also defined in the main executable are a problem
|
|
PATH=$PATH:. hledger addon --addonflag
|
|
>>>2 /Unknown flag: --addonflag/
|
|
>>>=1
|
|
|
|
# 16. hledger main executable ignores anything after -- (and hides the -- from the add-on)
|
|
PATH=$PATH:. hledger addon --help -- --addonflag
|
|
>>> /hledger-addon/
|
|
>>>=0
|
|
|