The issue with junit4 is that the suite definition is in an annotation and therefore has to be defined at compile time, so there is no mechanism to define tests at runtime.
manifest based code I did attempted to provide a mechanism to create the tests are runtime. Perhaps there is a common point here such that we can build an annotation suite that will allow identification of a test suite using annotations but delay the creation of the tests until runtime so that further configuration can be applied. Thoughts? Claude On Thu, Mar 27, 2014 at 4:49 PM, Jeremy J Carroll <[email protected]> wrote: > > > On Mar 26, 2014, at 2:21 PM, Andy Seaborne <[email protected]> wrote: > > > We (you, me, jeremy) seem to have ended up in a similar place. > > > I have used junit4 for quite a bit now, but I definitely like the ability > to define my own test suites programmatically, (which is needed for your > use case) and the Parameterized Test Runner that comes built-in is close > but not close enough; hence I roll my own > > > -- I like: Like Like - The likeliest place on the web<http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
