collapseos/tests/unit/runtests.sh

#!/usr/bin/env bash
set -e
# TODO: find POSIX substitute to that PIPESTATUS thing

BASE=../..
TOOLS="${BASE}/tools"
ZASM="${TOOLS}/zasm.sh"
RUNBIN="${TOOLS}/emul/runbin/runbin"
KERNEL="${BASE}/kernel"
APPS="${BASE}/apps"

chk() {
    echo "Running test $1"
    if ! ${ZASM} "${KERNEL}" "${APPS}" common.asm < $1 | ${RUNBIN}; then
        echo "failed with code ${PIPESTATUS[1]}"
        exit 1
    fi
}

if [ ! -z $1 ]; then
    chk $1
    exit 0
fi

for fn in test_*.asm; do
    chk "${fn}"
done

echo "All tests passed!"
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-13 10:23:11 -05: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 09:33:20 -04:00
Move "tests" folder to root 2019-12-31 13:07:05 -05:00			`BASE=../..`
			`TOOLS="${BASE}/tools"`
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-02 19:54:37 -04:00			`ZASM="${TOOLS}/zasm.sh"`
			`RUNBIN="${TOOLS}/emul/runbin/runbin"`
			`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 09:33:20 -04:00
zasm: clarify strlen's API 2019-07-23 09:28:39 -04: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-23 15:41:25 -05: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 09:33:20 -04:00			`echo "failed with code ${PIPESTATUS[1]}"`
			`exit 1`
			`fi`
zasm: clarify strlen's API 2019-07-23 09:28:39 -04: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-09 09:36:38 -05:00			`if [ ! -z $1 ]; then`
zasm: clarify strlen's API 2019-07-23 09:28:39 -04: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-23 15:41:25 -05:00			`for fn in test_*.asm; do`
zasm: clarify strlen's API 2019-07-23 09:28:39 -04: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 09:33:20 -04:00			`done`

			`echo "All tests passed!"`