cypherpunks authored 10 years ago and Nick Mathewson committed 9 years ago

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.

Also add test-memwipe to .gitignore file.

Signed-off-by: David Goulet <dgoulet@ev0ke.net>

This removes roughly 5000 branches in my testing. We never want to
trigger assertions even during tests, so this is sane. Implements #15400.

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.

cypherpunks authored 10 years ago and Nick Mathewson committed 10 years ago

Fixes the following rules in out-of-tree builds;
- check-spaces
- check-docs
- check-logs
- Doxygen
- coverage-html

And cleans up additional directories;
- coverage_html
- doc/doxygen

George Kadianakis authored 10 years ago and Nick Mathewson committed 10 years ago

We want to use this function in our guardfraction unittests, so make a
test_helpers module and move it there.

Before a couple weeks ago didn't know Tor had these tests, interesting! Stem
already has tests for spawning tor processes but lacked any with this targeted
focus on its arguments.

I've added our own counterpart for these tests. Many are direct copies but
there were others I improved a little...

  https://trac.torproject.org/projects/tor/ticket/14109
  https://gitweb.torproject.org/stem.git/commit/?id=137d193a026638f066e817e3396cebbbb6ace012

Now that Tor uses Stem to supplement its tests no reason for these to live
separately. Tested by simply building tor and confirming test_cmdline_args.py
is no longer in the generated Makefile.

This can run in parallel with the faster ones and the other tests.

rl1987 authored 10 years ago and Nick Mathewson committed 10 years ago

Now the code has separate implementation and examination functions,
uses smartlists sanely, and has relatively decent test coverage.

It seems to be working, but more tuning is needed.

Check that tor generates new keys, and overwrites the empty key files.
Test that tor generates new keys when keys are missing (existing
behaviour).
Test that tor does not overwrite key files that already contain data
(existing behaviour).

Tests fixes to bug 13111.

Michael Scherer authored 11 years ago and Nick Mathewson committed 10 years ago

This permit for now to signal readiness in a cleaner way
to systemd.

By now, support in the network is widespread and it's time to require
more modern crypto on all Tor instances, whether they're clients or
servers. By doing this early in 0.2.6, we can be sure that at some point
all clients will have reasonable support.

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.

Patch from "chobe".  Closes ticket 961.

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.

This reduces the likelihood that I have made any exploitable errors
in the encoding/decoding.

This commit also imports the trunnel runtime source into Tor.

Arlo Breault authored 10 years ago and Nick Mathewson committed 10 years ago

Also, sort test suites alphabetically.

anonymous authored 10 years ago and meejah committed 10 years ago

test-11291-group-redable-hsdirs-wtests-may8.patch

dana koch authored 10 years ago and Nick Mathewson committed 10 years ago

This is using the paradigm introduced for test_status.c.

Making the text file work out-of-tree didn't work on windows.

Maybe we can get it working that way later.

dana koch authored 10 years ago and Nick Mathewson committed 10 years ago

A new set of unit test cases are provided, as well as introducing
an alternative paradigm and macros to support it. Primarily, each test
case is given its own namespace, in order to isolate tests from each
other. We do this by in the usual fashion, by appending module and
submodule names to our symbols. New macros assist by reducing friction
for this and other tasks, like overriding a function in the global
namespace with one in the current namespace, or declaring integer
variables to assist tracking how many times a mock has been called.

A set of tests for a small-scale module has been included in this
commit, in order to highlight how the paradigm can be used. This
suite gives 100% coverage to status.c in test execution.

Also rename a function to be more accurate (resolve->resolved)