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).
35 lines
620 B
Plaintext
35 lines
620 B
Plaintext
# a commodity may contain/end with numbers, if double quoted
|
|
# 1. without quotes, fail. XXX parse error should be clearer here
|
|
hledger -f- print
|
|
<<<
|
|
2010-04-05 x
|
|
a 10 DE0002635307
|
|
b
|
|
>>>2 /unexpected/
|
|
>>>= 1
|
|
# 2. with quotes, ok; quotes appear in print output
|
|
hledger -f- print
|
|
<<<
|
|
2010-04-05 x
|
|
a 10 "DE 0002 635307"
|
|
b
|
|
>>>
|
|
2010/04/05 x
|
|
a 10 "DE 0002 635307"
|
|
b -10 "DE 0002 635307"
|
|
|
|
>>>=0
|
|
|
|
# 3. and in other reports too, I guess
|
|
hledger -f- balance
|
|
<<<
|
|
2010-04-05 x
|
|
a 10 "DE0002635307"
|
|
b
|
|
>>>
|
|
10 "DE0002635307" a
|
|
-10 "DE0002635307" b
|
|
--------------------
|
|
0
|
|
>>>=0
|