blob: 0fc0528e88eb008e746ad8caccfc59cb9b6c9f28 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
#!/usr/local/bin/perl
#
# Test processing of CLI options.
#
use strict;
use warnings;
use File::Basename;
use Test::More tests => 1;
use testutil;
#init_test_dirs();
# Since here we're doing black-box testing on the stow executable,
# this looks like it should be robust:
#
#my $STOW = dirname(__FILE__) . '/../bin/stow';
#
# but unfortunately it breaks things like "make distcheck", which
# builds the stow script into a separate path like
#
# stow-2.3.0/_build/sub/bin
#
# before cd'ing to something like
#
# stow-2.3.0/_build/sub
#
# and then running the tests via:
#
# make check-TESTS
# make[2]: Entering directory '/path/to/stow/src/stow-2.3.0/_build/sub'
# dir=../../t; \
# /usr/bin/perl -Ibin -Ilib -I../../t -MTest::Harness -e 'runtests(@ARGV)' "${dir#./}"/*.t
#
# So the simplest solution is to hardcode an assumption that we run
# tests either from somewhere like this during distcheck:
#
# stow-2.3.0/_build/sub
#
# or from the top of the source tree during development. This can be done
# via the following, which also follows the KISS principle:
my $STOW = 'bin/stow';
`$STOW --help`;
is($?, 0, "--help should return 0 exit code");
# vim:ft=perl
|
