dorian
/
paramiko
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
paramiko/test.py

102 lines
4.3 KiB
Python
Raw Normal View History

[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-32] add unit tests add unit tests for BufferedFile and SFTP (it's a start). remove the demo sftp client because it was 99% copied from the other demos, which makes it kinda confusing. the unit tests are a much better example.
2004-03-08 12:54:19 -05:00
#!/usr/bin/python
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-154] even better 1.2 lapras re-bump the version # to 1.2 (with a new date since i added more stuff). add 2005 to the copyright date in a bunch of files.
2005-02-28 03:06:08 -05:00
# Copyright (C) 2003-2005 Robey Pointer <robey@lag.net>
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-32] add unit tests add unit tests for BufferedFile and SFTP (it's a start). remove the demo sftp client because it was 99% copied from the other demos, which makes it kinda confusing. the unit tests are a much better example.
2004-03-08 12:54:19 -05:00
#
# This file is part of paramiko.
#
# Paramiko is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Paramiko is distrubuted in the hope that it will be useful, but WITHOUT ANY
# WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
# A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
# details.
#
# You should have received a copy of the GNU Lesser General Public License
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-61] no more Foobar fix "Foobar" to be "Paramiko" in the one place i missed it in all the gpl headers. sigh. :)
2004-06-10 14:12:00 -04:00
# along with Paramiko; if not, write to the Free Software Foundation, Inc.,
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-32] add unit tests add unit tests for BufferedFile and SFTP (it's a start). remove the demo sftp client because it was 99% copied from the other demos, which makes it kinda confusing. the unit tests are a much better example.
2004-03-08 12:54:19 -05:00
# 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
"""
do the unit tests!
"""
import sys, os, unittest
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
from optparse import OptionParser
import paramiko
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-32] add unit tests add unit tests for BufferedFile and SFTP (it's a start). remove the demo sftp client because it was 99% copied from the other demos, which makes it kinda confusing. the unit tests are a much better example.
2004-03-08 12:54:19 -05:00
sys.path.append('tests/')
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
from test_message import MessageTest
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-32] add unit tests add unit tests for BufferedFile and SFTP (it's a start). remove the demo sftp client because it was 99% copied from the other demos, which makes it kinda confusing. the unit tests are a much better example.
2004-03-08 12:54:19 -05:00
from test_file import BufferedFileTest
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
from test_pkey import KeyTest
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-102] add key exchange tests + 1 more sftp test add test suite for key-exchange protocols, since i apparently broke the "gex" protocol recently and never noticed. also add an sftp unit test for mkdir/rmdir.
2004-11-06 21:08:11 -05:00
from test_kex import KexTest
[project @ Arch-1:robey@lag.net--2005-master-shake%paramiko--dev--1--patch-8] add unit tests for the packetizer, and fix a little locking bug where i think more of the packetizer write function should be inside a lock
2005-05-10 13:36:38 -04:00
from test_packetizer import PacketizerTest
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-94] start testing Transport the beginnings of tests for Transport. only the bare minimum is there right now. also started doc'ing things up to ivysaur.
2004-10-20 12:52:51 -04:00
from test_transport import TransportTest
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-32] add unit tests add unit tests for BufferedFile and SFTP (it's a start). remove the demo sftp client because it was 99% copied from the other demos, which makes it kinda confusing. the unit tests are a much better example.
2004-03-08 12:54:19 -05:00
from test_sftp import SFTPTest
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
default_host = 'localhost'
default_user = os.environ.get('USER', 'nobody')
default_keyfile = os.path.join(os.environ.get('HOME', '/'), '.ssh/id_rsa')
default_passwd = None
parser = OptionParser('usage: %prog [options]')
[project @ robey@ralph.lag.net-20051203043919-0a8c4665d04853fc] turn down output for unit tests by default, but add --verbose option to manually crank them back up
2005-12-02 23:39:19 -05:00
parser.add_option('--verbose', action='store_true', dest='verbose', default=False,
help='verbose display (one line per test)')
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-139] make loopback sftp tests the default change the unit tests to default to always running the sftp tests locally, and make a -R option to force the tests to run against a remote server. the tests seem to work fine locally, and it helps test out server mode, even though there's a danger that they could get isolated from reality and only test that paramiko can talk to itself.
2005-01-16 16:03:15 -05:00
parser.add_option('--no-pkey', action='store_false', dest='use_pkey', default=True,
help='skip RSA/DSS private key tests (which can take a while)')
parser.add_option('--no-transport', action='store_false', dest='use_transport', default=True,
help='skip transport tests (which can take a while)')
parser.add_option('--no-sftp', action='store_false', dest='use_sftp', default=True,
help='skip SFTP client/server tests, which can be slow')
parser.add_option('--no-big-file', action='store_false', dest='use_big_file', default=True,
help='skip big file SFTP tests, which are slow as molasses')
parser.add_option('-R', action='store_false', dest='use_loopback_sftp', default=True,
help='perform SFTP tests against a remote server (by default, SFTP tests ' +
'are done through a loopback socket)')
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
parser.add_option('-H', '--sftp-host', dest='hostname', type='string', default=default_host,
metavar='<host>',
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-139] make loopback sftp tests the default change the unit tests to default to always running the sftp tests locally, and make a -R option to force the tests to run against a remote server. the tests seem to work fine locally, and it helps test out server mode, even though there's a danger that they could get isolated from reality and only test that paramiko can talk to itself.
2005-01-16 16:03:15 -05:00
help='[with -R] host for remote sftp tests (default: %s)' % default_host)
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
parser.add_option('-U', '--sftp-user', dest='username', type='string', default=default_user,
metavar='<username>',
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-139] make loopback sftp tests the default change the unit tests to default to always running the sftp tests locally, and make a -R option to force the tests to run against a remote server. the tests seem to work fine locally, and it helps test out server mode, even though there's a danger that they could get isolated from reality and only test that paramiko can talk to itself.
2005-01-16 16:03:15 -05:00
help='[with -R] username for remote sftp tests (default: %s)' % default_user)
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
parser.add_option('-K', '--sftp-key', dest='keyfile', type='string', default=default_keyfile,
metavar='<keyfile>',
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-139] make loopback sftp tests the default change the unit tests to default to always running the sftp tests locally, and make a -R option to force the tests to run against a remote server. the tests seem to work fine locally, and it helps test out server mode, even though there's a danger that they could get isolated from reality and only test that paramiko can talk to itself.
2005-01-16 16:03:15 -05:00
help='[with -R] location of private key for remote sftp tests (default: %s)' %
default_keyfile)
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
parser.add_option('-P', '--sftp-passwd', dest='password', type='string', default=default_passwd,
metavar='<password>',
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-139] make loopback sftp tests the default change the unit tests to default to always running the sftp tests locally, and make a -R option to force the tests to run against a remote server. the tests seem to work fine locally, and it helps test out server mode, even though there's a danger that they could get isolated from reality and only test that paramiko can talk to itself.
2005-01-16 16:03:15 -05:00
help='[with -R] (optional) password to unlock the private key for remote sftp tests')
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
options, args = parser.parse_args()
if len(args) > 0:
parser.error('unknown argument(s)')
[project @ Arch-1:robey@lag.net--2005-master-shake%paramiko--dev--1--patch-5] split out Packetizer, fix banner detection bug, new unit test split out a chunk of BaseTransport into a Packetizer class, which handles the in/out packet data, ciphers, etc. it didn't make the code any smaller (transport.py is still close to 1500 lines, which is awful) but it did split out a coherent chunk of functionality into a discrete unit. in the process, fixed a bug that alain spineux pointed out: the banner check was too forgiving and would block forever waiting for an SSH banner. now it waits 5 seconds for the first line, and 2 seconds for each subsequent line, before giving up. added a unit test to test keepalive, since i wasn't sure that was still working after pulling out Packetizer.
2005-05-01 04:04:59 -04:00
# setup logging
paramiko.util.log_to_file('test.log')
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
if options.use_sftp:
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-139] make loopback sftp tests the default change the unit tests to default to always running the sftp tests locally, and make a -R option to force the tests to run against a remote server. the tests seem to work fine locally, and it helps test out server mode, even though there's a danger that they could get isolated from reality and only test that paramiko can talk to itself.
2005-01-16 16:03:15 -05:00
if options.use_loopback_sftp:
SFTPTest.init_loopback()
else:
SFTPTest.init(options.hostname, options.username, options.keyfile, options.password)
if not options.use_big_file:
SFTPTest.set_big_file_test(False)
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-32] add unit tests add unit tests for BufferedFile and SFTP (it's a start). remove the demo sftp client because it was 99% copied from the other demos, which makes it kinda confusing. the unit tests are a much better example.
2004-03-08 12:54:19 -05:00
suite = unittest.TestSuite()
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
suite.addTest(unittest.makeSuite(MessageTest))
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-32] add unit tests add unit tests for BufferedFile and SFTP (it's a start). remove the demo sftp client because it was 99% copied from the other demos, which makes it kinda confusing. the unit tests are a much better example.
2004-03-08 12:54:19 -05:00
suite.addTest(unittest.makeSuite(BufferedFileTest))
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-94] start testing Transport the beginnings of tests for Transport. only the bare minimum is there right now. also started doc'ing things up to ivysaur.
2004-10-20 12:52:51 -04:00
if options.use_pkey:
suite.addTest(unittest.makeSuite(KeyTest))
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-102] add key exchange tests + 1 more sftp test add test suite for key-exchange protocols, since i apparently broke the "gex" protocol recently and never noticed. also add an sftp unit test for mkdir/rmdir.
2004-11-06 21:08:11 -05:00
suite.addTest(unittest.makeSuite(KexTest))
[project @ Arch-1:robey@lag.net--2005-master-shake%paramiko--dev--1--patch-8] add unit tests for the packetizer, and fix a little locking bug where i think more of the packetizer write function should be inside a lock
2005-05-10 13:36:38 -04:00
suite.addTest(unittest.makeSuite(PacketizerTest))
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-136] loopback sftp test add ability to turn off more tests, and a secret (for now) -X option to do the sftp tests via loopback socket. added another symlink sftp test to see what happens with absolute symlinks.
2004-12-19 14:56:48 -05:00
if options.use_transport:
suite.addTest(unittest.makeSuite(TransportTest))
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-139] make loopback sftp tests the default change the unit tests to default to always running the sftp tests locally, and make a -R option to force the tests to run against a remote server. the tests seem to work fine locally, and it helps test out server mode, even though there's a danger that they could get isolated from reality and only test that paramiko can talk to itself.
2005-01-16 16:03:15 -05:00
if options.use_sftp:
[project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-91] fix test.py to use options instead of env vars, sftp tests default off fix up the test framework so that the sftp unit tests aren't always run (you have to ask for them explicitly) and they take their configuration from command-line options. they still require a remote server.
2004-09-25 18:03:48 -04:00
suite.addTest(unittest.makeSuite(SFTPTest))
[project @ robey@ralph.lag.net-20051203043919-0a8c4665d04853fc] turn down output for unit tests by default, but add --verbose option to manually crank them back up
2005-12-02 23:39:19 -05:00
verbosity = 1
if options.verbose:
verbosity = 2
unittest.TextTestRunner(verbosity=verbosity).run(suite)