Thnx for answering Vincent. I'm new to Cactus. I thought it worked as fast as junit or at least like dbunit. Of course it is an unvaluable resource for in-container testing. I was just wondering if i had done some bad settings that made my testing going slower.
Thnx. (i bought ur Junit in Action. Nice work! Try to keep the bar green...) "Vincent Massol" <[EMAIL PROTECTED]> ha scritto nel messaggio news:[EMAIL PROTECTED] > Hi Kimbuba, > > I've timed the cactus test suite itself (which uses cactus). It takes > 1mn 40s for 101 tests using Resin 2.1.11. My machine is 1.2GHz. These > tests do not access the database. Roughly a test takes about 1.3 > seconds. You need to add extra time like database access. However, if > you're writing unit tests, a database SQL call should usually not take > longer than 70 ms (and the time to get a connection is negligible if > you're using a data source). If it takes more you need some tuning on > your database (like setting correct indexes, etc) :-) > > <idea>You can actually even wrap a Cactus test in a JUnitPerf suite if > you wish to perform performance tests...</idea> > > Thanks > -Vincent > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
