Virgil Dupras a034f63e23 test: begin adding common test harnessing code ... This should make tests a bit more convenient to write and debug. Moreover, begin de de-IX-ization of parseExpr. I have, in a local WIP, a parseExpr implemented using a recursive descent algo, it passes all tests, but it unfortunately assembles a faulty zasm. I have to find the expressions that it doesn't parse properly. But before I do that, I prefer to commit these significant improvements I've been making to tests harness in parallel of this development.		2019-12-23 15:41:25 -05:00
..
runtests.sh	test: begin adding common test harnessing code	2019-12-23 15:41:25 -05:00
test_basic_parse.asm	test: begin adding common test harnessing code	2019-12-23 15:41:25 -05:00
test_core.asm	test: begin adding common test harnessing code	2019-12-23 15:41:25 -05:00
test_ed_util.asm	core: remove cpHLDE	2019-12-12 15:53:14 -05:00
test_expr.asm	test: begin adding common test harnessing code	2019-12-23 15:41:25 -05:00
test_lib_ari.asm	lib/expr: refactor for easier operator addition	2019-11-22 14:45:12 -05:00
test_lib_fmt.asm	basic: add puth command	2019-12-09 14:34:14 -05:00
test_parse_z.asm	Make the shell a userspace app	2019-11-15 15:37:49 -05:00
test_parse.asm	Make the shell a userspace app	2019-11-15 15:37:49 -05:00
test_symbol.asm	Extract str.asm from core.asm and make core included by userspace	2019-11-14 10:14:15 -05:00
test_util_z.asm	lib/expr: refactor for easier operator addition	2019-11-22 14:45:12 -05:00
test_z_instr.asm	zasm: little drive-by optimization	2019-12-13 10:54:01 -05:00