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 fcdfd5f107 tests: fix disconnect_cleanup.yml target count assumption 6 years ago
..
ansible tests: fix disconnect_cleanup.yml target count assumption 6 years ago
bench tests/bench: run roundtrip.py a ton more to reduce variance 6 years ago
data tests: 3.x syntax compat for tests/data/stubs/ 6 years ago
image_prep tests: allow passing -vvv to build_docker_images. 6 years ago
soak
README.md
__init__.py
broker_test.py issue #406: ensure broker_test waits for broker exit. 6 years ago
call_error_test.py issue #406: test for FD leak after every TestCase 6 years ago
call_function_test.py core: dead messages have optional body, use it everywhere; closes #387. 6 years ago
channel_test.py
doas_test.py tests: stub tests for doas/mitogen_doas 6 years ago
docker_test.py issue #406: test for FD leak after every TestCase 6 years ago
fakessh_test.py issue #406: test for FD leak after every TestCase 6 years ago
first_stage_test.py
fork_test.py tests: fix fork_test compat on 3.x. 6 years ago
id_allocation_test.py
importer_test.py
io_op_test.py
kubectl_test.py issue #409: add kubectl stub and constructor test. 6 years ago
latch_test.py
local_test.py issue #406: test for FD leak after every TestCase 6 years ago
lxc_test.py issue #409: name-prefix stubs so they can be added to PATH 6 years ago
lxd_test.py issue #409: name-prefix stubs so they can be added to PATH 6 years ago
master_test.py issue #406: test for FD leak after every TestCase 6 years ago
minify_test.py tests: make minify_test print something useful on failure 6 years ago
module_finder_test.py
nested_test.py
parent_test.py tests: fix more DisconnectTest raciness. 6 years ago
poller_test.py tests: poller_test 3.x fix. 6 years ago
receiver_test.py
responder_test.py issue #406: test for FD leak after every TestCase 6 years ago
router_test.py core: dead messages have optional body, use it everywhere; closes #387. 6 years ago
select_test.py
serialization_test.py issue #406: test for FD leak after every TestCase 6 years ago
service_test.py
show_docker_hostname.py
ssh_test.py issue #406: test for FD leak after every TestCase 6 years ago
sudo_test.py issue #410: support sudo --user and SELinux options, add stub test. 6 years ago
testlib.py tests: handle NameError when faulthandler is not installed. 6 years ago
two_three_compat_test.py
types_test.py issue #406: test for FD leak after every TestCase 6 years ago
unix_test.py issue #406: fix thread leaks in unix_test too. 6 years ago
utils_test.py issue #406: test for FD leak after every TestCase 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.