mitogen/tests
David Wilson 9d5b3d9e02 issue #477: stop using fork in service_test. 2019-01-26 01:40:02 +00:00
..
ansible issue #477: fix 2 runner tests on Ansible 2.7. 2019-01-25 16:17:29 +00:00
bench issue #415: add IPC latency bench. 2019-01-20 14:04:06 +00:00
data issue #477: build a CentOS 5/Py2.4 container + playbook compat fixes. 2019-01-24 19:57:24 +00:00
image_prep issue #477: build a CentOS 5/Py2.4 container + playbook compat fixes. 2019-01-24 19:57:24 +00:00
soak tests: make cpu_load.py more random. 2018-07-07 14:55:47 +01:00
README.md tests: add new users for conndel tests. 2018-08-18 16:43:59 +01:00
__init__.py tests: Make the tests directory an importable package 2018-04-01 01:32:13 +01:00
broker_test.py core: docstring tidyups 2018-12-14 14:49:34 +00:00
call_error_test.py issue #477: replace type(e) -> __class__ for an exception 2019-01-26 00:48:06 +00:00
call_function_test.py tests: don't call Router.shutdown() twice. 2019-01-19 06:19:55 +00:00
channel_test.py Import and use unittest2 without aliasing it 2018-03-19 21:58:28 +05:45
doas_test.py tests: stub tests for doas/mitogen_doas 2018-11-01 00:49:26 +00:00
docker_test.py issue #406: test for FD leak after every TestCase 2018-11-03 13:28:37 +00:00
error_test.py tests: some more utility function tests + flake8. 2019-01-21 19:38:23 +00:00
fakessh_test.py issue #406: test for FD leak after every TestCase 2018-11-03 13:28:37 +00:00
file_service_test.py tests: file_service_test fixes 2019-01-19 06:19:04 +00:00
first_stage_test.py issue #477: old Py zlib did not include extended exception text. 2019-01-26 00:49:18 +00:00
fork_test.py issue #477: make mitogen.fork unsupported on Py<2.6. 2019-01-25 23:47:08 +00:00
id_allocation_test.py tests: remove stray hard-coded interpreter. 2018-07-07 14:55:47 +01:00
importer_test.py issue #477: _update_linecache() must append newlines. 2019-01-24 16:59:24 +00:00
io_op_test.py issue #477: old Mock does not throw side_effect exceptions from a list 2019-01-26 00:47:35 +00:00
kubectl_test.py issue #409: add kubectl stub and constructor test. 2018-10-31 00:46:47 +00:00
latch_test.py core: Latch.empty() improvements 2019-01-19 22:24:46 +00:00
local_test.py tests: Pythonize env_wrapper.sh, clean up local_test 2018-11-06 16:57:51 +00:00
lxc_test.py issue #477: any() polyfill for lxc_test. 2019-01-26 00:48:38 +00:00
lxd_test.py issue #409: name-prefix stubs so they can be added to PATH 2018-10-31 00:08:33 +00:00
master_test.py issue #406: test for FD leak after every TestCase 2018-11-03 13:28:37 +00:00
minify_test.py tests: make minify_test print something useful on failure 2018-11-04 01:48:04 +00:00
module_finder_test.py issue #477: ModuleFinder now returns Unicode module names. 2019-01-25 15:56:06 +00:00
nested_test.py Initial Python 3.x port work. 2018-07-07 14:55:47 +01:00
parent_test.py issue #477: stop using fork() in parent_test, compatible enumerate(). 2019-01-26 01:39:07 +00:00
policy_function_test.py tests: add some more helper function tests. 2019-01-21 15:25:46 +00:00
poller_test.py issue #415, #477: Poller must handle POLLHUP too. 2019-01-24 15:04:56 +00:00
polyfill_functions_test.py issue #477: rename and add tests for polyfill functions. 2019-01-24 13:27:05 +00:00
receiver_test.py issue #477: stop using router.fork() in receiver_test 2019-01-26 00:49:02 +00:00
requirements.txt Split dev_requirements.txt up according to test mode. 2018-11-06 17:00:17 +00:00
responder_test.py tests: fix responder_test after removing unused imports 2019-01-20 08:11:54 +00:00
router_test.py issue #477: stop using .fork() in router_test, one small 2.4 fix. 2019-01-26 01:14:37 +00:00
select_test.py select: Python 2.x required __nonzero__ for bool(Select) 2018-12-11 23:16:26 +00:00
serialization_test.py tests: some more utility function tests + flake8. 2019-01-21 19:38:23 +00:00
service_test.py issue #477: stop using fork in service_test. 2019-01-26 01:40:02 +00:00
signals_test.py tests: some more utility function tests + flake8. 2019-01-21 19:38:23 +00:00
ssh_test.py issue #436: decode debug log lines on Python 3. 2019-01-20 12:31:38 +00:00
stream_test.py core: detect stream corruption. Closes #438. 2018-12-10 02:23:26 +00:00
sudo_test.py issue #410: support sudo --user and SELinux options, add stub test. 2018-10-31 15:46:59 +00:00
testlib.py issue #477: Popen.terminate() polyfill for Py2.4. 2019-01-26 01:38:03 +00:00
two_three_compat_test.py tests: quieten a bunch of spam printed during run 2019-01-20 07:10:37 +00:00
types_test.py issue #477: fix new KwargsTest on Python 3.x. 2019-01-25 16:02:26 +00:00
unix_test.py tests: stray socket file left during unix_test. 2019-01-20 07:15:53 +00:00
utils_test.py issue #406: test for FD leak after every TestCase 2018-11-03 13:28:37 +00:00

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.