view tests/0019/run-test.sh @ 151:5fa52830e532

More defensive command-line error checking:

* the command line is also used by the WS server, so don't call exit()
  directly, call error();
* turn the server flag on before parsing the command-line, so that calls
  to error() do the right thing..

#! /bin/sh

. ../test-utils.sh

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

${AUDIODB} -d testdb -N

intstring 2 > testfeature01
floatstring 0 1 >> testfeature01
intstring 2 > testfeature10
floatstring 1 0 >> testfeature10

${AUDIODB} -d testdb -I -f testfeature01
${AUDIODB} -d testdb -I -f testfeature10

start_server ${AUDIODB} 10019

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

${AUDIODB} -c localhost:10019 -d testdb -Q track -l 1 -f testquery > testoutput
echo testfeature01 0.5 0 0 > test-expected-output
echo testfeature10 0 0 0 >> test-expected-output
cmp testoutput test-expected-output
${AUDIODB} -c localhost:10019 -d testdb -Q track -l 1 -f testquery -r 1 > testoutput
echo testfeature01 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:10019 -d testdb -Q track -l 1 -f testquery > testoutput
echo testfeature10 0.5 0 0 > test-expected-output
echo testfeature01 0 0 0 >> test-expected-output
cmp testoutput test-expected-output
${AUDIODB} -c localhost:10019 -d testdb -Q track -l 1 -f testquery -r 1 > testoutput
echo testfeature10 0.5 0 0 > test-expected-output
cmp testoutput test-expected-output

stop_server $!

exit 104