view tests/0012/run-test.sh @ 104:97107ee61dba

Temporary signal handling.

"Temporary" because it will not work on platforms which don't have real
signals (Hello, Win32) but nevertheless useful, as otherwise gcov (the
code coverage tool) will not count executions of processes that are
killed by signals (in particular, the server processes started in the
tests).

A brief experiment suggests that we're up to about 80% statement
coverage from our 20 tests.

#! /bin/sh

. ../test-utils.sh

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

${AUDIODB} -d testdb -N

intstring 2 > testfeature
floatstring 0 0.5 >> testfeature
floatstring 0.5 0 >> testfeature

# sequence queries require L2NORM; check that we can still insert
# after turning flag on
${AUDIODB} -d testdb -L

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

echo "query point (0.0,0.5)"
intstring 2 > testquery
floatstring 0 0.5 >> testquery

${AUDIODB} -d testdb -Q sequence -l 1 -f testquery > testoutput
echo testfeature 1 0 0 > test-expected-output
cmp testoutput test-expected-output
${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -n 1 > testoutput
echo testfeature 0 0 0 > test-expected-output
cmp testoutput test-expected-output

echo "query point (0.5,0.0)"
intstring 2 > testquery
floatstring 0.5 0 >> testquery

${AUDIODB} -d testdb -Q sequence -l 1 -f testquery > testoutput
echo testfeature 1 0 1 > test-expected-output
cmp testoutput test-expected-output
${AUDIODB} -d testdb -Q sequence -l 1 -f testquery -n 1 > testoutput
echo testfeature 0 0 1 > test-expected-output
cmp testoutput test-expected-output

exit 104