libssh2/tests/Makefile.am

AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include -I$(top_builddir)/src
LDADD = ../src/libssh2.la

if SSHD
noinst_PROGRAMS = ssh2
ssh2_SOURCES = ssh2.c
endif

ctests = simple$(EXEEXT)
TESTS = $(ctests) mansyntax.sh
if SSHD
TESTS += ssh2.sh
endif
check_PROGRAMS = $(ctests)

TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT)
TESTS_ENVIRONMENT += srcdir=$(top_srcdir)/tests builddir=$(top_builddir)/tests

EXTRA_DIST = ssh2.sh mansyntax.sh
EXTRA_DIST += etc/host etc/host.pub etc/user etc/user.pub
EXTRA_DIST += CMakeLists.txt libssh2_config_cmake.h.in sshd_fixture.sh.in
EXTRA_DIST += key_dsa key_dsa.pub key_dsa_wrong key_dsa_wrong.pub key_rsa key_rsa.pub
EXTRA_DIST += openssh_server/authorized_keys openssh_server/Dockerfile openssh_server/ssh_host_rsa_key
EXTRA_DIST += openssh_fixture.c openssh_fixture.h runner.c session_fixture.c session_fixture.h
EXTRA_DIST += test_hostkey.c test_hostkey_hash.c
EXTRA_DIST += test_keyboard_interactive_auth_fails_with_wrong_response.c
EXTRA_DIST += test_keyboard_interactive_auth_succeeds_with_correct_response.c
EXTRA_DIST += test_password_auth_fails_with_wrong_password.c
EXTRA_DIST += test_password_auth_fails_with_wrong_username.c
EXTRA_DIST += test_password_auth_succeeds_with_correct_credentials.c
EXTRA_DIST += test_public_key_auth_fails_with_wrong_key.c
EXTRA_DIST += test_public_key_auth_succeeds_with_correct_dsa_key.c
EXTRA_DIST += test_public_key_auth_succeeds_with_correct_rsa_key.c
EXTRA_DIST += test_public_key_auth_succeeds_with_correct_encrypted_rsa_key.c
Add a more realistic self-test of libssh2. 2008-11-21 15:00:18 +00:00			`AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include -I$(top_builddir)/src`
Add basic self test. 2007-01-09 09:49:15 +00:00			`LDADD = ../src/libssh2.la`

Add a more realistic self-test of libssh2. 2008-11-21 15:00:18 +00:00			`if SSHD`
			`noinst_PROGRAMS = ssh2`
			`ssh2_SOURCES = ssh2.c`
			`endif`

Need to use $(EXEEXT) on programs in TESTS to fix mingw cross-compiles. 2009-08-11 02:46:45 +02:00			`ctests = simple$(EXEEXT)`
Add manpage syntax checker to 'check' target In virtually every libssh2 release Debian's lintian catches syntax errors in manpages. Prevent it by checking manpages as a part of testsuite. 2011-09-10 15:57:12 +02:00			`TESTS = $(ctests) mansyntax.sh`
Add a more realistic self-test of libssh2. 2008-11-21 15:00:18 +00:00			`if SSHD`
			`TESTS += ssh2.sh`
			`endif`
Add basic self test. 2007-01-09 09:49:15 +00:00			`check_PROGRAMS = $(ctests)`
Add a more realistic self-test of libssh2. 2008-11-21 15:00:18 +00:00
Support EXEEXT in self-test. 2008-11-27 16:00:07 +00:00			`TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT)`
tests/mansyntax.sh: fix 'make distcheck' with recent autotools Do not create symbolic links off the build directory. Recent autotools verify that out-of-source build works even if the source directory tree is not writable. 2015-07-02 12:08:03 +02:00			`TESTS_ENVIRONMENT += srcdir=$(top_srcdir)/tests builddir=$(top_builddir)/tests`
Add a more realistic self-test of libssh2. 2008-11-21 15:00:18 +00:00
Add manpage syntax checker to 'check' target In virtually every libssh2 release Debian's lintian catches syntax errors in manpages. Prevent it by checking manpages as a part of testsuite. 2011-09-10 15:57:12 +02:00			`EXTRA_DIST = ssh2.sh mansyntax.sh`
Add a more realistic self-test of libssh2. 2008-11-21 15:00:18 +00:00			`EXTRA_DIST += etc/host etc/host.pub etc/user etc/user.pub`
cmake: include CMake files in the release tarballs Despite we announced the CMake support in libssh2-1.6.0 release notes, the files required by the CMake build system were not included in the release tarballs. Hence, the only way to use CMake for build was the upstream git repository. This commit makes CMake actually supported in the release tarballs. 2015-07-02 12:50:29 +02:00			`EXTRA_DIST += CMakeLists.txt libssh2_config_cmake.h.in sshd_fixture.sh.in`
Basic dockerised test suite. This introduces a test suite for libssh2. It runs OpenSSH in a Docker container because that works well on Windows (via docker-machine) as well as Linux. Presumably it works on Mac too with docker-machine, but I've not tested that. Because the test suite is docker-machine aware, you can also run it against a cloud provider, for more realistic network testing, by setting your cloud provider as your active docker machine. The Appveyor CI setup in this commit does that because Appveyor doesn't support docker locally. 2016-08-14 16:03:25 +01:00			`EXTRA_DIST += key_dsa key_dsa.pub key_dsa_wrong key_dsa_wrong.pub key_rsa key_rsa.pub`
			`EXTRA_DIST += openssh_server/authorized_keys openssh_server/Dockerfile openssh_server/ssh_host_rsa_key`
			`EXTRA_DIST += openssh_fixture.c openssh_fixture.h runner.c session_fixture.c session_fixture.h`
			`EXTRA_DIST += test_hostkey.c test_hostkey_hash.c`
			`EXTRA_DIST += test_keyboard_interactive_auth_fails_with_wrong_response.c`
			`EXTRA_DIST += test_keyboard_interactive_auth_succeeds_with_correct_response.c`
			`EXTRA_DIST += test_password_auth_fails_with_wrong_password.c`
			`EXTRA_DIST += test_password_auth_fails_with_wrong_username.c`
			`EXTRA_DIST += test_password_auth_succeeds_with_correct_credentials.c`
			`EXTRA_DIST += test_public_key_auth_fails_with_wrong_key.c`
			`EXTRA_DIST += test_public_key_auth_succeeds_with_correct_dsa_key.c`
			`EXTRA_DIST += test_public_key_auth_succeeds_with_correct_rsa_key.c`
tests: add simple test for passphrase-protected PEM file support 2017-03-02 00:34:06 +01:00			`EXTRA_DIST += test_public_key_auth_succeeds_with_correct_encrypted_rsa_key.c`