worr has asked for the wisdom of the Perl Monks concerning the following question:
Hey PerlMonks!
I'm writing a Perl module that uses a popular social networking website. Obviously I'd like to write some good unit tests so that I can verify that my code works, but I'm at a loss at the best way to do this.
Since data on the site has a tendency to fluctuate often, what kind of stuff should I do to set up my tests? Should I some of the methods test against my own account and hope the expected results don't change?
Also, I use Moose in my Perl module, but should I really bother testing the methods that it writes for me?
I'm new to Perl testing, so any help would be appreciated.
Thoughts?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Testing perl modules that rely on remote data
by Corion (Patriarch) on Aug 01, 2010 at 19:13 UTC | |
Re: Testing perl modules that rely on remote data
by morgon (Priest) on Aug 02, 2010 at 01:17 UTC | |
Re: Testing perl modules that rely on remote data
by Utilitarian (Vicar) on Aug 01, 2010 at 20:36 UTC | |
Re: Testing perl modules that rely on remote data
by pemungkah (Priest) on Aug 02, 2010 at 21:43 UTC | |
Re: Testing perl modules that rely on remote data
by TGI (Parson) on Aug 06, 2010 at 05:58 UTC | |
Re: Testing perl modules that rely on remote data
by stvn (Monsignor) on Aug 04, 2010 at 16:46 UTC |
Back to
Seekers of Perl Wisdom