TestCase: data provider supports \Traversable - #272
Merged
Conversation
Contributor
Author
There was a problem hiding this comment.
ok, I'll get rid of it
Contributor
|
👍 |
Member
|
What about to support |
Contributor
Author
|
@milo I thought about it, but didn't find any use case for |
jiripudil
force-pushed
the
feature/dataprovider-generator
branch
from
November 13, 2015 17:16
870b790 to
027fb44
Compare
Contributor
Author
|
I've added support for Traversable and squashed the branch into a single commit. |
Member
|
Imho ready to merge. I left few CS hint comments. |
Contributor
Author
|
@milo I've fixed the CS compliance. Should I squash it now? |
Member
|
Yes please. |
jiripudil
force-pushed
the
feature/dataprovider-generator
branch
from
November 14, 2015 17:33
98b0db6 to
7066509
Compare
Contributor
Author
|
Squashed. |
milo
added a commit
that referenced
this pull request
Nov 14, 2015
TestCase: data provider supports \Traversable
Member
|
Thank you. |
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
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.
I've found that if you want to return some more complex structures from a data provider or even do some other logic to it inbetween, generators seem to be a more convenient approach than arrays.
In my case, I need to test data validation of a third-party API, generating a valid request and breaking it in a lot of slightly different ways, and generators just seem to be much more expressive: