I use all three at work. They're all for different types of testing. JUnit is required for unit tests. We write unit tests for our code, and use these as regression tests also. JProbe is used for fixing performance/memory problems. It allows us to figure out what are the slow pieces of code and where memory is causing performance problems. JTest is for the monkey on the keyboard testing. Just call every method you have and see what breaks. This is also useful because it catches cases you missed with your unit tests. Although I've found it tends to handle interfaces and factory models poorly. Bob Tanner <tanner at real-time.com> writes: > I have been using JUnit on many of my projects. It works fine, but as time > tables shrink, I started to look for something more automated. > > I found JTest and JProbe. > > Anyone have any comparisions they would like to share? Both JTest and JProbe are > pricy and I don't want to go down that path if they aren't much better then > JUnit. > > -- > Bob Tanner <tanner at real-time.com> | Phone : (952)943-8700 > http://www.mn-linux.org | Fax : (952)943-8500 > Key fingerprint = 6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9 > > _______________________________________________ > tclug-devel mailing list > tclug-devel at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-devel -- Jon Schewe | http://mtu.net/~jpschewe | jpschewe at mtu.net For I am convinced that neither death nor life, neither angels nor demons, neither the present nor the future, nor any powers, neither height nor depth, nor anything else in all creation, will be able to separate us from the love of God that is in Christ Jesus our Lord. - Romans 8:38-39