Ashley C Straw

1. create a hooks.py file, containing the new hook as a stub 2. use ``pytest_addhooks`` to register the new hook 3. in pytest_assume, extract the current output into the new...

I think it's about 80% of the way there, just a few notes. 1. rename the hook to "pytest_assume_summary_report" 2. extract the existing output to the new hook (just make...

Hi @mbednarski, This was a part of a change to make pytest-assume play nicer with other plugins. I'll see what I can do about it, because it really isn't pretty...

As an update, I pushed a change to the 'traceback' branch that changes the output: ``` __________________________________ test_func __________________________________ tp = , value = None, tb = None def reraise(tp,...

I'm thinking it might be because six doesn't have ``__tracebackhide__`` in it, or the implementation of the reraise function itself. Vendoring that function (& adding ``__tracebackhide__`` & ``raise exc.with_traceback()``) shows...

I believe it's due to pytest's assertion rewriting & exception handling.. When we have a simple test: ``` def test_one(): with pytest.assume: assert 1 == 2 ``` We get pytest's...

I think the solution is still leveraging pytest's AST assertion rewriting to also rewrite pytest.assume. Unfortunately, my situation hasn't changed in that I can't devote the time necessary right now...

That is expected. We only hook into `runtest_call`, not fixture setup/teardown.