1 files changed, 64 insertions, 0 deletions
diff --git a/src/tests/client/test-client.sh b/src/tests/client/test-client.sh
new file mode 100755
index 00000000..985d07c9
--- /dev/null
+++ b/src/tests/client/test-client.sh
@@ -0,0 +1,64 @@
+#!/bin/bash
+
+set -e
+
+die() {
+    printf '%s\n' "$@"
+    exit 1
+}
+
+if [ "$2" != "" ]; then
+    SRCDIR="$(realpath "$2")"
+else
+    SRCDIR="$(realpath "$(dirname "$BASH_SOURCE")/../../..")"
+fi
+
+if [ "$1" != "" ]; then
+    BUILDDIR="$(realpath "$1")"
+elif test -d "$SRCDIR/build" ; then
+    BUILDDIR="$(realpath "$SRCDIR/build")"
+else
+    BUILDDIR="$SRCDIR"
+fi
+
+test -d "$BUILDDIR" || die "BUILDDIR \"$BUILDDIR\" does not exist?"
+test -d "$SRCDIR" || die "SRCDIR \"$SRCDIR\" does not exist?"
+
+if [ "$3" != "" ]; then
+    PYTHON="$3"
+elif [ "$PYTHON" == "" ]; then
+    PYTHON="$(command -v python)" || die "python not found?"
+fi
+
+test -f "$BUILDDIR/src/nmcli/nmcli" || die "\"$BUILDDIR/src/nmcli/nmcli\" does not exist?"
+
+if test -f "$BUILDDIR/src/libnm-client-impl/.libs/libnm.so" ; then
+    LIBDIR="$BUILDDIR/src/libnm-client-impl/.libs"
+elif test -f "$BUILDDIR/src/libnm-client-impl/libnm.so" ; then
+    LIBDIR="$BUILDDIR/src/libnm-client-impl"
+else
+    die "libnm.so does not exist under expected paths in \"$BUILDDIR/src/libnm-client-impl/{.,.libs}/\""
+fi
+
+mkdir -p "$BUILDDIR/src/tests/client/" || die "failure to create build output directory \"$BUILDDIR/src/tests/client/\""
+
+export NM_TEST_CLIENT_NMCLI_PATH="$BUILDDIR/src/nmcli/nmcli"
+export GI_TYPELIB_PATH="$BUILDDIR/src/libnm-client-impl${GI_TYPELIB_PATH:+:$GI_TYPELIB_PATH}"
+export LD_LIBRARY_PATH="$LIBDIR${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
+export NM_TEST_CLIENT_BUILDDIR="$BUILDDIR"
+
+# Run nmcli at least once. With libtool, nmcli is a shell script and with LTO
+# this seems to perform some slow setup during the first run. If we do that
+# during the test, it will timeout and fail.
+"$NM_TEST_CLIENT_NMCLI_PATH" --version &>/dev/null
+
+# we first collect all the output in "test-client.log" and print it at once
+# afterwards. The only reason is that when you run with `make -j` that the
+# test output is grouped together.
+
+r="ok"
+"$PYTHON" "$SRCDIR/src/tests/client/test-client.py" -v &> "$BUILDDIR/src/tests/client/test-client.log" || r=fail
+
+cat "$BUILDDIR/src/tests/client/test-client.log"
+
+test "$r" = ok || die "test-client.py failed!!"