Brian Okken
Brian Okken
Agree with @joaonc . README is fine.
`check.any_failures()` is now implemented, so a workable workaround is: `assert not check.any_failures()`
--slowlocals is implemented in pytest as part of the traceback handling. See repr_locals call in repr_traceback_entry() Since pytest-check doesn't use pytest traceback mechanism, this isn't going to work. It would...
this isn't really an issue and I don't want to track it in issues, so closing for now.
@kapis90 I understand the request. I also understand the want. It's really a separate request, I think, from the original want. PR #115 solves the original issue, hopefully, but doesn't...
See changelog for `set_failure_callback()` on version 2.1.0
No current plans. Do you want to implement it?
Seems to work fine now, with pytest 7.4.2 and pytest-repeat 0.9.2 ```python import pytest @pytest.mark.parametrize('a', (10, 20)) def test_foo(a): ... ``` test run: ``` (pytest-repeat) $ pytest test_param.py -v --count...
The act of using `--count 3` changes the nodeids, so with `--count 3`, `test_foo[10]` no longer exists. There is a workaround, selecting parameters by keyword instead of nodeid: ``` (pytest-repeat)...
We also cannot select individual counts using nodeid: ``` (pytest-repeat) $ pytest 'test_param.py::test_foo[10-2-3]' =========================== test session starts ============================ collected 0 items ========================== no tests ran in 0.00s =========================== ERROR: not...