Coverage-testing and Profiling a Catalyst application?

jdrago_999 has asked for the wisdom of the Perl Monks concerning the following question:

Monks!

I recently wrote a short article about performing code-coverage testing on an Apache2::ASP web application.

I am about to make another article on using Devel::NYTProf on your Apache2::ASP web application as well.

It got me wondering...how would I go about doing code-coverage and profiling on a Catalyst application? Also is there any way to profile and get coverage analysis of your views? How about your controllers?

Thanks!

Comment on Coverage-testing and Profiling a Catalyst application?

Replies are listed 'Best First'.
Re: Coverage-testing and Profiling a Catalyst application? by moritz (Cardinal) on May 23, 2008 at 18:12 UTC
It got me wondering...how would I go about doing code-coverage and profiling on a Catalyst application? The coverage part should be quite easy: write your tests, write a Buil.PL for and then run `perl Build.pl; ./Build testcover` (I don't know if the default Makefile.PL has the `testcover` target). If you configure your catalyst app as shown in Catalyst::Manual::Tutorial the debugging output shows timing informations for different request stages - not a full profile, but still very useful.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Coverage-testing and Profiling a Catalyst application?
by moritz (Cardinal) on May 23, 2008 at 18:12 UTC

It got me wondering...how would I go about doing code-coverage and profiling on a Catalyst application?

The coverage part should be quite easy: write your tests, write a Buil.PL for and then run perl Build.pl; ./Build testcover (I don't know if the default Makefile.PL has the testcover target).

If you configure your catalyst app as shown in Catalyst::Manual::Tutorial the debugging output shows timing informations for different request stages - not a full profile, but still very useful.

[reply]
[d/l]
[select]