You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A big part of the reason Brownie offers a limited subset of pytest flags is because of the amount of voodoo happening to allow things like with isolation and coverage. The test surface is exponentially larger when you add in all the extra flags, almost definitely something will end up breaking. Forcing the user to type python -m pytest in my mind is akin to an acknowledgement of "I'm doing something that might not be supported".
That said, I'm not inherently opposed to this change. Perhaps raising a warning with it's use that "here be (maybe) dragons" - this would be even more explicit than the current approach.
Overview
I have some tests marked xfail and I noticed that they started passing.
I tried to get more info about these like the pytest docs say to, but brownie doesn't pass these flags through.
Specification
Rather than add a bunch of flags to brownie, I think there could be a "--" flag and everything after that just gets passed to pytest.
The text was updated successfully, but these errors were encountered: