You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
mitogen/tests
David Wilson 519faa3b3b issue #369: add Connection.reset() test. 6 years ago
..
ansible issue #369: add Connection.reset() test. 6 years ago
bench tests: import a bunch more random unchecked in pieces. 6 years ago
data tests: import a bunch more random unchecked in pieces. 6 years ago
image_prep tests: Document Python versions in build_docker_images.py 6 years ago
soak tests: make cpu_load.py more random. 6 years ago
README.md tests: add new users for conndel tests. 6 years ago
__init__.py tests: Make the tests directory an importable package 7 years ago
broker_test.py core: split out & extend Broker.sync_call() 6 years ago
call_error_test.py tests: built-in exceptions live in a different module in 3.x 6 years ago
call_function_test.py issue #76: call_function_test fix. 6 years ago
channel_test.py Import and use unittest2 without aliasing it 7 years ago
docker_test.py tests: move stub tools, into subdir, import docker_test. 6 years ago
fakessh_test.py tests: put unittest.skip() around fakessh tests for the time being 7 years ago
first_stage_test.py Initial Python 3.x port work. 6 years ago
fork_test.py Initial Python 3.x port work. 6 years ago
id_allocation_test.py tests: remove stray hard-coded interpreter. 6 years ago
importer_test.py tests: must decode() zlib result for 3.x. 6 years ago
io_op_test.py issue #174: test all io_op() logic. 7 years ago
latch_test.py Initial Python 3.x port work. 6 years ago
local_test.py issue #291: permit supplying a full Python argv. 6 years ago
lxc_test.py tests: move stub tools, into subdir, import docker_test. 6 years ago
lxd_test.py tests: move stub tools, into subdir, import docker_test. 6 years ago
master_test.py master: update scan_code_imports to cope with wordcode 6 years ago
minimize_source_test.py tests: importer fixes 7 years ago
module_finder_test.py Update pytz to 2018.05 (needed by babel 2.6.0) 6 years ago
nested_test.py Initial Python 3.x port work. 6 years ago
parent_test.py tests: fix wstatus_to_str() test on 3.x 6 years ago
receiver_test.py Initial Python 3.x port work. 6 years ago
responder_test.py master: log error an refuse __main__ import if no guard detected. 6 years ago
router_test.py issue #76: record egress context IDs 6 years ago
select_test.py master: split Select() into new module to reduce wire size. 7 years ago
serialization_test.py core: fix serialization of empty bytes() on 3.x. 6 years ago
service_test.py tests: another smattering of 3.x type/API fixes. 6 years ago
show_docker_hostname.py Initial Python 3.x port work. 6 years ago
ssh_test.py tests: rename one more stubs/ssh.py reference. 6 years ago
testlib.py tests: activate faulthandler if available 6 years ago
two_three_compat_test.py tests: remove stray enable_debug() 6 years ago
types_test.py tests: another smattering of 3.x type/API fixes. 6 years ago
unix_test.py tests: fix fork FD sharing in unix_test. 6 years ago
utils_test.py tests: Add tests of mitogen.utils.cast() 6 years ago

README.md

Warning

This directory is full of disorganized crap, including random hacks I checked in that I'd like to turn into tests. The effort to write tests only really started in September 2017. Pull requests in this area are very welcome!

Running The Tests

Build Status

Your computer should have an Internet connection, and the docker command line tool should be able to connect to a working Docker daemon (localhost or elsewhere for OS X etc.) that can run new images.

The IP address of the Docker daemon must allow exposing ports from running containers, e.g. it should not be firewalled or port forwarded.

If in doubt, just install Docker on a Linux box in the default configuration and run the tests there.

Steps To Prepare Development Environment

  1. Get the code git clone https://github.com/dw/mitogen.git
  2. Go into the working directory cd mitogen
  3. Establish the docker image ./tests/build_docker_image.py
  4. Build the virtual environment virtualenv ../venv
  5. Enable the virtual environment we just built source ../venv/bin/activate
  6. Install Mitogen in pip editable mode pip install -e .
  7. Run test

Selecting a target distribution

Docker target images exist for testing against CentOS and Debian, with the default being Debian. To select CentOS, specify MITOGEN_TEST_DISTRO=centos in the environment.

User Accounts

A set of standard user account names are used by in the Docker container and also by Ansible's osx_setup.yml.

root In the Docker image only, the password is "rootpassword".

mitogen__has_sudo The login password is "has_sudo_password" and the account is capable of sudoing to root, by supplying the account password to sudo.

mitogen__has_sudo_pubkey The login password is "has_sudo_pubkey_password". Additionally tests/data/docker/mitogen__has_sudo_pubkey.key SSH key may be used to log in. It can sudo the same as mitogen__has_sudo.

mitogen__has_sudo_nopw The login password is "has_sudo_nopw_password". It can sudo to root without supplying a password. It has explicit sudoers rules forcing it to require a password for other accounts.

mitogen__pw_required The login password is "pw_required_password". When "sudo -u" is used to target this account, its password must be entered rather than the login user's password.

mitogen__require_tty The login password is "require_tty_password". When "sudo -u" is used to target this account, the parent session requires a TTY.

mitogen__require_tty_pw_required The login password is "require_tty_pw_required_password". When "sudo -u" is used to target this account, the parent session requires a TTY and the account password must be entered.

mitogen__user1 .. mitogen__user5 These accounts do not have passwords set. They exist to test the Ansible interpreter recycling logic.

mitogen__sudo1 .. mitogen__sudo4 May passwordless sudo to any account.

mitogen__webapp A plain old account with no sudo access, used as the target for fakessh tests.

Ansible Integration Test Environment

The integration tests expect to be run against a either one of the Docker images, or a similar target with the same set of UNIX accounts and sudo rules.

The login account should be able to sudo to root witout a password.