tag:blogger.com,1999:blog-9238405.post116499115167930423..comments2024-03-18T02:04:50.380-07:00Comments on Agile Testing: "Performance Testing with JUnitPerf" articleGrig Gheorghiuhttp://www.blogger.com/profile/17863511617654196370noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-9238405.post-1165041099711580052006-12-01T22:31:00.000-08:002006-12-01T22:31:00.000-08:00Hi Grig: Looks like a good article. I maintain Tes...Hi Grig: Looks like a good article. I maintain <A HREF="http://www.pushtotest.com" REL="nofollow">TestMaker</A> - the open-source SOA test automation tool. It has a proxy recorder to create Jython-based JUnit TestCase classes. TestMaker turns the TestCase functional test into a scalability and performance test with its XSTest framework. The advantage here is Jython's ability to use Java classes to implement functional tests and then turn them into load tests with minimal effort. -FrankAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-1164995932090782702006-12-01T09:58:00.000-08:002006-12-01T09:58:00.000-08:00Yeah, functional tests are probably a better targe...Yeah, functional tests are probably a better target for performance testing. But if you read the article, even individual methods can be tested for performance at the unit test level.Grig Gheorghiuhttps://www.blogger.com/profile/17863511617654196370noreply@blogger.comtag:blogger.com,1999:blog-9238405.post-1164995825782368512006-12-01T09:57:00.000-08:002006-12-01T09:57:00.000-08:00Isn't it conventional wisdom that you want to perf...Isn't it conventional wisdom that you want to performance test your *functional* tests, rather than your unit tests?<BR/><BR/>(This is because unit tests don't generally represent common "paths" through the code; instead, they test *most* paths through the code. What you want to optimize are what people *actually* do, not what your unit tests do.)<BR/><BR/>--titusAnonymousnoreply@blogger.com