R: [testedby-dev] Blocking point for a first release

0 views
Skip to first unread message

Alessio Soldano

unread,
Nov 14, 2009, 5:38:03 PM11/14/09
to tested...@googlegroups.com

I've just started reasoning on how to provide a maven plugin, probably going to post on the list about this soon;-)
Stay tuned..
Alessio

Ps. Stefano,take care..ok posting from bed, but..:-)

/sent from my mobile

Il giorno 14/nov/2009 22:34, "Stefano Maestri" <stefano...@javalinux.it> ha scritto:

I'd like to see the first public release of TestsedBy in next few weeks. IMHO we don't need a lot of things completed before we can go for a release. In particular I'm thinking about just two main things:
  • The core need api to create instance of an InterfaceUndertest: when a test is defined on an interface and we are stressing n implementers classes we need to run the same test n times with different instances of that interface under test. I'll take care of this point.
  • A maven or ant plugin to run tests using testedby runner. Of course it's fundamental to have it before a release.
I haven't other blocking point in mind for a first, maybe beta, release. If you have something to add feel free to answer to this post.

bye
S.


Reply all
Reply to author
Forward
0 new messages