0b4899ef23
The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
16 lines
376 B
Bash
Executable File
16 lines
376 B
Bash
Executable File
#!/bin/sh
|
|
|
|
UNIT_TEST=$1
|
|
|
|
shift
|
|
|
|
echo "Running ./test-interactive $UNIT_TEST $@"
|
|
echo ""
|
|
echo "NOTE: For debugging purposes, you can run this single test as follows:"
|
|
echo "$ libtool --mode=execute \\"
|
|
echo " gdb --eval-command=\"b `echo $UNIT_TEST|tr '-' '_'`_main\" \\"
|
|
echo " --args ./test-interactive $UNIT_TEST"
|
|
|
|
./test-interactive $UNIT_TEST "$@"
|
|
|