Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Utilise scope in pytest.fixture #265

Closed
paddyroddy opened this issue Sep 25, 2024 · 1 comment
Closed

Utilise scope in pytest.fixture #265

paddyroddy opened this issue Sep 25, 2024 · 1 comment
Assignees
@paddyroddy
Labels
enhancement New feature or request

Comments

@paddyroddy
Copy link
Member

Is Your Feature Request Related to a Problem? Please Describe

In general it makes sense to only generate pytest.fixture once, unless it's required to not do that https://docs.pytest.org/en/6.2.x/fixture.html#scope-sharing-fixtures-across-classes-modules-packages-or-session

Describe the Solution You'd Like

No response

Describe Alternatives You've Considered

No response

Additional Context

No response
@paddyroddy paddyroddy added the enhancement New feature or request label Sep 25, 2024
@paddyroddy paddyroddy self-assigned this Sep 25, 2024
paddyroddy added a commit that referenced this issue Sep 25, 2024
@paddyroddy
gh-265: calculate fixture once per testing session (#266)
f26c8c8 
Follows up #241. See explanation
of what the `scope` parameter does for `pytest.fixture`. Seems silly to
not use it (although in this case the speed-up will be minimal).
@paddyroddy
Copy link
Member Author

Closed in #266

Saransh-cpp pushed a commit that referenced this issue Sep 25, 2024
@paddyroddy @Saransh-cpp
gh-265: calculate fixture once per testing session (#266)
83905b3 
Follows up #241. See explanation
of what the `scope` parameter does for `pytest.fixture`. Seems silly to
not use it (although in this case the speed-up will be minimal).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paddyroddy paddyroddy

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@paddyroddy