-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Please allow Iterable as type for @DataPoints #126
Comments
Duplicate of issue 110 (but you're right, there's no reason to exclude Iterables as well). |
Proposing for 4.12 |
Mostly #658 actually, but #651's involved too. On a related note: I'd actually thought that this was slowly migrating across to junit.contrib, so I'd been completely ignoring it for a while now really while that dust settled. Is there an ongoing plan for that? Currently looks like it's got the 4.11 implementation, but none of the 4.12 bits yet. I assume the plan is to pull those changes across (e.g. the fix for this), tidy them up (i.e. fix #673) and then push a release, yes? (And then pull it out of JUnit proper). If that's true and there's nothing else much going on on this now, I might try and take a look at sorting that out in the next month or so. Would that be useful? |
Great, that's what I thought. On your related note: @pimterry, yes, that's the medium-term plan (since getting theories Right involves either depending on things we don't want core JUnit depending on, or re-implementing things core JUnit has no business re-implementing.) And help is definitely appreciated. Be sure to also check in with @pholser, who's done the bulk of the heavy-lifting thus far. |
Happy to start rolling 4.12-ish theory changes into contrib once 4.12 goes live. |
Just for reference: this issue was eventually resolved by #658. |
Often it is easier to just return a Collection that contains the data points. Therefore I think it will be helpful to allow additional return types for those methods.
I suggest Iterable, but at least Collection should be allowed.
The text was updated successfully, but these errors were encountered: