pytest-testinfra
pytest-testinfra copied to clipboard
pytest-dev
Testinfra test your infrastructures
Version 3.0 (all from .0.0 to .0.5) breaks connections to ansible hosts behind a "jumphost or bastionhost". (#439 Doesn't fix it) What worked fine in 2.x version now doesn't. For...
With the latest testinfra version during a molecule setup, it seems that the port is used for picking up the container: ``` No such container: instance:7525\ ``` But the port...
Hello @philpep, thanks for the great project. I'm struggling to write custom testinfra modules that extend the builtins, e.g. `File`. Right now I'm trying to write a module for checking...
I'm using this snippet of code to test listening ports: ``` def test_listening_socket(host): listening = host.socket.get_listening_sockets() for spec in ( "tcp://:::22", "tcp://:::5432", ): socket = host.socket(spec) assert socket.is_listening ``` but...
I have a somewhat strange test case scenario that I'm currently handling via pytest/fabric (as quirky as that interaction is). For the purposes of testing a new image, I spin...
When both testinfra and [pytest-ansible](https://pypi.python.org/pypi/pytest-ansible) are installed, testinfra fails with the following output: ``` $ testinfra --connection=ansible --sudo --ansible-inventory=inventory test_proxy.py Traceback (most recent call last): File "/home/ivan/cde/devops/devops-env/bin/testinfra", line 11, in...
I am unable to run the iptables functionality ```python def test_iptables_rules(host): rules = host.iptables.rules(table=u'filter', chain=u'INPUT') ``` How I invoke it ```bash $ py.test-s --connection=ansible --ansible-inventory ./myhosts --hosts="agroup" mytest.py ``` In...
It would be nice to be able to pass arguments to `host.sudo()`. My use-case for this is needing to have the `$HOME` environment variable set in the target user's environment....
Hello, Consider the following basic WinRM test: ``` def test_echo(host): hello = 'Hello, world!' res = host.run('echo %s', hello) assert res.stdout == hello # Fails ``` ``` assert res.stdout== hello...
Not sure if this is a bug or something which has not yet been implemented yet. If the latter it should probably be documented. I just tried to call a...
