view tests/0014/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 1 >> testfeature
floatstring 1 0 >> testfeature

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

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

start_server ${AUDIODB} 10014

${AUDIODB} -c localhost:10014 -d testdb -Q point -f testquery > testoutput
echo testfeature 0.5 0 0 > test-expected-output
echo testfeature 0 0 1 >> test-expected-output
cmp testoutput test-expected-output
${AUDIODB} -c localhost:10014 -d testdb -Q point -f testquery -n 1 > testoutput
echo testfeature 0.5 0 0 > test-expected-output
cmp testoutput test-expected-output

check_server $!

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

${AUDIODB} -c localhost:10014 -d testdb -Q point -f testquery > testoutput
echo testfeature 0.5 0 1 > test-expected-output
echo testfeature 0 0 0 >> test-expected-output
cmp testoutput test-expected-output
${AUDIODB} -c localhost:10014 -d testdb -Q point -f testquery -n 1 > testoutput
echo testfeature 0.5 0 1 > test-expected-output
cmp testoutput test-expected-output

stop_server $!

exit 104