Of the three, I've only used JProbe, so my input value is limitted. Jprobe has some pretty nice profiling features, and it will run in non-interactive mode spitting data into a file to be analyzed later. So if you're trying to find out why your server applications are running slow/large, it can help quite a bit. Other than that, of course, there is the standard step-through-the-running-code widget, which supposedly works well with multi-threaded apps, but I've never used that part. It has a pretty nice Iface, but if you want to do something specific, there can be a bit of an rtfm investment to find out how to do what you want. Hope that helps a little. Bill --- Bob Tanner <tanner at real-time.com> wrote: > 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 __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/