hledger/tests/balance/depth.test

# 1.
hledger -f sample.journal balance --no-total --depth 1
>>>
                 $-1  assets
                  $2  expenses
                 $-2  income
                  $1  liabilities
>>>=0

# 2. Depth 0 aggregates everything into one line
hledger -f sample.journal balance --no-total --depth 0
>>>
                   0  ...
>>>=0

# 3. Ditto in a multi-column balance report.
hledger -f sample.journal balance -M -e 2008/4 --depth 0
>>>
Balance changes in 2008/01:

     || Jan 
=====++=====
 ... ||   0 
-----++-----
     ||   0 
>>>=0
balance, register, register-csv: depth 0 shows summary items (#206) Previously, a depth:0 query produced an empty report (since there are no level zero accounts). Now, it aggregates all data into one summary item with account name "...". This makes it easier to see the kind of data Gwern was looking for from register-csv (net worth over time). Eg this shows one line per month summarising the total of assets and liabilities: hledger register-csv -- -MHE ^assets ^liabilities depth:0 Single and multi-column balance reports behave similarly. 2014-10-20 04:53:20 +04:00			`# 1.`
tests: make functional tests use "hledger" again 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). 2015-07-12 21:54:08 +03:00			`hledger -f sample.journal balance --no-total --depth 1`
convert a few doctests to shell test format 2009-06-27 12:16:19 +04:00			`>>>`
			`$-1 assets`
			`$2 expenses`
			`$-2 income`
			`$1 liabilities`
update functional tests to shelltest 1.0 format 2011-08-15 02:15:39 +04:00			`>>>=0`
gather balance tests 2011-09-23 06:04:33 +04:00
balance, register, register-csv: depth 0 shows summary items (#206) Previously, a depth:0 query produced an empty report (since there are no level zero accounts). Now, it aggregates all data into one summary item with account name "...". This makes it easier to see the kind of data Gwern was looking for from register-csv (net worth over time). Eg this shows one line per month summarising the total of assets and liabilities: hledger register-csv -- -MHE ^assets ^liabilities depth:0 Single and multi-column balance reports behave similarly. 2014-10-20 04:53:20 +04:00			`# 2. Depth 0 aggregates everything into one line`
tests: make functional tests use "hledger" again 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). 2015-07-12 21:54:08 +03:00			`hledger -f sample.journal balance --no-total --depth 0`
balance, register, register-csv: depth 0 shows summary items (#206) Previously, a depth:0 query produced an empty report (since there are no level zero accounts). Now, it aggregates all data into one summary item with account name "...". This makes it easier to see the kind of data Gwern was looking for from register-csv (net worth over time). Eg this shows one line per month summarising the total of assets and liabilities: hledger register-csv -- -MHE ^assets ^liabilities depth:0 Single and multi-column balance reports behave similarly. 2014-10-20 04:53:20 +04:00			`>>>`
			`0 ...`
			`>>>=0`

			`# 3. Ditto in a multi-column balance report.`
tests: make functional tests use "hledger" again 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). 2015-07-12 21:54:08 +03:00			`hledger -f sample.journal balance -M -e 2008/4 --depth 0`
balance, register, register-csv: depth 0 shows summary items (#206) Previously, a depth:0 query produced an empty report (since there are no level zero accounts). Now, it aggregates all data into one summary item with account name "...". This makes it easier to see the kind of data Gwern was looking for from register-csv (net worth over time). Eg this shows one line per month summarising the total of assets and liabilities: hledger register-csv -- -MHE ^assets ^liabilities depth:0 Single and multi-column balance reports behave similarly. 2014-10-20 04:53:20 +04:00			`>>>`
			`Balance changes in 2008/01:`

update functional tests for new monthly headings 2018-03-29 16:54:36 +03:00			`\|\| Jan`
			`=====++=====`
			`... \|\| 0`
			`-----++-----`
			`\|\| 0`
balance, register, register-csv: depth 0 shows summary items (#206) Previously, a depth:0 query produced an empty report (since there are no level zero accounts). Now, it aggregates all data into one summary item with account name "...". This makes it easier to see the kind of data Gwern was looking for from register-csv (net worth over time). Eg this shows one line per month summarising the total of assets and liabilities: hledger register-csv -- -MHE ^assets ^liabilities depth:0 Single and multi-column balance reports behave similarly. 2014-10-20 04:53:20 +04:00			`>>>=0`