$ py.test --driver Chrome camayoc/tests/qcs/ui/test_login.py
=============================================== test session starts ===============================================
platform linux -- Python 3.6.4, pytest-3.3.1, py-1.5.2, pluggy-0.6.0
driver: Chrome
sensitiveurl: .*
metadata: {'Python': '3.6.4', 'Platform': 'Linux-4.14.14-300.fc27.x86_64-x86_64-with-fedora-27-Twenty_Seven', 'Packages': {'pytest': '3.3.1', 'py': '1.5.2', 'pluggy': '0.6.0'}, 'Plugins': {'wait-for': '1.0.9', 'xdist': '1.20.1', 'variables': '1.7.1', 'selenium': '1.11.4', 'metadata': '1.5.1', 'html': '1.16.1', 'forked': '0.2', 'cov': '2.5.1', 'base-url': '1.4.1'}, 'Base URL': '', 'Driver': 'Chrome', 'Capabilities': {}}
rootdir: /home/elyezer/code/camayoc, inifile:
plugins: wait-for-1.0.9, xdist-1.20.1, variables-1.7.1, selenium-1.11.4, metadata-1.5.1, html-1.16.1, forked-0.2, cov-2.5.1, base-url-1.4.1
collected 1 item
camayoc/tests/qcs/ui/test_login.py . [100%]
============================================ 1 passed in 3.59 seconds =============================================
I think it worth using pytest-selenium to remove all the boilerplat to configure and have an isolated browser instance for each test. Also it is easy to run locally and the remote browser (such as on a docker container or sauce labs)