izaya
/
collapseos
mirror of https://github.com/hsoft/collapseos.git
1
0
Fork 0
Code Issues Releases Wiki Activity
collapseos/tests/unit/runtests.sh

29 lines
504 B
Bash
Raw Normal View History

zasm: little drive-by optimization Use IX directly for argspec rows instead of going through DE. It saves a bit of processing. The code was this way because I initially didn't use IX at all, so as code evolved, that DE translation stayed as an artifact.
2019-12-14 02:23:11 +11:00
#!/usr/bin/env bash
set -e
# TODO: find POSIX substitute to that PIPESTATUS thing
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
Move "tests" folder to root
2020-01-01 05:07:05 +11:00
BASE=../..
Move "emul" folder to root
2020-01-01 05:32:09 +11:00
ZASM="${BASE}/emul/zasm.sh"
RUNBIN="${BASE}/emul/runbin/runbin"
zasm: includes CFS is now built on-the-fly by zasm.sh This makes for a much more usable zasm linux binary that doesn't have to be rebuilt every time apps or kernel change.
2019-06-03 09:54:37 +10:00
KERNEL="${BASE}/kernel"
APPS="${BASE}/apps"
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
zasm: clarify strlen's API
2019-07-23 23:28:39 +10:00
chk() {
echo "Running test $1"
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-24 07:41:25 +11:00
if ! ${ZASM} "${KERNEL}" "${APPS}" common.asm < $1 | ${RUNBIN}; then
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
echo "failed with code ${PIPESTATUS[1]}"
exit 1
fi
zasm: clarify strlen's API
2019-07-23 23:28:39 +10:00
}
Make makefiles and shell scripts portable It's no longer required to use `gmake` under OpenBSD and shell scripts no longer require bash.
2019-12-10 01:36:38 +11:00
if [ ! -z $1 ]; then
zasm: clarify strlen's API
2019-07-23 23:28:39 +10:00
chk $1
exit 0
fi
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-24 07:41:25 +11:00
for fn in test_*.asm; do
zasm: clarify strlen's API
2019-07-23 23:28:39 +10:00
chk "${fn}"
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 23:33:20 +10:00
done
echo "All tests passed!"