Anatoly Bubenkov
Anatoly Bubenkov
@blaise-io good that you've mentioned providing access to pytest-dev organization for all the pytest rtd projects that paylogic has access to. However, it seems there's no dedicated shared account for...
makes total sense to me
looks like we should check for existence of /dev/log then, in this fixture: ``` @pytest.fixture(scope='session') def services_log(slave_id): """A services_logger with the slave id.""" handler = None for kwargs in (dict(socktype=socket.SOCK_RAW),...
I think the solution is to simply use docker for most if not all services: ```python @pytest.fixture(scope='session') def mysql_watcher( request, run_services, watcher_getter, mysql_system_database, mysql_pid, mysql_socket, mysql_data_dir, mysql_defaults_file): """The mysqld process...
@di please submit a PR addressing it
you can override a fixture / set the option to have implicit wait timeout be 0, which should effectively disable implicit wait
Thank you. But please update the README in master, as the example there is outdated. On Mon, Apr 21, 2025 at 11:58 PM Noel Towa ***@***.***> wrote: > Sorry for...
The scenario you have doesn't make sense to me You've made it that there's no way for user to understand what's in u'eat', u'left', u'start' If they are not important...
it's perfectly supported, but without mentioning it in the scenarios directly eg you can have implicit (pytest) and explicit (scenario) parametrisation
still your explanation is not clear, scenario text should make sense as a scenario, it's NOT a program, it's a business case