Ronny Pfannschmidt comments

Results 1747 comments of


                                            Ronny Pfannschmidt

Create a pytest plugin that is the official methodology for managing resource lifecycles

@gsmethells pytest is **under no circumstances** suitable as a container PID 0

Create a pytest plugin that is the official methodology for managing resource lifecycles

im incline to close this issue as the particular key here is incorrect termination from the outside, we might want to add a doc section on correct termination setup for...

Double reporting teardown failure

@asottile as this one is about sometimes doublse, sometimes single entries in the junit report, i do wonder if we should take it as a bug, but its not clear...

Double reporting teardown failure

@asottile as im reading this again on a computer, its clearly doing something wrong it should report the teardown errors in the junit and it shouldnt have double reports blindly...

Package scoped fixture will not execute teardown

to add extra context, each import of a fixture creates a new definition point, thus iporting the fixtures to closer file location points fixes the issues by creating new definitions...

Cannot use pytest.mark.usefixtures() in pytest.param

linking https://github.com/pytest-dev/pytest/issues/349#issuecomment-428680193 as it has some more details on the problem

Cannot use pytest.mark.usefixtures() in pytest.param

marks on fixtures are NOT supported and won't be

pytest_fixture_setup hook doesn't run for session scoped fixture

I see, it's quite tricky to decide whether this is a feature or a bug But im leaning towards bug since the location should matter

disable_test_id_escaping_and_forfeit_all_rights_to_community_support not working

the output doesn't indicate that a configfile is used, thats most interesting

disable_test_id_escaping_and_forfeit_all_rights_to_community_support not working

A extra arg to param is not acceptable