Jim Brännlund
Jim Brännlund
That's actually what we do [today](https://github.com/pytest-dev/pytest-metadata/blob/master/.github/workflows/publish.yml) But that doesn't cover what you're after.
Can you create a reproducible test case including all pertinent information (versions etc.)?
From the example you provided, you're not using this plugin. It should look like: test_base.py ```python def test_base(driver): driver.get("https://google.com/") ``` Given you've passed in the `--driver chrome` argument to pytest....
Closing this for lack of interaction. Feel free to re-open.
@rindPHI @mnaumann-plenty Mind trying out `4.0.0rc1` ?
This should be supported in v4 now.
/remove-lifecycle stale
/remove-lifecycle stale
> @jbedard Interesting - I'll take a look at your PR for inspiration here, thanks for that. > > One other disadvantage I was thinking about with pnpm workspaces though...
Let me know if you encounter a specific use-case wrt. internal or external dependencies that doesn't work you. The approach when publishing packages to NPM requires a bit more "stuff"...