view tests/0014/run-test.sh @ 252:fe4dc39b2dd7

Perform the incredibly tedious job of making the tests bash scripts,
rather than shell scripts.

This seems easier than emulating all the useful error-handling features
that bash provides in POSIX functionality as provided by dash(1).

#! /bin/bash

. ../test-utils.sh

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

${AUDIODB} -d testdb -N

${AUDIODB} -d testdb -L

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