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
Steven Robertson 5a0da02e6c code review changes, using when statements and adding trailing comma 4 years ago
..
ansible code review changes, using when statements and adding trailing comma 4 years ago
bench Add mitogen.core.now() and use it everywhere; closes #614. 5 years ago
data Merge devel/290 @ 79b979ec8544ef5d8620c64068d4a42fabf50415 5 years ago
image_prep attempt at fixing 'sudo runas gid invalid value' since the sudo command looks correct 5 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 issue #170: implement timers. 5 years ago
buildah_test.py [stream-refactor] port mitogen.buildah, added to master since work began 5 years ago
call_error_test.py issue #477: replace type(e) -> __class__ for an exception 6 years ago
call_function_test.py issue #477: call_function_test fixes for 2.4. 6 years ago
channel_test.py Import and use unittest2 without aliasing it 7 years ago
connection_test.py parent: zombie reaping v3 5 years ago
context_test.py core: move message encoding to Message.pack(), add+refactor tests. 5 years ago
create_child_test.py Add mitogen.core.now() and use it everywhere; closes #614. 5 years ago
doas_test.py disabling another flaky test 5 years ago
docker_test.py Refactor Stream, introduce quasi-asynchronous connect, much more 5 years ago
error_test.py tests: some more utility function tests + flake8. 6 years ago
fakessh_test.py issue #477: util/fakessh/two_three_compat fixes. 6 years ago
file_service_test.py issue #615: fix up FileService tests for new logic 5 years ago
first_stage_test.py [stream-refactor] Py3.x test fixes 5 years ago
fork_test.py issue #477: make mitogen.fork unsupported on Py<2.6. 6 years ago
id_allocation_test.py tests: remove stray hard-coded interpreter. 6 years ago
importer_test.py issue #590: teach importer to handle self-replacing modules 6 years ago
io_op_test.py issue #477: old Mock does not throw side_effect exceptions from a list 6 years ago
iter_split_test.py [stream-refactor] Py2.4 compat fix for iter_split_test. 5 years ago
jail_test.py tests: jail_test fixes. 5 years ago
kubectl_test.py issue #409: add kubectl stub and constructor test. 6 years ago
latch_test.py core: Latch.empty() improvements 6 years ago
local_test.py tests: Pythonize env_wrapper.sh, clean up local_test 6 years ago
log_handler_test.py disable flaky test on py3.6 5 years ago
lxc_test.py Refactor Stream, introduce quasi-asynchronous connect, much more 5 years ago
lxd_test.py Refactor Stream, introduce quasi-asynchronous connect, much more 5 years ago
master_test.py issue #406: test for FD leak after every TestCase 6 years ago
message_test.py core: move message encoding to Message.pack(), add+refactor tests. 5 years ago
minify_test.py issue #508: tests: skip minify_test Py2.4/2.5 for profiler.py. 6 years ago
mitogen_protocol_test.py Refactor Stream, introduce quasi-asynchronous connect, much more 5 years ago
module_finder_test.py issue #590: rework ParentEnumerationMethod to recursively handle bad modules 5 years ago
nested_test.py Initial Python 3.x port work. 6 years ago
os_fork_test.py os_fork: python 3 fixes and tests. 6 years ago
parent_test.py Add mitogen.core.now() and use it everywhere; closes #614. 5 years ago
policy_function_test.py tests: add some more helper function tests. 6 years ago
poller_test.py Add mitogen.core.now() and use it everywhere; closes #614. 5 years ago
polyfill_functions_test.py issue #477: rename and add tests for polyfill functions. 6 years ago
push_file_service_test.py issue #532: PushFileService race. 6 years ago
reaper_test.py issue #627: add test and tweak Reaper behaviour. 5 years ago
receiver_test.py issue #477: stop using router.fork() in receiver_test 6 years ago
requirements.txt cffi super old, try and update it 4 years ago
responder_test.py issue #590: whoops, import missing test modules 5 years ago
router_test.py Merge devel/290 @ 79b979ec8544ef5d8620c64068d4a42fabf50415 5 years ago
select_test.py select: make Select.add() handle multiple buffered items. 5 years ago
service_test.py tests: add a few extra service tests. 5 years ago
setns_test.py disabled flaky test 5 years ago
signals_test.py issue #477: more fork removal 6 years ago
ssh_test.py tests: clean up old-style SSH exception catch 5 years ago
su_test.py [stream-refactor] remove one more getuser() usage 5 years ago
sudo_test.py disabling another flaky test 5 years ago
testlib.py mitogen_test_distro appeared to not be used which broke centos7 trying to run doas not in debian container, so fixing that 5 years ago
timer_test.py Add mitogen.core.now() and use it everywhere; closes #614. 5 years ago
two_three_compat_test.py issue #477: util/fakessh/two_three_compat fixes. 6 years ago
types_test.py tests: note location of related tests. 5 years ago
unix_test.py Add mitogen.core.now() and use it everywhere; closes #614. 5 years ago
utils_test.py tests: move affinity_test to Ansible tests. 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.