annotate tests/0003/run-test.sh @ 620:70fc1a504138

Okay, I think my python bindings have reached the border of useful, so in the svn they go. The bindings currently allow for adb create and open, status and the setting of the l2norm and power flags. Note that these are the direct c bindings, when it's done there will be OO dressing on top for standard entry. Also, even though I don't use numpy yet, the include file is brought in, so the module won't build if you don't have numpy in an importable place.
author map01bf
date Tue, 15 Sep 2009 17:40:02 +0000
parents fe4dc39b2dd7
children
rev   line source
mas01cr@252 1 #! /bin/bash
mas01cr@43 2
mas01cr@48 3 . ../test-utils.sh
mas01cr@44 4
mas01cr@43 5 if [ -f testdb ]; then rm -f testdb; fi
mas01cr@43 6
mas01cr@43 7 ${AUDIODB} -d testdb -N
mas01cr@43 8
mas01cr@239 9 # point query now implemented as sequence search
mas01cr@239 10 ${AUDIODB} -d testdb -L
mas01cr@239 11
mas01cr@45 12 # We could contemplate putting the test feature (and the expected
mas01cr@45 13 # query output) under svn control if we trust its binary file
mas01cr@45 14 # handling.
mas01cr@45 15
mas01cr@43 16 # FIXME: endianness!
mas01cr@48 17 intstring 1 > testfeature
mas01cr@48 18 floatstring 1 >> testfeature
mas01cr@43 19
mas01cr@43 20 ${AUDIODB} -d testdb -I -f testfeature
mas01cr@43 21
mas01cr@46 22 ${AUDIODB} -d testdb -Q point -f testfeature > test-query-output
mas01cr@43 23
mas01cr@46 24 echo testfeature 1 0 0 > test-expected-query-output
mas01cr@43 25
mas01cr@46 26 cmp test-query-output test-expected-query-output
mas01cr@43 27
mas01cr@44 28 # failure cases
mas01cr@54 29 expect_clean_error_exit ${AUDIODB} -d testdb -I
mas01cr@54 30 expect_clean_error_exit ${AUDIODB} -d testdb -f testfeature
mas01cr@54 31 expect_clean_error_exit ${AUDIODB} -I -f testfeature
mas01cr@54 32 expect_clean_error_exit ${AUDIODB} -d testdb -Q notpoint -f testfeature
mas01cr@54 33 expect_clean_error_exit ${AUDIODB} -Q point -f testfeature
mas01cr@44 34
mas01cr@43 35 exit 104