f420d876f2
issue #477 : stop using fork in responder_test.
6 years ago
386d869d5f
tests: fix responder_test after removing unused imports
6 years ago
26fdbf70e0
tests: good_load_module_size check can't be exact
...
Since message contains pathnames that vary across machines
6 years ago
f2f41809ae
issue #459 : initial get_stats() implementation
6 years ago
1d97493fcd
tests: fallout from #447 .
6 years ago
8a0b343760
issue #406 : test for FD leak after every TestCase
6 years ago
4146648759
master: log error an refuse __main__ import if no guard detected.
...
Closes #366 .
6 years ago
6cbf34d5fe
tests: another smattering of 3.x type/API fixes.
6 years ago
1d04a99adb
issue #275 : missing check_output() call
6 years ago
f7d2eace08
tests: importer fixes
7 years ago
ce6fb05d87
tests: 'fix' responder test.
...
Needs a complete rewrite, but this will do for now.
7 years ago
2132c311b2
tests: mark some tests as skipped
7 years ago
b433645d11
tests: Fix import error
7 years ago
ccd9c62399
tests: stubs for future whitelist/blacklist tests.
7 years ago
7e01c5bed5
Import and use unittest2 without aliasing it
7 years ago
e8e023ce59
Use specific TestCase assertions throughout tests
...
e.g. assert x == y -> self.assertEqual(x, y);
self.assertTrue(isinstance(x, y)) -> self.assertIsInstance(x, y)
These specific methods give more useful errors in the case of a test
failure.
7 years ago
17da6e9998
Use unittest2 in all tests
...
This allows using features such as TestCase,assertIsInstance on Python
2.6 and earlier.
7 years ago
f8a84616d7
tests: stop responder_test spamming the logs
7 years ago
1449c972eb
Allow running responder_test with unittest.
7 years ago
e2d3ac9b6a
Fixup some more tests.
7 years ago
e7ff6259a3
Initial commit.
7 years ago
David Wilson