Document pytest.param #2881
Merged
Document pytest.param #2881
Conversation
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
Append example for pytest.param in the example/parametrize document.
|
This PR is targeting #2658 . Any suggestion is welcome! Thanks! |
hackebrot
added
the
type: docs
nicoddemus
approved these changes
Oct 29, 2017
|
as far as i can tell the ci errors are unrelated, thanks 👍 |
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this pull request
Nov 9, 2017
I spent some time today figuring out why PR pytest-dev#2881 was not showing up on doc/parametrize... then after some digging even on readthedocs wondering if the last documentation build had failed, I realized the docs I was looking for was in doc/example/parametrize instead. The section that mentions this is very easy to miss, this makes it a full fledged title and easier to find.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Append example for pytest.param in the example/parametrize document.
Thanks for submitting a PR, your contribution is really appreciated!
Here's a quick checklist that should be present in PRs:
$issue_id.$typefor example (588.bug)removal,feature,bugfix,vendor,docortrivialbugfix,vendor,docortrivialfixes, targetmaster; for removals or features targetfeatures;Unless your change is a trivial or a documentation fix (e.g., a typo or reword of a small section) please:
AUTHORS, in alphabetical order;