Quoting Jon Schewe (jpschewe at mtu.net): > 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. Has your return on investment on JTest been good? I was quoted $7K for it, so I want to make sure I get $7K out of it. :-) -- 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