[Raleigh-talk] Testing

[Jason Purdy]

Testing is awesome - that's what I'm actually in the middle of right now. My
boss decided to take one of our applications and make it available on
another site. Since I wrote several test scripts for the original
application, I was able to move it over to the other site and adapt the test
scripts and over these last few days, I've been able to hammer out the bugs
and have great confidence that the application on the new site will be
pretty well-QA'd.

We develop web applications and those are tough to test entirely from Perl.
So we (I ;) ) split test cases into client-side (I've used Selenium and
YUITest) to test javascript code and then Test::More (I just dabbled w/
Test::HTML::Content today and love it ... really can't go wrong w/ anything
Test::* can you? ;)) to test the web application code (written w/
CGI::Application).

I touched a little bit about my approach in my use.perl
journal<http://use.perl.org/%7EPurdy/journal/38209>
.

Cheers,

Jason

On Wed, Feb 4, 2009 at 2:28 PM, Trevor Little <trevormg19 at gmail.com> wrote:

> I was wondering how many of you write tests for your code on a regular
> basis. What modules do you use to make that easier? I'm familiar with the
> Test::{Simple,More,Deep,...} family, but are there others anyone has used
> and likes? Does anyone work in a place were unit testing is enforced or at
> least strongly encouraged? I guess I'm just trying to figure out how other
> companies/people approach this kind of unit testing.
>
> Thanks,
> Trevor
> _______________________________________________
> Raleigh-talk mailing list
> Raleigh-talk at pm.org
> http://mail.pm.org/mailman/listinfo/raleigh-talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/raleigh-talk/attachments/20090204/078ca9f7/attachment.html>