Permit variable-level scopes for client fixture.#970
Open
faelin wants to merge 1 commit intodbfixtures:mainfrom
Open
Permit variable-level scopes for client fixture.#970faelin wants to merge 1 commit intodbfixtures:mainfrom
faelin wants to merge 1 commit intodbfixtures:mainfrom
Conversation
Sometimes a user might not *want* the client fixture to be function-scoped. For example, another fixture may rely on the connection info of the client, such as port-number, and might want that data to remain static throughout a session, or might need that data in a session-scoped fixture.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sometimes a user might not want the client fixture to be function-scoped. For example, another fixture may rely on the connection info of the client, such as port-number, and might want that data to remain static throughout a session, or might need that data in a session-scoped fixture.
Chore that needs to be done:
pipenv run towncrier create [issue_number].[type].rstTypes are defined in the pyproject.toml, issue_number either from issue tracker or the Pull request number