<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 1, 2012, at 11:45 AM, George Hartzell wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Sounds to me that it was the back end. If that's true and you've<br><armchair_quarterbacking> sliced things "right"<br></armchair_quarterbacking> then you can beat the day lights out of it<br>without having to get any of the web ui involved.<br><br>My favorite tools in those cases have always been hand rolled and not<br>particularly graceful, either doing something that I expect to be<br>troublesome or actually replaying events from traces of real activity.</span></blockquote><br></div><div>Right -- the failure was in the back end not the UI. I know I can use WWW::Mechanize to simulate a bunch of user activity. What I was looking for was a framework for doing that activity simultaneously (i.e. as multiple concurrent users) and tracking performance along the way. I'm sure I can do that with the right combination of Test::* modules and forking. I just thought there might be something ready-made.</div><div><br></div><div>-Jeff</div><br></body></html>