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
Alex Willmer 9cdd51cf5b Declare Python 3.13 support
No code changes needed, that I could find.
2 months ago
..
ansible ansible_mitogen: Support templated SSH port 2 months ago
bench
data trivia: Fix trailing whitespace 2 months ago
image_prep trivia: Fix trailing whitespace 2 months ago
soak
README.md CI: Remove Azure DevOps pipelines (replaced by GitHub Actions) 2 months ago
__init__.py
broker_test.py prefer newer unittest.mock from the standad library 8 months ago
buildah_test.py
call_error_test.py
call_function_test.py
channel_test.py
connection_test.py tests: Remove unused import 2 months ago
constraints.txt CI: Workaround "No module named 'setuptools.command.test'" 4 months ago
context_test.py
create_child_test.py mitogen: Fix subprocess ResourceWarning 3 months ago
doas_test.py
docker_test.py
error_test.py
fakessh_test.py
file_service_test.py
first_stage_test.py
fork_test.py
id_allocation_test.py tests: Shutdown contexts on completion 3 months ago
importer_test.py prefer newer unittest.mock from the standad library 8 months ago
io_op_test.py prefer newer unittest.mock from the standad library 8 months ago
iter_split_test.py mitogen: Consolidate back compatibility fallbacks and polyfills in mitogen.core 2 months ago
jail_test.py
kubectl_test.py
latch_test.py
local_test.py
log_handler_test.py prefer newer unittest.mock from the standad library 8 months ago
lxc_test.py mitogen: Consolidate back compatibility fallbacks and polyfills in mitogen.core 2 months ago
lxd_test.py
master_test.py
message_test.py prefer newer unittest.mock from the standad library 8 months ago
minify_test.py
mitogen_protocol_test.py prefer newer unittest.mock from the standad library 8 months ago
module_finder_test.py
nested_test.py
os_fork_test.py
parent_test.py prefer newer unittest.mock from the standad library 8 months ago
podman_test.py
policy_function_test.py prefer newer unittest.mock from the standad library 8 months ago
poller_test.py mitogen: Consolidate back compatibility fallbacks and polyfills in mitogen.core 2 months ago
polyfill_functions_test.py
push_file_service_test.py
reaper_test.py mitogen: Fix subprocess ResourceWarning 3 months ago
receiver_test.py
requirements-tox.txt mitogen: Support Python 3.12 8 months ago
requirements.txt Declare Python 3.13 support 2 months ago
responder_test.py prefer newer unittest.mock from the standad library 8 months ago
router_test.py
select_test.py
service_test.py
setns_test.py
signals_test.py
ssh_test.py tests: Shutdown contexts on completion 3 months ago
su_test.py
sudo_test.py
testlib.py ci: Extract container registry location into variables 2 months ago
timer_test.py prefer newer unittest.mock from the standad library 8 months ago
two_three_compat_test.py CI: Migrate macOS integration tests to macOS 12, drop Python 2.7 jobs 4 months ago
types_test.py
unix_test.py tests: Don't suppress output while testing unix Listener 3 months ago
utils_test.py mitogen: Raise TypeError on `mitogen.utils.cast(custom_str)` failures 8 months 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.