Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I wonder if your post today was inspired by what I wrote in reply [perl.org] to your last post or we're just on the same wavelength with this. :)

    At YAPC::NA this year I did a lightning talk on a web-testing framework I built for a client*. The main topic was just that the tests were all data-driven, and because of that I gained a pile of great functionality, not least of which was the ability to turn my test suite into a benchmarking suite seamlessly.

    By running via prove or directly, each script was a set of unit
    • It's mostly because of some issues at work.

      We've got ourselves a shiny new load testing environment, which is useful for catching major performance regressions.

      But it doesn't easily catch slowdowns in strange and unusual places. Stuff beyond just the "scrape the website" tests, things that only run in the backend and do a lot of heavy lifting.

      What we'd like is a way to have a benchmark suite that sits in the project, runs nightly with the smoke tests, and logs to a database so that we can do performance trend-spotting on specific functions or processes.

      Web performance testing is important too, but more complex. The one we need the most is a way to test more tightly than that.