Here's how I'm thinking about moving forward: we currently have @Rule,
which provides a way to override the rules for _running_ a method, for
_every @Test_ method in the class. I'm considering a similar
construct, which will allow overriding:
1) Which methods trigger tests
2) How many tests per method
3) Validation of test methods
4) Test-instance creation
5) Test-method invoking
Given this, it should be possible to enable something very close to
@NonParameterized as a drop-in Rule-like object, rather than as a core
modification to the overall Parameterized runner.
It's a bit abstract for me, I can not imagine/picture how my use case will look like with this. With the above features it sounds like it will be quite useful.
If you like you can make a sudo example to show how you imagine it to be used.
One issue: I can't think of a name for this new construct. Suggestions welcome.
One problem that I noticed with @RunWith(JUnitParamsRunner.class) tests is that
IDE support lags a bit or maybe its a bug, but from eclipse I can't re-run a single method or one of it's permutations or jump to its location by double-clicking on it in the junit panel. It works fine with @RunWith(value = Parameterized.class) which I'm glad to see.
Before I knew about this, I made my own suite implementation to sort of do this,
and with some tweaking I was able to get eclipse to be able to re-run those too.