mirror of
https://github.com/Mercury-Language/mercury.git
synced 2026-04-15 09:23:44 +00:00
d64781a3d7
Estimated hours taken: 15 Add a testing architecture for the samples directory. The tests are in the "tests" subdirectory of the samples directory. This keeps them close to the samples, but not close enough to clutter up the samples. It also means you don't have to worry about the issue of exactly where the developer has checked out the CVS tests module. samples/c_interface/simpler_c_calls_mercury/Mmakefile: Update this example to generate a .a file instead of directly using $(mercury_lib.os) samples/tests/*: Test cases for all the samples.
19 lines
335 B
Bash
Executable File
19 lines
335 B
Bash
Executable File
#!/bin/sh
|
|
|
|
# Process command line options.
|
|
. ./handle_options
|
|
|
|
# Run the tests in each of the subdirectories.
|
|
. ./subdir_runtests
|
|
|
|
if test "$subdir_failures" = ""
|
|
then
|
|
echo "all tests have succeeded"
|
|
echo "mmakeopts=$mmakeopts"
|
|
exit 0
|
|
else
|
|
echo "some tests have failed in: $subdir_failures"
|
|
echo "mmakeopts=$mmakeopts"
|
|
exit 1
|
|
fi
|