Having looked at JackRabbit for 2 days, but knowing both JUnit and other test tools fairly well, I would say that unless somebody have made a JackRabbit specific test tool, JUnit is probably your best choice for testing behaviour, but not for performance. JUnit is designed to be a tool to test behaviour.
For performance, you might want to check out JMeter. Sincerely, Jørgen Sivesind malsi wrote: > > I would like to test my code using JUnit in order to see if my code is > doing well in terms of performance and behavior (see if nodes are realy > deleted or not, really read or not, if the right node is read, etc..) > My questions are the following: > > Is JUnit the best way to test my code? > Is there any documentation anywhere for using JUnit for testing an > implementation that uses Jackrabbit ? > > > Fabián Mandelbaum wrote: >> >> Hello, I'm using nothing more than JUnit4, and JackRabbit to do unit >> tests. In the "setup" methods (before, after, beforeClass, afterClass) I >> do the repo >> setup/cleanup/write_status_to_visually_check_if_everything_is fine >> thing, and then just make test methods for each of my classes' public >> methods. >> >> [EMAIL PROTECTED] escribió: >>> I guess you could take the JCR API and maybe the JackRabbit API in >>> combination with JMock to unit test your code. >>> >>> Hth, >>> >>> Nick Stolwijk >>> >>> >>> -----Original Message----- >>> From: malsi [mailto:[EMAIL PROTECTED] >>> Sent: Thu 11/29/2007 9:47 AM >>> To: [email protected] >>> Subject: Junit and jackrabbit >>> >>> >>> >>> >>> Hi, >>> >>> I am implementing classes that access and store nodes in a repository. I >>> would like to test my code using JUnit () >>> >> >> >> > > -- View this message in context: http://www.nabble.com/RE%3A-Junit-and-jackrabbit-tf4895862.html#a14027429 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
