3.0.2 testinfra not working on freshly initialized role

Issue Type

• Bug report

Molecule and Ansible details

docker run -v $(pwd):$(pwd) -w $(pwd) quay.io/ansible/molecule:3.0.2 molecule init role --verifier-name testinfra foobar
docker run -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd):$(pwd) -w $(pwd) quay.io/ansible/molecule:3.0.2 molecule test

Molecule installation method (one of):

• docker

Ansible installation method (one of):

• docker

Detail any linters or test runners used:

Desired Behavior

The default tests should run without any problems

Actual Behaviour

an error is thrown

ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: --connection=ansible --ansible-inventory=/root/.cache/molecule/foobar/default/inventory/ansible_inventory.yml
  inifile: None
  rootdir: /home/xxx/Downloads/Projects/test/foobar/molecule/default

[ssbarnea]

Closing because it was fixed on master, next release will include testinfra inside the container.

[unglaublicherdude]

Oh. IMHO that’s a bad decision. I guess, for most of the molecule users testinfra is still the default. And it is a really bad user experience, when I can initialize something with your docker image, but the run itself without custom changes just fails.