On Fri, Jun 10, 2011 at 3:49 AM, Peter De Berdt <peter.de.be...@pandora.be> wrote: > > First of all, running load testing on different methods or a whole scenario > is a waste of time, since it doesn't give you any indication on which method > is underperforming under high server load. Also, filling in forms using > Selenium (or just simulating it using Cucumber) will also yield unreliable > results (running the code that has nothing to do with the actual server also > takes time). What you want is targetted performance tests on one particular > form url, which automatically brings us back to httperf. > If you are looking for load testing with form data, httperf supports this. > Just google "httperf post data" and you'll get plenty of information. Yes, > the way to do it is awful, a nice wrapper around it would be nice.
Have you tried http://blitz.io? Comes with a ruby gem so you can integrate load testing into your continuous deployment. K. --- http://blitz.io http://twitter.com/pcapr http://labs.mudynamics.com -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
