nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-11 21:53:48 +01:00
Code Issues Packages Projects Releases Wiki Activity
98e1a1d106
tor/src/test/include.am

361 lines
12 KiB
Plaintext
Raw Normal View History

Use TESTS_ENVIRONMENT for older Automake versions The AM_TESTS_ENVIRONMENT variable is available since Automake v1.12 but some distributions have older Automake versions so we use TESTS_ENVIRONMENT.
2015-12-14 21:03:10 +01:00
# When the day comes that Tor requires Automake >= 1.12 change
# TESTS_ENVIRONMENT to AM_TESTS_ENVIRONMENT because the former is reserved for
# users while the later is reserved for developers.
TESTS_ENVIRONMENT = \
Use variables instead of substitutions Using variables removes the ambiguity about when to use variables and when to use substitutions. Variables always work. Substitutions only work when Autoconf knows about them which is not always the case. The variables are also placed between quotes to ensures spaces in the variables are handled properly.
2015-12-11 23:51:17 +01:00
export PYTHON="$(PYTHON)"; \
export SHELL="$(SHELL)"; \
export abs_top_srcdir="$(abs_top_srcdir)"; \
Allow Rust build using locally supplied crates or crates.io This adds a couple of configure commands to control whether we're requiring all dependencies to be available locally (default) or not (--enable-cargo-online-mode). When building from a tarball, we require the RUST_DEPENDENCIES variable to point to the local repository of crates. This also adds src/ext/rust as a git submodule that contains such a local repository for easy setup.
2017-05-02 04:21:42 +02:00
export abs_top_builddir="$(abs_top_builddir)"; \
Use variables instead of substitutions Using variables removes the ambiguity about when to use variables and when to use substitutions. Variables always work. Substitutions only work when Autoconf knows about them which is not always the case. The variables are also placed between quotes to ensures spaces in the variables are handled properly.
2015-12-11 23:51:17 +01:00
export builddir="$(builddir)"; \
Run cargo test during make check
2017-04-29 13:17:22 +02:00
export TESTING_TOR_BINARY="$(TESTING_TOR_BINARY)"; \
cargo-online-mode configure argument Passing --enable-cargo-online-mode during configure allows cargo to make network requests while building Tor or running tests. If this flag is not supplied, the dependencies need to be available in the form of a local mirror.
2017-05-02 05:06:45 +02:00
export CARGO="$(CARGO)"; \
export CARGO_ONLINE="$(CARGO_ONLINE)";
Stop trying to generate test scripts via autoconf substitution. Use environment variables instead. This repairs 'make distcheck', which was running into trouble when it tried to chmod the generated scripts. Fixes 17148.
2015-09-24 21:07:39 +02:00
Addition to test cases: make sure fuzzer binaries allow known cases This isn't fuzzing per se, so much as replaying the highlights of past fuzzer runs.
2016-12-14 21:57:22 +01:00
TESTSCRIPTS = \
src/test/fuzz_static_testcases.sh \
src/test/test_zero_length_keys.sh \
Add several test scripts wrapping test_workqueue This is a fairly easy way for us to get our test coverage up on compat_threads.c and workqueue.c -- I already implemented these tests, so we might as well enable them.
2016-06-08 23:29:06 +02:00
src/test/test_workqueue_cancel.sh \
src/test/test_workqueue_efd.sh \
src/test/test_workqueue_efd2.sh \
src/test/test_workqueue_pipe.sh \
src/test/test_workqueue_pipe2.sh \
src/test/test_workqueue_socketpair.sh \
Add unit tests for switch_id(), including tests for capabilities
2015-11-06 21:35:15 +01:00
src/test/test_switch_id.sh
Integrate zero_length_keys test into the automake test suite. The zero length keys test now requires the path to the Tor binary as the first parameter to ensure the correct Tor binary is used without hard coding a path. The wrapper script calls the zero length keys test for each test separately to ensure the correct shell is used (as configured by autoconf). Another solution would have been to place the tests into separate functions so multiple tests could be run internally. This would have made a diff of considerable size and frankly it is outside the scope of this fix.
2015-03-05 09:03:06 +01:00
Run cargo test during make check
2017-04-29 13:17:22 +02:00
if USE_RUST
TESTSCRIPTS += \
src/test/test_rust.sh
endif
Integrate ntor test into the automake test suite.
2015-03-05 10:43:12 +01:00
if USEPYTHON
prop224: Add Python integration tests for HS ntor. This test is identical to the ./src/test/test_ntor.sh integration test.
2017-03-14 14:06:36 +01:00
TESTSCRIPTS += src/test/test_ntor.sh src/test/test_hs_ntor.sh src/test/test_bt.sh
Integrate ntor test into the automake test suite.
2015-03-05 10:43:12 +01:00
endif
Kludge include.am to work with automake <1.12 The SH_LOG_COMPILER feature doesn't work with older automakes, and those are still in use in many environments we want to support development on, like Debian Stable. Instead, use autoconf substitution to fill out the shebang lines on the shell scripts, and an intermediate make target to make them executable. This is a bugfix on the patches for #15344. Bug not in any released tor.
2015-04-24 14:41:53 +02:00
TESTS += src/test/test src/test/test-slow src/test/test-memwipe \
Add several test scripts wrapping test_workqueue This is a fairly easy way for us to get our test coverage up on compat_threads.c and workqueue.c -- I already implemented these tests, so we might as well enable them.
2016-06-08 23:29:06 +02:00
src/test/test_workqueue \
src/test/test_keygen.sh \
routerkeys: Add cmdline option for learning signing key expiration. * CLOSES #17639. * ADDS new --key-expiration commandline option which prints when the signing key expires.
2017-07-14 03:25:01 +02:00
src/test/test_key_expiration.sh \
Quick-and-dirty test for timers code.
2016-04-13 21:30:59 +02:00
src/test/test-timers \
Add unit tests for switch_id(), including tests for capabilities
2015-11-06 21:35:15 +01:00
$(TESTSCRIPTS)
Kludge include.am to work with automake <1.12 The SH_LOG_COMPILER feature doesn't work with older automakes, and those are still in use in many environments we want to support development on, like Debian Stable. Instead, use autoconf substitution to fill out the shebang lines on the shell scripts, and an intermediate make target to make them executable. This is a bugfix on the patches for #15344. Bug not in any released tor.
2015-04-24 14:41:53 +02:00
Add "make test-network-all" to verify multiple test networks make test-network-all is Makefile target which verifies a series of test networks generated using test-network.sh and chutney. It runs IPv6 and mixed version test networks if the prerequisites are available. Each test network reports PASS, FAIL, or SKIP. Closes ticket 16953. Patch by "teor". Also adds "--hs-multi-client 1" option to TEST_NETWORK_FLAGS. This resolves #17012. Larger networks, such as bridges+hs, may fail until #16952 is merged.
2015-09-08 14:27:59 +02:00
# These flavors are run using automake's test-driver and test-network.sh
Add v3 hidden service support to make test-network-all Requires chutney master 50f64ea or later. Implements ticket 22437.
2017-09-12 09:08:28 +02:00
TEST_CHUTNEY_FLAVORS = basic-min bridges-min hs-v2-min hs-v3-min \
single-onion-v23
Add "make test-network-all" to verify multiple test networks make test-network-all is Makefile target which verifies a series of test networks generated using test-network.sh and chutney. It runs IPv6 and mixed version test networks if the prerequisites are available. Each test network reports PASS, FAIL, or SKIP. Closes ticket 16953. Patch by "teor". Also adds "--hs-multi-client 1" option to TEST_NETWORK_FLAGS. This resolves #17012. Larger networks, such as bridges+hs, may fail until #16952 is merged.
2015-09-08 14:27:59 +02:00
# only run if we can ping6 ::1 (localhost)
Don't run IPv6-only v3 single onion service tests using chutney Part of #23820.
2017-10-26 07:51:04 +02:00
# IPv6-only v3 single onion services don't work yet, so we don't test the
Test that IPv6-only clients can use microdescriptors When running "make test-network-all", test that IPv6-only clients can use microdescriptors. IPv6-only microdescriptor client support was fixed in tor 0.3.0.1-alpha. Requires chutney master 61c28b9 or later. Closes ticket 24109.
2017-11-01 07:13:07 +01:00
# single-onion-v23-ipv6-md flavor
TEST_CHUTNEY_FLAVORS_IPV6 = bridges+ipv6-min ipv6-exit-min hs-v23-ipv6-md \
single-onion-ipv6-md
Add "make test-network-all" to verify multiple test networks make test-network-all is Makefile target which verifies a series of test networks generated using test-network.sh and chutney. It runs IPv6 and mixed version test networks if the prerequisites are available. Each test network reports PASS, FAIL, or SKIP. Closes ticket 16953. Patch by "teor". Also adds "--hs-multi-client 1" option to TEST_NETWORK_FLAGS. This resolves #17012. Larger networks, such as bridges+hs, may fail until #16952 is merged.
2015-09-08 14:27:59 +02:00
# only run if we can find a stable (or simply another) version of tor
Add v3 hidden service support to make test-network-all Requires chutney master 50f64ea or later. Implements ticket 22437.
2017-09-12 09:08:28 +02:00
TEST_CHUTNEY_FLAVORS_MIXED = mixed+hs-v23
Add "make test-network-all" to verify multiple test networks make test-network-all is Makefile target which verifies a series of test networks generated using test-network.sh and chutney. It runs IPv6 and mixed version test networks if the prerequisites are available. Each test network reports PASS, FAIL, or SKIP. Closes ticket 16953. Patch by "teor". Also adds "--hs-multi-client 1" option to TEST_NETWORK_FLAGS. This resolves #17012. Larger networks, such as bridges+hs, may fail until #16952 is merged.
2015-09-08 14:27:59 +02:00
Kludge include.am to work with automake <1.12 The SH_LOG_COMPILER feature doesn't work with older automakes, and those are still in use in many environments we want to support development on, like Debian Stable. Instead, use autoconf substitution to fill out the shebang lines on the shell scripts, and an intermediate make target to make them executable. This is a bugfix on the patches for #15344. Bug not in any released tor.
2015-04-24 14:41:53 +02:00
### This is a lovely feature, but it requires automake >= 1.12, and Tor
Stop trying to generate test scripts via autoconf substitution. Use environment variables instead. This repairs 'make distcheck', which was running into trouble when it tried to chmod the generated scripts. Fixes 17148.
2015-09-24 21:07:39 +02:00
### doesn't require that yet.
Kludge include.am to work with automake <1.12 The SH_LOG_COMPILER feature doesn't work with older automakes, and those are still in use in many environments we want to support development on, like Debian Stable. Instead, use autoconf substitution to fill out the shebang lines on the shell scripts, and an intermediate make target to make them executable. This is a bugfix on the patches for #15344. Bug not in any released tor.
2015-04-24 14:41:53 +02:00
###
# TEST_EXTENSIONS = .sh
# SH_LOG_COMPILER = $(SHELL)
Start work on fancy compiler tricks to expose extra stuff to our tests This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests.
2013-06-06 20:56:05 +02:00
noinst_PROGRAMS+= src/test/bench
if UNITTESTS_ENABLED
Split the slow unit tests into their own binary This can run in parallel with the faster ones and the other tests.
2015-01-23 17:15:53 +01:00
noinst_PROGRAMS+= \
src/test/test \
src/test/test-slow \
Here is a test for memwipe. It invokes undefined behavior, I'm afraid, since there's no other c-legal way to test whether memwipe() works when we're not allowed to look at it. Closes ticket 15377.
2015-03-19 20:28:22 +01:00
src/test/test-memwipe \
Split the slow unit tests into their own binary This can run in parallel with the faster ones and the other tests.
2015-01-23 17:15:53 +01:00
src/test/test-child \
Add unit tests for switch_id(), including tests for capabilities
2015-11-06 21:35:15 +01:00
src/test/test_workqueue \
Quick-and-dirty test for timers code.
2016-04-13 21:30:59 +02:00
src/test/test-switch-id \
src/test/test-timers
Start work on fancy compiler tricks to expose extra stuff to our tests This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests.
2013-06-06 20:56:05 +02:00
endif
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src_test_AM_CPPFLAGS = -DSHARE_DATADIR="\"$(datadir)\"" \
-DLOCALSTATEDIR="\"$(localstatedir)\"" \
-DBINDIR="\"$(bindir)\"" \
Start work on fancy compiler tricks to expose extra stuff to our tests This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests.
2013-06-06 20:56:05 +02:00
-I"$(top_srcdir)/src/or" -I"$(top_srcdir)/src/ext" \
Start testing cell encoders/processers for the v3 handshake. An earlier version of these tests was broken; now they're a nicer, more robust, more black-box set of tests. The key is to have each test check a handshake message that is wrong in _one_ way.
2014-10-08 21:39:34 +02:00
-I"$(top_srcdir)/src/trunnel" \
-I"$(top_srcdir)/src/ext/trunnel" \
Start work on fancy compiler tricks to expose extra stuff to our tests This is mainly a matter of automake trickery: we build each static library in two versions now: one with the TOR_UNIT_TESTS macro defined, and one without. When TOR_UNIT_TESTS is defined, we can enable mocking and expose more functions. When it's not defined, we can lock the binary down more. The alternatives would be to have alternate build modes: a "testing configuration" for building the libraries with test support, and a "production configuration" for building them without. I don't favor that approach, since I think it would mean more people runnning binaries build for testing, or more people not running unit tests.
2013-06-06 20:56:05 +02:00
-DTOR_UNIT_TESTS
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
# -L flags need to go in LDFLAGS. -l flags need to go in LDADD.
# This seems to matter nowhere but on Windows, but I assure you that it
# matters a lot there, and is quite hard to debug if you forget to do it.
src_test_test_SOURCES = \
Add tests for compat_libevent
2015-09-15 17:20:44 +02:00
src/test/log_test_helpers.c \
test: Move duplicate HS test code and unify it Create the hs_test_helpers.{c|h} files that contains helper functions to create introduction point, descriptor and compare descriptor. Used by both the hs cache and hs descriptor tests. Unify them to avoid code duplication. Also, this commit fixes the usage of the signing key that was wrongly used when creating a cross signed certificate. Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-04-07 16:28:57 +02:00
src/test/hs_test_helpers.c \
Add tests for the rend cache
2015-09-15 16:21:50 +02:00
src/test/rend_test_helpers.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test.c \
Merge remote-tracking branch 'public/ticket9969' Conflicts: src/or/directory.c src/or/routerlist.c src/or/routerlist.h src/test/include.am src/test/test.c
2015-01-23 15:36:00 +01:00
src/test/test_accounting.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_addr.c \
Merge branch 'if_addr_refactoring_squashed' Conflicts: src/test/include.am src/test/test.c
2015-01-23 16:13:37 +01:00
src/test/test_address.c \
test: Add unit tests for addressset.c This also adds one that tests the integration with the nodelist. Signed-off-by: David Goulet <dgoulet@torproject.org>
2018-02-08 20:35:22 +01:00
src/test/test_address_set.c \
Split out buffers and socks tests into separate modules. No other changes were made here. Keeping everything in src/test/test.c was a legacy of back when we had all our unit tests in one big file. Doing this now because I'm adding an ext_or_command test.
2013-07-17 23:31:27 +02:00
src/test/test_buffers.c \
Refactor begin cell parsing into its own function, with tests. Add 'flags' argument to begin cells, per proposal 208.
2012-10-22 17:28:37 +02:00
src/test/test_cell_formats.c \
Merge remote-tracking branch 'public/ticket9969' Conflicts: src/or/directory.c src/or/routerlist.c src/or/routerlist.h src/test/include.am src/test/test.c
2015-01-23 15:36:00 +01:00
src/test/test_cell_queue.c \
Unit tests for channel_get_cell_queue_entry_size() and channel_write_*() functions
2013-12-13 15:34:46 +01:00
src/test/test_channel.c \
Netflow record collapsing defense. This defense will cause Cisco, Juniper, Fortinet, and other routers operating in the default configuration to collapse netflow records that would normally be split due to the 15 second flow idle timeout. Collapsing these records should greatly reduce the utility of default netflow data for correlation attacks, since all client-side records should become 30 minute chunks of total bytes sent/received, rather than creating multiple separate records for every webpage load/ssh command interaction/XMPP chat/whatever else happens to be inactive for more than 15 seconds. The defense adds consensus parameters to govern the range of timeout values for sending padding packets, as well as for keeping connections open. The defense only sends padding when connections are otherwise inactive, and it does not pad connections used solely for directory traffic at all. By default it also doesn't pad inter-relay connections. Statistics on the total padding in the last 24 hours are exported to the extra-info descriptors.
2016-09-06 20:35:53 +02:00
src/test/test_channelpadding.c \
Initial test_channeltls.c
2014-01-23 01:51:44 +01:00
src/test/test_channeltls.c \
Merge remote-tracking branch 'public/ticket9969' Conflicts: src/or/directory.c src/or/routerlist.c src/or/routerlist.h src/test/include.am src/test/test.c
2015-01-23 15:36:00 +01:00
src/test/test_checkdir.c \
Add some basic unit tests for the circuit map data structure. These show off the new mocking code by mocking the circuitmux code so that we can test the circuit map code in isolation.
2013-07-10 21:07:32 +02:00
src/test/test_circuitlist.c \
Regression test for destroy cell queue This exercises the code that crashed and caused #9296.
2013-07-19 16:17:00 +02:00
src/test/test_circuitmux.c \
Add tests for new_route_len()
2017-03-28 23:34:54 +02:00
src/test/test_circuitbuild.c \
Refactor circuit_predict_and_launch_new
2016-10-14 14:00:35 +02:00
src/test/test_circuituse.c \
Add tests for compat_libevent
2015-09-15 17:20:44 +02:00
src/test/test_compat_libevent.c \
Unit tests for router download functions. Also, sort test suites alphabetically.
2014-09-23 18:22:36 +02:00
src/test/test_config.c \
Prop210: Refactor connection_get_* to produce lists and counts
2015-12-07 07:40:56 +01:00
src/test/test_connection.c \
Tests for simple cases of conscache code.
2017-04-04 19:51:34 +02:00
src/test/test_conscache.c \
Consensus diff backend from Daniel Martí GSOC project. (This commit was extracted by nickm based on the final outcome of the project, taking only the changes in the files touched by this commit from the consdiff_rebased branch. The directory-system changes are going to get worked on separately.)
2017-03-07 15:58:30 +01:00
src/test/test_consdiff.c \
Unit tests for consdiffmgr module Initial tests. These just try adding a few consensuses, looking them up, and making sure that consensus diffs are generated in a more or less reasonable-looking way. It's enough for 87% coverage, but it leaves out a lot of functionality.
2017-04-14 18:35:02 +02:00
src/test/test_consdiffmgr.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_containers.c \
Add "ADD_ONION"/"DEL_ONION" and "GETINFO onions/*" to the controller. These commands allow for the creation and management of ephemeral Onion ("Hidden") services that are either bound to the lifetime of the originating control connection, or optionally the lifetime of the tor instance. Implements #6411.
2015-04-25 10:23:15 +02:00
src/test/test_controller.c \
Test functions used for TB_EMPTY and CELL_STATS events.
2013-05-31 15:51:25 +02:00
src/test/test_controller_events.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_crypto.c \
Remove crypto/rand include from test_crypto.c Create a new test_crypto_openssl to test openssl-only crypto.c functionality.
2017-03-25 12:04:11 +01:00
src/test/test_crypto_openssl.c \
test: Add unit tests for the DoS subsystem Signed-off-by: David Goulet <dgoulet@torproject.org>
2018-01-25 22:38:59 +01:00
src/test/test_dos.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_data.c \
src/test/test_dir.c \
Add unit test for router_pick_directory_server_impl
2015-01-26 20:49:48 +01:00
src/test/test_dir_common.c \
Add tests for directory_handle_command_get
2015-09-07 19:22:33 +02:00
src/test/test_dir_handle_get.c \
Begin writing unit tests for rewrite code
2015-01-13 03:08:43 +01:00
src/test/test_entryconn.c \
Add the entrynodes.c unit tests.
2014-06-24 20:22:52 +02:00
src/test/test_entrynodes.c \
Add unittests for the guardfraction feature.
2015-01-29 16:10:28 +01:00
src/test/test_guardfraction.c \
Unit tests for ext_or_id_map.
2013-07-18 21:51:29 +02:00
src/test/test_extorport.c \
Unit tests for router download functions. Also, sort test suites alphabetically.
2014-09-23 18:22:36 +02:00
src/test/test_hs.c \
test: Add test_hs_common unit tests Move tests from test_hs_service.c to this file. Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-04-20 17:20:02 +02:00
src/test/test_hs_common.c \
test: Add HS v2 service configuration unit tests Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-01-13 17:20:31 +01:00
src/test/test_hs_config.c \
test: Add test_hs_cell unit tests Move ESTABLISH_INTRO tests from test_hs_service.c to this new file. Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-04-20 15:58:21 +02:00
src/test/test_hs_cell.c \
test: Add test_hs_ntor unit tests Move the ntor test from test_hs_service.c to this file. Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-04-20 16:04:28 +02:00
src/test/test_hs_ntor.c \
prop224: Add unittests handling v3 ESTABLISH_INTRO cells. Test for both v2 and v3 ESTABLISH_INTRO handling.
2016-09-05 18:03:30 +02:00
src/test/test_hs_service.c \
test: Add client-side unittests for e2e rend circuits.
2017-05-02 15:36:59 +02:00
src/test/test_hs_client.c \
prop224: Add unittests handling v3 ESTABLISH_INTRO cells. Test for both v2 and v3 ESTABLISH_INTRO handling.
2016-09-05 18:03:30 +02:00
src/test/test_hs_intropoint.c \
Basic 'handle' implementation and tests. This abstraction covers the case where one part of the program needs to refer to another object that is allowed to disappear.
2016-02-12 00:34:29 +01:00
src/test/test_handles.c \
test: Add prop224 directory cache unit tests Signed-off-by: David Goulet <dgoulet@torproject.org> Signed-off-by: George Kadianakis <desnacked@riseup.net>
2016-08-10 22:40:06 +02:00
src/test/test_hs_cache.c \
test: Add prop224 descriptor unit tests Signed-off-by: David Goulet <dgoulet@torproject.org> Signed-off-by: George Kadianakis <desnacked@riseup.net>
2016-03-15 19:18:03 +01:00
src/test/test_hs_descriptor.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_introduce.c \
Key-pinning back-end for directory authorities. This module implements a key-pinning mechanism to ensure that it's safe to use RSA keys as identitifers even as we migrate to Ed25519 keys. It remembers, for every Ed25519 key we've seen, what the associated Ed25519 key is. This way, if we see a different Ed25519 key with that RSA key, we'll know that there's a mismatch. We persist these entries to disk using a simple format, where each line has a base64-encoded RSA SHA1 hash, then a base64-endoded Ed25519 key. Empty lines, misformed lines, and lines beginning with a # are ignored. Lines beginning with @ are reserved for future extensions.
2014-10-02 21:34:23 +02:00
src/test/test_keypin.c \
Start testing cell encoders/processers for the v3 handshake. An earlier version of these tests was broken; now they're a nicer, more robust, more black-box set of tests. The key is to have each test check a handshake message that is wrong in _one_ way.
2014-10-08 21:39:34 +02:00
src/test/test_link_handshake.c \
Unit tests for new functions in log.c
2013-07-29 19:30:49 +02:00
src/test/test_logging.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_microdesc.c \
Unit tests for router download functions. Also, sort test suites alphabetically.
2014-09-23 18:22:36 +02:00
src/test/test_nodelist.c \
Initial unit tests for OOM handling
2014-01-13 20:15:33 +01:00
src/test/test_oom.c \
Unit test for connection_handle_oos()
2016-07-02 06:39:45 +02:00
src/test/test_oos.c \
Start of a unit test for options_validate. I added this so I could write a unit test for ServerTransportOptions, but it incidentally exercises the succeed-on-defaults case of options_validate too.
2013-07-18 20:38:31 +02:00
src/test/test_options.c \
Merge remote-tracking branch 'public/ticket9969' Conflicts: src/or/directory.c src/or/routerlist.c src/or/routerlist.h src/test/include.am src/test/test.c
2015-01-23 15:36:00 +01:00
src/test/test_policy.c \
Add tests for procmon. These currently fail. Investigation should happen before submitting
2015-09-15 17:56:56 +02:00
src/test/test_procmon.c \
Let's get 100% coverage for proto_http while we're at it. There was some coverage before, but it was mostly accidental.
2017-09-28 03:45:55 +02:00
src/test/test_proto_http.c \
Add unit tests for var_cell and control0 proto functions.
2017-09-27 15:09:00 +02:00
src/test/test_proto_misc.c \
checkpoint basic protover backend
2016-08-10 01:11:47 +02:00
src/test/test_protover.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_pt.c \
Basic work on a publish/subscribe abstraction The goal here is to provide a way to decouple pieces of the code that want to learn "when something happens" from those that realize that it has happened. The implementation here consists of a generic backend, plus a set of macros to define and implement a set of type-safe frontends.
2016-03-24 16:15:19 +01:00
src/test/test_pubsub.c \
Add append_cell_to_circuit_queue() unit test
2014-01-21 11:54:35 +01:00
src/test/test_relay.c \
Merge remote-tracking branch 'public/ticket9969' Conflicts: src/or/directory.c src/or/routerlist.c src/or/routerlist.h src/test/include.am src/test/test.c
2015-01-23 15:36:00 +01:00
src/test/test_relaycell.c \
Add tests for the rend cache
2015-09-15 16:21:50 +02:00
src/test/test_rendcache.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_replay.c \
test: Add unittest for descriptors with BridgeDistribution option.
2017-10-23 21:44:06 +02:00
src/test/test_router.c \
Unit tests for test_routerkeys_write_fingerprint
2014-02-26 19:42:21 +01:00
src/test/test_routerkeys.c \
Unit tests for router download functions. Also, sort test suites alphabetically.
2014-09-23 18:22:36 +02:00
src/test/test_routerlist.c \
Merge remote-tracking branch 'public/ticket9969' Conflicts: src/or/directory.c src/or/routerlist.c src/or/routerlist.h src/test/include.am src/test/test.c
2015-01-23 15:36:00 +01:00
src/test/test_routerset.c \
Add some Rust utility functions and print support This gives an indication in the log that Tor was built with Rust support, as well as laying some groundwork for further string-returning APIs to be converted to Rust
2017-04-29 09:15:14 +02:00
src/test/test_rust.c \
Initial test_scheduler.c
2014-01-24 05:55:34 +01:00
src/test/test_scheduler.c \
prop250: Add unit tests Signed-off-by: David Goulet <dgoulet@torproject.org> Signed-off-by: George Kadianakis <desnacked@riseup.net>
2016-05-03 17:42:50 +02:00
src/test/test_shared_random.c \
Split out buffers and socks tests into separate modules. No other changes were made here. Keeping everything in src/test/test.c was a legacy of back when we had all our unit tests in one big file. Doing this now because I'm adding an ext_or_command test.
2013-07-17 23:31:27 +02:00
src/test/test_socks.c \
Merge remote-tracking branch 'public/ticket9969' Conflicts: src/or/directory.c src/or/routerlist.c src/or/routerlist.h src/test/include.am src/test/test.c
2015-01-23 15:36:00 +01:00
src/test/test_status.c \
Define a "storagedir" abstraction to hold numerous similar files We could use one of these for holding "junk" descriptors and unparseable things -- but we'll _need_ it for having cached consensuses and diffs between them.
2017-03-10 19:22:01 +01:00
src/test/test_storagedir.c \
Move thread tests into their own module
2013-09-25 20:50:01 +02:00
src/test/test_threads.c \
Add tests for tortls.c
2015-09-15 17:09:18 +02:00
src/test/test_tortls.c \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src/test/test_util.c \
Add tests for util_format
2015-09-15 17:40:16 +02:00
src/test/test_util_format.c \
Add tests for util_process
2015-09-15 17:37:25 +02:00
src/test/test_util_process.c \
Unittest prep: Move get_yesterday_date_str() to helper file. We want to use this function in our guardfraction unittests, so make a test_helpers module and move it there.
2015-01-29 16:09:53 +01:00
src/test/test_helpers.c \
Add tests for directory_handle_command_get
2015-09-07 19:22:33 +02:00
src/test/test_dns.c \
Split the slow unit tests into their own binary This can run in parallel with the faster ones and the other tests.
2015-01-23 17:15:53 +01:00
src/test/testing_common.c \
Move unittests' RSA pregen code into a new file, and improve. This patch moves the pregenerated RSA key logic into a new testing_rsakeys.c. Also, it adds support for RSA2048, since the link handshake tests want that. Also, it includes pregenerated keys, rather than trying to actually generate the keys at startup, since generating even a small handful of RSA2048 keys makes for an annoying delay.
2016-09-11 18:36:09 +02:00
src/test/testing_rsakeys.c \
Move all externally maintained source files into src/ext The rationale for treating these files differently is that we should be checking upstream for changes as applicable, and merging changes upstream as warranted.
2012-10-11 23:19:37 +02:00
src/ext/tinytest.c
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
Split the slow unit tests into their own binary This can run in parallel with the faster ones and the other tests.
2015-01-23 17:15:53 +01:00
src_test_test_slow_SOURCES = \
src/test/test_slow.c \
src/test/test_crypto_slow.c \
src/test/test_util_slow.c \
src/test/testing_common.c \
Move unittests' RSA pregen code into a new file, and improve. This patch moves the pregenerated RSA key logic into a new testing_rsakeys.c. Also, it adds support for RSA2048, since the link handshake tests want that. Also, it includes pregenerated keys, rather than trying to actually generate the keys at startup, since generating even a small handful of RSA2048 keys makes for an annoying delay.
2016-09-11 18:36:09 +02:00
src/test/testing_rsakeys.c \
Split the slow unit tests into their own binary This can run in parallel with the faster ones and the other tests.
2015-01-23 17:15:53 +01:00
src/ext/tinytest.c
Here is a test for memwipe. It invokes undefined behavior, I'm afraid, since there's no other c-legal way to test whether memwipe() works when we're not allowed to look at it. Closes ticket 15377.
2015-03-19 20:28:22 +01:00
src_test_test_memwipe_SOURCES = \
src/test/test-memwipe.c
Quick-and-dirty test for timers code.
2016-04-13 21:30:59 +02:00
src_test_test_timers_SOURCES = \
src/test/test-timers.c
Split the slow unit tests into their own binary This can run in parallel with the faster ones and the other tests.
2015-01-23 17:15:53 +01:00
Coverage support: build with --enable-coverage to have tests run with gcov If you pass the --enable-coverage flag on the command line, we build our testing binaries with appropriate options eo enable coverage testing. We also build a "tor-cov" binary that has coverage enabled, for integration tests. On recent OSX versions, test coverage only works with clang, not gcc. So we warn about that. Also add a contrib/coverage script to actually run gcov with the appropriate options to generate useful .gcov files. (Thanks to automake, the .o files will not have the names that gcov expects to find.) Also, remove generated gcda and gcno files on clean.
2013-07-09 18:37:11 +02:00
src_test_test_CFLAGS = $(AM_CFLAGS) $(TEST_CFLAGS)
Disable assertions during coverage builds This removes roughly 5000 branches in my testing. We never want to trigger assertions even during tests, so this is sane. Implements #15400.
2015-03-20 13:12:09 +01:00
src_test_test_CPPFLAGS= $(src_test_AM_CPPFLAGS) $(TEST_CPPFLAGS)
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src_test_bench_SOURCES = \
src/test/bench.c
Rename bench_workqueue -> test_workqueue and make it a unit test.
2013-09-25 17:36:02 +02:00
src_test_test_workqueue_SOURCES = \
src/test/test_workqueue.c
src_test_test_workqueue_CPPFLAGS= $(src_test_AM_CPPFLAGS)
src_test_test_workqueue_CFLAGS = $(AM_CFLAGS) $(TEST_CFLAGS)
Initial workqueue implemention, with a simple test. It seems to be working, but more tuning is needed.
2013-09-23 07:19:16 +02:00
Add unit tests for switch_id(), including tests for capabilities
2015-11-06 21:35:15 +01:00
src_test_test_switch_id_SOURCES = \
src/test/test_switch_id.c
src_test_test_switch_id_CPPFLAGS= $(src_test_AM_CPPFLAGS)
src_test_test_switch_id_CFLAGS = $(AM_CFLAGS) $(TEST_CFLAGS)
Add zlib path when linking the switch_id test
2015-12-18 10:04:06 +01:00
src_test_test_switch_id_LDFLAGS = @TOR_LDFLAGS_zlib@
Add unit tests for switch_id(), including tests for capabilities
2015-11-06 21:35:15 +01:00
src_test_test_switch_id_LDADD = \
src/common/libor-testing.a \
Add -ftrapv to gcc-hardening ... mostly! We know there are overflows in curve25519-donna-c32, so we'll have to have that one be fwrapv. Only apply the asan, ubsan, and trapv options to the code that does not need to run in constant time. Those options introduce branches to the code they instrument. (These introduced branches should never actually be taken, so it might _still_ be constant time after all, but branch predictors are complicated enough that I'm not really confident here. Let's aim for safety.) Closes 17983.
2016-04-13 00:59:40 +02:00
src/common/libor-ctime-testing.a \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
$(rust_ldadd) \
Add --enable-lzma to our configure script. This patch adds support for enabling support for LZMA to our configure script. By default, the --enable-lzma option is set to "auto" which means if liblzma is available we'll build Tor with LZMA support. See: https://bugs.torproject.org/21662
2017-04-18 13:56:02 +02:00
@TOR_ZLIB_LIBS@ @TOR_LIB_MATH@ \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
@TOR_LIB_WS32@ @TOR_LIB_USERENV@ \
@TOR_LZMA_LIBS@ @TOR_ZSTD_LIBS@
Add unit tests for switch_id(), including tests for capabilities
2015-11-06 21:35:15 +01:00
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src_test_test_LDFLAGS = @TOR_LDFLAGS_zlib@ @TOR_LDFLAGS_openssl@ \
@TOR_LDFLAGS_libevent@
Do not link tests against both libor.a and libor-testing.a Also, put libor-testing.a at a better position in the list of libraries, to avoid linker errors. This is a fix, or part of a fix, for 18490.
2016-03-11 15:53:25 +01:00
src_test_test_LDADD = src/or/libtor-testing.a \
src/common/libor-crypto-testing.a \
$(LIBKECCAK_TINY) \
$(LIBDONNA) \
src/common/libor-testing.a \
Add -ftrapv to gcc-hardening ... mostly! We know there are overflows in curve25519-donna-c32, so we'll have to have that one be fwrapv. Only apply the asan, ubsan, and trapv options to the code that does not need to run in constant time. Those options introduce branches to the code they instrument. (These introduced branches should never actually be taken, so it might _still_ be constant time after all, but branch predictors are complicated enough that I'm not really confident here. Let's aim for safety.) Closes 17983.
2016-04-13 00:59:40 +02:00
src/common/libor-ctime-testing.a \
Do not link tests against both libor.a and libor-testing.a Also, put libor-testing.a at a better position in the list of libraries, to avoid linker errors. This is a fix, or part of a fix, for 18490.
2016-03-11 15:53:25 +01:00
src/common/libor-event-testing.a \
Add the SHA-3 hash functions to common/crypto.h. * DIGEST_SHA3_[256,512] added as supported algorithms, which do exactly what is said on the tin. * test/bench now benchmarks all of the supported digest algorithms, so it's possible to see just how slow SHA-3 is, though the message sizes could probably use tweaking since this is very dependent on the message size vs the SHA-3 rate.
2015-12-18 23:15:01 +01:00
src/trunnel/libor-trunnel-testing.a \
trace: Add a basic event-tracing infrastructure. This commit adds the src/trace directory containing the basics for our tracing subsystem. It is not used in the code base. The "src/trace/debug.h" file contains an example on how we can map our tor trace events to log_debug(). The tracing subsystem can only be enabled by tracing framework at compile time. This commit introduces the "--enable-tracing-debug" option that will make all "tor_trace()" function be maped to "log_debug()". Closes #13802 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-01-23 20:28:10 +01:00
src/trace/libor-trace.a \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
$(rust_ldadd) \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
@TOR_ZLIB_LIBS@ @TOR_LIB_MATH@ @TOR_LIBEVENT_LIBS@ \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
@TOR_OPENSSL_LIBS@ @TOR_LIB_WS32@ @TOR_LIB_GDI@ @TOR_LIB_USERENV@ \
@CURVE25519_LIBS@ \
@TOR_SYSTEMD_LIBS@ @TOR_LZMA_LIBS@ @TOR_ZSTD_LIBS@
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
Split the slow unit tests into their own binary This can run in parallel with the faster ones and the other tests.
2015-01-23 17:15:53 +01:00
src_test_test_slow_CPPFLAGS = $(src_test_test_CPPFLAGS)
src_test_test_slow_CFLAGS = $(src_test_test_CFLAGS)
src_test_test_slow_LDADD = $(src_test_test_LDADD)
src_test_test_slow_LDFLAGS = $(src_test_test_LDFLAGS)
Here is a test for memwipe. It invokes undefined behavior, I'm afraid, since there's no other c-legal way to test whether memwipe() works when we're not allowed to look at it. Closes ticket 15377.
2015-03-19 20:28:22 +01:00
src_test_test_memwipe_CPPFLAGS = $(src_test_test_CPPFLAGS)
Document why we build memwipe that way.
2016-05-12 18:56:47 +02:00
# Don't use bugtrap cflags here: memwipe tests require memory violations.
Do not apply bugtrapping flags to test-memwipe, since testing memwipe requires bugs. Fixes bug 18901.
2016-05-02 18:56:18 +02:00
src_test_test_memwipe_CFLAGS = $(TEST_CFLAGS)
Here is a test for memwipe. It invokes undefined behavior, I'm afraid, since there's no other c-legal way to test whether memwipe() works when we're not allowed to look at it. Closes ticket 15377.
2015-03-19 20:28:22 +01:00
src_test_test_memwipe_LDADD = $(src_test_test_LDADD)
Document why we build memwipe that way.
2016-05-12 18:56:47 +02:00
# The LDFLAGS need to include the bugtrap cflags, or else we won't link
# successfully with the libraries built with them.
Do not apply bugtrapping flags to test-memwipe, since testing memwipe requires bugs. Fixes bug 18901.
2016-05-02 18:56:18 +02:00
src_test_test_memwipe_LDFLAGS = $(src_test_test_LDFLAGS) @CFLAGS_BUGTRAP@
Here is a test for memwipe. It invokes undefined behavior, I'm afraid, since there's no other c-legal way to test whether memwipe() works when we're not allowed to look at it. Closes ticket 15377.
2015-03-19 20:28:22 +01:00
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
src_test_bench_LDFLAGS = @TOR_LDFLAGS_zlib@ @TOR_LDFLAGS_openssl@ \
@TOR_LDFLAGS_libevent@
Make libcurve25519_donna get built as a .a This lets us give it compiler flags differing from the rest of libor-crypto.a
2012-12-06 18:07:58 +01:00
src_test_bench_LDADD = src/or/libtor.a src/common/libor.a \
Add -ftrapv to gcc-hardening ... mostly! We know there are overflows in curve25519-donna-c32, so we'll have to have that one be fwrapv. Only apply the asan, ubsan, and trapv options to the code that does not need to run in constant time. Those options introduce branches to the code they instrument. (These introduced branches should never actually be taken, so it might _still_ be constant time after all, but branch predictors are complicated enough that I'm not really confident here. Let's aim for safety.) Closes 17983.
2016-04-13 00:59:40 +02:00
src/common/libor-ctime.a \
Add the SHA-3 hash functions to common/crypto.h. * DIGEST_SHA3_[256,512] added as supported algorithms, which do exactly what is said on the tin. * test/bench now benchmarks all of the supported digest algorithms, so it's possible to see just how slow SHA-3 is, though the message sizes could probably use tweaking since this is very dependent on the message size vs the SHA-3 rate.
2015-12-18 23:15:01 +01:00
src/common/libor-crypto.a $(LIBKECCAK_TINY) $(LIBDONNA) \
prop220: Implement certificates and key storage/creation For prop220, we have a new ed25519 certificate type. This patch implements the code to create, parse, and validate those, along with code for routers to maintain their own sets of certificates and keys. (Some parts of master identity key encryption are done, but the implementation of that isn't finished)
2014-09-30 22:00:17 +02:00
src/common/libor-event.a src/trunnel/libor-trunnel.a \
trace: Add a basic event-tracing infrastructure. This commit adds the src/trace directory containing the basics for our tracing subsystem. It is not used in the code base. The "src/trace/debug.h" file contains an example on how we can map our tor trace events to log_debug(). The tracing subsystem can only be enabled by tracing framework at compile time. This commit introduces the "--enable-tracing-debug" option that will make all "tor_trace()" function be maped to "log_debug()". Closes #13802 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-01-23 20:28:10 +01:00
src/trace/libor-trace.a \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
$(rust_ldadd) \
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
@TOR_ZLIB_LIBS@ @TOR_LIB_MATH@ @TOR_LIBEVENT_LIBS@ \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
@TOR_OPENSSL_LIBS@ @TOR_LIB_WS32@ @TOR_LIB_GDI@ @TOR_LIB_USERENV@ \
@CURVE25519_LIBS@ \
@TOR_SYSTEMD_LIBS@ @TOR_LZMA_LIBS@ @TOR_ZSTD_LIBS@
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
Rename bench_workqueue -> test_workqueue and make it a unit test.
2013-09-25 17:36:02 +02:00
src_test_test_workqueue_LDFLAGS = @TOR_LDFLAGS_zlib@ @TOR_LDFLAGS_openssl@ \
Initial workqueue implemention, with a simple test. It seems to be working, but more tuning is needed.
2013-09-23 07:19:16 +02:00
@TOR_LDFLAGS_libevent@
Rename bench_workqueue -> test_workqueue and make it a unit test.
2013-09-25 17:36:02 +02:00
src_test_test_workqueue_LDADD = src/or/libtor-testing.a \
src/common/libor-testing.a \
Add -ftrapv to gcc-hardening ... mostly! We know there are overflows in curve25519-donna-c32, so we'll have to have that one be fwrapv. Only apply the asan, ubsan, and trapv options to the code that does not need to run in constant time. Those options introduce branches to the code they instrument. (These introduced branches should never actually be taken, so it might _still_ be constant time after all, but branch predictors are complicated enough that I'm not really confident here. Let's aim for safety.) Closes 17983.
2016-04-13 00:59:40 +02:00
src/common/libor-ctime-testing.a \
Add the SHA-3 hash functions to common/crypto.h. * DIGEST_SHA3_[256,512] added as supported algorithms, which do exactly what is said on the tin. * test/bench now benchmarks all of the supported digest algorithms, so it's possible to see just how slow SHA-3 is, though the message sizes could probably use tweaking since this is very dependent on the message size vs the SHA-3 rate.
2015-12-18 23:15:01 +01:00
src/common/libor-crypto-testing.a $(LIBKECCAK_TINY) $(LIBDONNA) \
Rename bench_workqueue -> test_workqueue and make it a unit test.
2013-09-25 17:36:02 +02:00
src/common/libor-event-testing.a \
trace: Add a basic event-tracing infrastructure. This commit adds the src/trace directory containing the basics for our tracing subsystem. It is not used in the code base. The "src/trace/debug.h" file contains an example on how we can map our tor trace events to log_debug(). The tracing subsystem can only be enabled by tracing framework at compile time. This commit introduces the "--enable-tracing-debug" option that will make all "tor_trace()" function be maped to "log_debug()". Closes #13802 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-01-23 20:28:10 +01:00
src/trace/libor-trace.a \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
$(rust_ldadd) \
Initial workqueue implemention, with a simple test. It seems to be working, but more tuning is needed.
2013-09-23 07:19:16 +02:00
@TOR_ZLIB_LIBS@ @TOR_LIB_MATH@ @TOR_LIBEVENT_LIBS@ \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
@TOR_OPENSSL_LIBS@ @TOR_LIB_WS32@ @TOR_LIB_GDI@ @TOR_LIB_USERENV@ \
@CURVE25519_LIBS@ \
@TOR_LZMA_LIBS@ @TOR_ZSTD_LIBS@
Initial workqueue implemention, with a simple test. It seems to be working, but more tuning is needed.
2013-09-23 07:19:16 +02:00
Quick-and-dirty test for timers code.
2016-04-13 21:30:59 +02:00
src_test_test_timers_CPPFLAGS = $(src_test_test_CPPFLAGS)
src_test_test_timers_CFLAGS = $(src_test_test_CFLAGS)
src_test_test_timers_LDADD = \
Merge branch 'ftrapv_v3' There were some conflicts here, and some breakage to fix concerning library link order in newer targets.
2016-05-12 19:00:45 +02:00
src/common/libor-testing.a \
src/common/libor-ctime-testing.a \
Quick-and-dirty test for timers code.
2016-04-13 21:30:59 +02:00
src/common/libor-event-testing.a \
src/common/libor-crypto-testing.a $(LIBKECCAK_TINY) $(LIBDONNA) \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
$(rust_ldadd) \
Quick-and-dirty test for timers code.
2016-04-13 21:30:59 +02:00
@TOR_ZLIB_LIBS@ @TOR_LIB_MATH@ @TOR_LIBEVENT_LIBS@ \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
@TOR_OPENSSL_LIBS@ @TOR_LIB_WS32@ @TOR_LIB_GDI@ @TOR_LIB_USERENV@ \
@CURVE25519_LIBS@ \
@TOR_LZMA_LIBS@
Quick-and-dirty test for timers code.
2016-04-13 21:30:59 +02:00
src_test_test_timers_LDFLAGS = $(src_test_test_LDFLAGS)
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
noinst_HEADERS+= \
Add fakechans.h to noinst_headers
2014-12-04 15:19:44 +01:00
src/test/fakechans.h \
Add hs_test_helpers.h to noinst_HEADERS
2017-05-15 17:45:20 +02:00
src/test/hs_test_helpers.h \
new headers must get distributed
2015-10-02 13:15:20 +02:00
src/test/log_test_helpers.h \
Fix "make distcheck"
2015-10-02 15:36:59 +02:00
src/test/rend_test_helpers.h \
Move test_descriptors.txt to an include file Making the text file work out-of-tree didn't work on windows. Maybe we can get it working that way later.
2014-07-16 22:37:00 +02:00
src/test/test.h \
Unittest prep: Move get_yesterday_date_str() to helper file. We want to use this function in our guardfraction unittests, so make a test_helpers module and move it there.
2015-01-29 16:09:53 +01:00
src/test/test_helpers.h \
Fix a couple of jenkins issues from 12538.
2015-12-21 18:32:20 +01:00
src/test/test_dir_common.h \
test: Move some test code to test helpers. Move code to create connection streams and rend_data structures to test_helpers so that we can use them from the e2e rendezvous circuit unittests.
2017-05-02 15:35:22 +02:00
src/test/test_connection.h \
Add a reference implementation of our ed25519 modifications Also, use it to generate test vectors, and add those test vectors to test_crypto.c This is based on ed25519.py from the ed25519 webpage; the kludgy hacks are my own.
2014-09-01 01:39:43 +02:00
src/test/test_descriptors.inc \
Base tests for 11243: test parsing for md, ei, and ri. We didn't really have test coverage for these parsing functions, so I went and made some. These tests also verify that the parsing functions set the list of invalid digests correctly.
2014-10-06 15:06:04 +02:00
src/test/example_extrainfo.inc \
src/test/failing_routerdescs.inc \
Merge branch 'bug12844' Conflicts: src/or/circuituse.c src/test/include.am src/test/test_entrynodes.c
2015-02-11 21:06:04 +01:00
src/test/ed25519_vectors.inc \
Fix "make distcheck"
2015-10-02 15:36:59 +02:00
src/test/test_descriptors.inc \
Add test_hs_descriptor.inc to include.am to unbreak distcheck.
2017-08-23 19:08:59 +02:00
src/test/test_hs_descriptor.inc \
Fix "make distcheck"
2015-10-02 15:36:59 +02:00
src/test/vote_descriptors.inc
Move to non-recursive make This gives us a few benefits: 1) make -j clean all this will start working, as it should. It currently doesn't. 2) increased parallel build recursive make will max out at number of files in a directory, non-recursive make doesn't have such a limitation 3) Removal of duplicate information in make files, less error prone I've also slightly updated how we call AM_INIT_AUTOMAKE, as the way that was used was not only deprecated but will be *removed* in the next major automake release (1.13).... so probably best that we can continue to bulid tor without requiring old automake. (see http://www.gnu.org/software/automake/manual/html_node/Public-Macros.html ) For more reasons why, see resources such as: http://miller.emu.id.au/pmiller/books/rmch/
2012-08-02 15:31:43 +02:00
Add reference implementation for ntor, plus compatibility test Before I started coding ntor in C, I did another one in Python. Turns out, they interoperate just fine.
2012-12-08 06:52:44 +01:00
noinst_PROGRAMS+= src/test/test-ntor-cl
prop224: Add Python integration tests for HS ntor. This test is identical to the ./src/test/test_ntor.sh integration test.
2017-03-14 14:06:36 +01:00
noinst_PROGRAMS+= src/test/test-hs-ntor-cl
Add reference implementation for ntor, plus compatibility test Before I started coding ntor in C, I did another one in Python. Turns out, they interoperate just fine.
2012-12-08 06:52:44 +01:00
src_test_test_ntor_cl_SOURCES = src/test/test_ntor_cl.c
src_test_test_ntor_cl_LDFLAGS = @TOR_LDFLAGS_zlib@ @TOR_LDFLAGS_openssl@
src_test_test_ntor_cl_LDADD = src/or/libtor.a src/common/libor.a \
Add -ftrapv to gcc-hardening ... mostly! We know there are overflows in curve25519-donna-c32, so we'll have to have that one be fwrapv. Only apply the asan, ubsan, and trapv options to the code that does not need to run in constant time. Those options introduce branches to the code they instrument. (These introduced branches should never actually be taken, so it might _still_ be constant time after all, but branch predictors are complicated enough that I'm not really confident here. Let's aim for safety.) Closes 17983.
2016-04-13 00:59:40 +02:00
src/common/libor-ctime.a \
Add the SHA-3 hash functions to common/crypto.h. * DIGEST_SHA3_[256,512] added as supported algorithms, which do exactly what is said on the tin. * test/bench now benchmarks all of the supported digest algorithms, so it's possible to see just how slow SHA-3 is, though the message sizes could probably use tweaking since this is very dependent on the message size vs the SHA-3 rate.
2015-12-18 23:15:01 +01:00
src/common/libor-crypto.a $(LIBKECCAK_TINY) $(LIBDONNA) \
trace: Add a basic event-tracing infrastructure. This commit adds the src/trace directory containing the basics for our tracing subsystem. It is not used in the code base. The "src/trace/debug.h" file contains an example on how we can map our tor trace events to log_debug(). The tracing subsystem can only be enabled by tracing framework at compile time. This commit introduces the "--enable-tracing-debug" option that will make all "tor_trace()" function be maped to "log_debug()". Closes #13802 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-01-23 20:28:10 +01:00
src/trace/libor-trace.a \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
$(rust_ldadd) \
Add reference implementation for ntor, plus compatibility test Before I started coding ntor in C, I did another one in Python. Turns out, they interoperate just fine.
2012-12-08 06:52:44 +01:00
@TOR_ZLIB_LIBS@ @TOR_LIB_MATH@ \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
@TOR_OPENSSL_LIBS@ @TOR_LIB_WS32@ @TOR_LIB_GDI@ @TOR_LIB_USERENV@ \
@CURVE25519_LIBS@ @TOR_LZMA_LIBS@
Add reference implementation for ntor, plus compatibility test Before I started coding ntor in C, I did another one in Python. Turns out, they interoperate just fine.
2012-12-08 06:52:44 +01:00
src_test_test_ntor_cl_AM_CPPFLAGS = \
-I"$(top_srcdir)/src/or"
prop224: Add Python integration tests for HS ntor. This test is identical to the ./src/test/test_ntor.sh integration test.
2017-03-14 14:06:36 +01:00
src_test_test_hs_ntor_cl_SOURCES = src/test/test_hs_ntor_cl.c
src_test_test_hs_ntor_cl_LDFLAGS = @TOR_LDFLAGS_zlib@ @TOR_LDFLAGS_openssl@
src_test_test_hs_ntor_cl_LDADD = src/or/libtor.a src/common/libor.a \
src/common/libor-ctime.a \
src/common/libor-crypto.a $(LIBKECCAK_TINY) $(LIBDONNA) \
@TOR_ZLIB_LIBS@ @TOR_LIB_MATH@ \
@TOR_OPENSSL_LIBS@ @TOR_LIB_WS32@ @TOR_LIB_GDI@ @CURVE25519_LIBS@
src_test_test_hs_ntor_cl_AM_CPPFLAGS = \
-I"$(top_srcdir)/src/or"
Tests for backtrace.c These need to be a separate executable, since the point of backtrace.c is that it can crash and write stuff.
2013-07-30 03:56:31 +02:00
noinst_PROGRAMS += src/test/test-bt-cl
src_test_test_bt_cl_SOURCES = src/test/test_bt_cl.c
src_test_test_bt_cl_LDADD = src/common/libor-testing.a \
Add -ftrapv to gcc-hardening ... mostly! We know there are overflows in curve25519-donna-c32, so we'll have to have that one be fwrapv. Only apply the asan, ubsan, and trapv options to the code that does not need to run in constant time. Those options introduce branches to the code they instrument. (These introduced branches should never actually be taken, so it might _still_ be constant time after all, but branch predictors are complicated enough that I'm not really confident here. Let's aim for safety.) Closes 17983.
2016-04-13 00:59:40 +02:00
src/common/libor-ctime-testing.a \
trace: Add a basic event-tracing infrastructure. This commit adds the src/trace directory containing the basics for our tracing subsystem. It is not used in the code base. The "src/trace/debug.h" file contains an example on how we can map our tor trace events to log_debug(). The tracing subsystem can only be enabled by tracing framework at compile time. This commit introduces the "--enable-tracing-debug" option that will make all "tor_trace()" function be maped to "log_debug()". Closes #13802 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-01-23 20:28:10 +01:00
src/trace/libor-trace.a \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
$(rust_ldadd) \
Tests for backtrace.c These need to be a separate executable, since the point of backtrace.c is that it can crash and write stuff.
2013-07-30 03:56:31 +02:00
@TOR_LIB_MATH@ \
22839: Build tor with rust enabled on win - make tor_util static library name configurable - fix Rust libary dependency order for Windows
2017-08-10 10:08:41 +02:00
@TOR_LIB_WS32@ @TOR_LIB_GDI@ @TOR_LIB_USERENV@
Tests for backtrace.c These need to be a separate executable, since the point of backtrace.c is that it can crash and write stuff.
2013-07-30 03:56:31 +02:00
src_test_test_bt_cl_CFLAGS = $(AM_CFLAGS) $(TEST_CFLAGS)
Disable assertions during coverage builds This removes roughly 5000 branches in my testing. We never want to trigger assertions even during tests, so this is sane. Implements #15400.
2015-03-20 13:12:09 +01:00
src_test_test_bt_cl_CPPFLAGS= $(src_test_AM_CPPFLAGS) $(TEST_CPPFLAGS)
Tests for backtrace.c These need to be a separate executable, since the point of backtrace.c is that it can crash and write stuff.
2013-07-30 03:56:31 +02:00
Distcheck repair: add new python testing code to "tarballs" 'make distcheck' now passes again.
2014-02-04 17:07:43 +01:00
EXTRA_DIST += \
src/test/bt_test.py \
src/test/ntor_ref.py \
prop224: Add Python integration tests for HS ntor. This test is identical to the ./src/test/test_ntor.sh integration test.
2017-03-14 14:06:36 +01:00
src/test/hs_ntor_ref.py \
test: Unit test for the hs indexes Using a test vector in python, test both hs_build_hsdir_index() and hs_build_hs_index(). This commit also adds the hs_build_address.py to EXTRA_DIST which was missing. Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-08-29 18:12:52 +02:00
src/test/hs_build_address.py \
src/test/hs_indexes.py \
Fix "make distcheck". I had forgotten to include the fuzz_static_testcases.sh script in EXTRA_DIST.
2017-02-03 18:04:08 +01:00
src/test/fuzz_static_testcases.sh \
Distcheck repair: add new python testing code to "tarballs" 'make distcheck' now passes again.
2014-02-04 17:07:43 +01:00
src/test/slownacl_curve25519.py \
Add test_keygen.sh to dist
2015-09-02 15:17:43 +02:00
src/test/zero_length_keys.sh \
Stop trying to generate test scripts via autoconf substitution. Use environment variables instead. This repairs 'make distcheck', which was running into trouble when it tried to chmod the generated scripts. Fixes 17148.
2015-09-24 21:07:39 +02:00
src/test/test_keygen.sh \
routerkeys: Add cmdline option for learning signing key expiration. * CLOSES #17639. * ADDS new --key-expiration commandline option which prints when the signing key expires.
2017-07-14 03:25:01 +02:00
src/test/test_key_expiration.sh \
Fix inconsistent tab/space mixing in include.am files. This is a whitespace only, cosmetic fix. There is still some inconsistency between lists, but less inconsistency inside individual lists.
2016-05-12 19:06:58 +02:00
src/test/test_zero_length_keys.sh \
prop224: Add Python integration tests for HS ntor. This test is identical to the ./src/test/test_ntor.sh integration test.
2017-03-14 14:06:36 +01:00
src/test/test_ntor.sh src/test/test_hs_ntor.sh src/test/test_bt.sh \
Repair "make distcheck".
2015-12-20 20:57:27 +01:00
src/test/test-network.sh \
Run cargo test during make check
2017-04-29 13:17:22 +02:00
src/test/test_rust.sh \
Add several test scripts wrapping test_workqueue This is a fairly easy way for us to get our test coverage up on compat_threads.c and workqueue.c -- I already implemented these tests, so we might as well enable them.
2016-06-08 23:29:06 +02:00
src/test/test_switch_id.sh \
src/test/test_workqueue_cancel.sh \
src/test/test_workqueue_efd.sh \
src/test/test_workqueue_efd2.sh \
src/test/test_workqueue_pipe.sh \
src/test/test_workqueue_pipe2.sh \
src/test/test_workqueue_socketpair.sh
Reference in New Issue Copy Permalink