flaky
flaky copied to clipboard
box
Plugin for nose or pytest that automatically reruns flaky tests.
I was trying to inspect the current stack of the raised exception. For some reason, I'm receiving an stdlib `traceback.traceback` object in the PyCharm debugger, but pytest's internal `_pytest._code.Traceback` object...
I see the tests are not rerunning if there is any exception at the fixture level and tests fail because of it. Could you please help. Thanks in advance. Following...
`flaky` re-runs tests that fail in teardown, but test suite result is always `ERROR`. 🤔 Meanwhile if test fails in the test itself, it is reran, and test suite result...
In the case of when the user is using `force-flaky`, it would be useful to be able to provide a filter function as well that can be used globally. I...
Hi, I've also filed this under https://github.com/okken/pytest-check/issues/25, but since the issue arises only when using both plugins together, I'm not sure where the responsibilities lie, so flagging it with both...
前提：执行最后一个case。 步骤：设置case，@flaky(max_runs=3, min_passes=1) 实际结果：当第一次case失败后，就会去执行：teardown_class。 预期结果：运行完3次case之后，再去执行teardown_class
Depending on test runtime and repetition count flaky tests can take a long time to complete. It would be nice if there was some feedback on flakyness during the test...
When I am using flaky with pytest, I see multiple copies of `` element in the XML output for the same test if it was reran by flaky. ```
I have a pytest fixture which runs at the "session" scope. This fixture starts a local web server, and initiates a sauce labs connection. Upon teardown, it stops the server...
I have a single test that has a: ``` @pytest.xfail(reason="Fails on Ubuntu, works on CentOS") ``` When that is hit in one of the test runners using xdist, the following...
