Skip to content

TestCase: possibility of named sets in dataprovider #293

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

Closed
wants to merge 3 commits into from

Conversation

stekycz
Copy link
Contributor

@stekycz stekycz commented Mar 3, 2016

Minor features which brings easier distinguishing which data the test is failing for. Useful for larger and more complicated datasets at the input.

$data[$setName] = $set;
} else {
$data[] = $set;
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stekycz All original keys can be preserved in $data[], not only strings.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@milo Unfortunately I can't because it breaks possibility of multiple data providers. The string key must be unique because it is explicit value however two different data providers without naming returns array with indexes 0, 1, 2, ... so it results in wrong data set. You can try it on your own ;-)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, the same string may replace previous dataset too.

Copy link
Contributor Author

@stekycz stekycz Apr 30, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it can. However the probability of that is lower then for regular array. The same string name must be specified explicitly however same array index is quite hard to find where the problem (overriding) is.

@stekycz stekycz force-pushed the dataprovider-named-sets branch from bb4246a to 6a5f7a3 Compare May 18, 2016 09:03
@stekycz
Copy link
Contributor Author

stekycz commented May 18, 2016

Rebased

@dg dg force-pushed the master branch 2 times, most recently from ee525b7 to 6ca248e Compare February 27, 2019 13:34
@dg dg force-pushed the master branch 7 times, most recently from 37f5151 to c3bd1b2 Compare November 19, 2019 13:19
@dg dg force-pushed the master branch 10 times, most recently from f2dae8a to 20b7c0b Compare January 24, 2020 13:18
@dg dg force-pushed the master branch 3 times, most recently from e9c3f27 to 666cb04 Compare July 13, 2020 13:17
@milo milo closed this in ae7292a Jul 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants