view tests/0003/run-test.sh @ 48:a7aad4c50cb9

Factor out some common utilities and setup code into test-utils.sh, and
source that file within each run-test file.

#! /bin/sh

. ../test-utils.sh

if [ -f testdb ]; then rm -f testdb; fi

${AUDIODB} -d testdb -N

# We could contemplate putting the test feature (and the expected
# query output) under svn control if we trust its binary file
# handling.

# FIXME: endianness!
intstring 1 > testfeature
floatstring 1 >> testfeature

${AUDIODB} -d testdb -I -f testfeature

${AUDIODB} -d testdb -Q point -f testfeature > test-query-output

echo testfeature 1 0 0 > test-expected-query-output

cmp test-query-output test-expected-query-output

# failure cases
${AUDIODB} -d testdb -I && exit 1
${AUDIODB} -d testdb -f testfeature && exit 1
${AUDIODB} -I -f testfeature && exit 1
${AUDIODB} -d testdb -Q notpoint -f testfeature && exit 1
${AUDIODB} -Q point -f testfeature && exit 1

exit 104