Well, just some howto for example, explaining what to do exactly to create a JUnit "test skeleton" in an automatic way (if possible at all)
If I get it correctly, if I create an EJB with xdoclet, I'd only have to test 1 of all the resulting files, namely the one I wrote myself... It's just that it's a bit vague to me how I can get started, writing such a test (as automatically as possible)... Thanks Hans On Sun, 2002-11-24 at 02:42, Erik Hatcher wrote: > I don't quite understand the question. We're happily using JUnit > testing by calling our session beans through our "proxy" object (a > custom <utilobject> template) which uses the generated home/remote > interfaces. > > There is no difference in how our JUnit tests interface with the > generated code than how our production code interfaces with it. > > Can you clarify your question more or provide an example of what you're > after? > > Erik > > > SainTiss wrote: > > Hi, > > > > Is there an example somewhere of a JUnit test written with the help of > > the JUnit ant task, on some XDoclet generated EJB code? > > > > Thanks > > > > Hans > > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user >
signature.asc
Description: This is a digitally signed message part
