We had lots of speed and memory issues as our cucumber test base grew. Using pl_analyze was a great start - http://www.linuxjournal.com/article/10128 . It gives you detailed summary information of the slowest regions of your code.
Our test were heavy on fixtures. I used this to finally diagnose a memory leak in cucumber. http://gist.github.com/69869 I took a memory footprint before and after loading the fixtures before each test (we destroyed all db records before loading), and watched the memory climb in a steady pattern. I've reported the issue at lighthouse. As our test base grew we had to keep upping the ram on the test slice (we did so twice). Finally, we worked out how to use transactional fixtures in cucumber, and builds went from taking eons to about three minutes. Regards, Nicholas On Mar 20, 4:18 pm, Torm3nt <[email protected]> wrote: > Hey all! > > Hope everyone is up to something this weekend, weather is looking good (at > least in Sydney =P) > > I currently work on a couple of projects, all utilising rspec/selenium.etc. > 2 of our projects run very fast in terms of running tests, however one is > very slow, and I can't for the life of me figure out why. Is there any way > to benchmark your tests so as to find the bottleneck? The project in > question is one of our smallest, and yet it runs 2-3x slower than the > others. > > Any ideas? > > Kirk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
