New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid getfuncargvalue #97

Closed
pelme opened this Issue Sep 6, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@pelme
Member

pelme commented Sep 6, 2017

getfuncargvalue is deprecated and raises warnings:
https://docs.pytest.org/en/latest/builtin.html#_pytest.fixtures.FixtureRequest.getfuncargvalue

We should stop using it and switch to getfixturevalue instead. getfixturevalue has been around for a while now and I think we can just change it.

pelme added a commit to pelme/pytest-splinter that referenced this issue Sep 6, 2017

Use getfixturevalue instead of getfuncargvalue.
getfuncargvalue is deprecated and raises warnings.

Fixed pytest-dev#97.

pelme added a commit to pelme/pytest-splinter that referenced this issue Sep 6, 2017

Use getfixturevalue instead of getfuncargvalue.
getfuncargvalue is deprecated and raises warnings.

Fixed pytest-dev#97.

@bubenkoff bubenkoff closed this in #98 Jun 3, 2018

bubenkoff added a commit that referenced this issue Jun 3, 2018

Merge pull request #98 from pelme/getfixturevalue
* Use getfixturevalue instead of getfuncargvalue.

getfuncargvalue is deprecated and raises warnings.

Fixes #97.

* Ensure pytest>=3.0.0 is used to support getfixturevalue().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment