Corion fixed the immediate problem, which is good. Here's how I would go about doing your tests. Everything is tested.
use strict;
# no "use warnings" unless I guarantee this is 5.6+.
# CPAN modules may not have that guarantee.
# If Makefile.PL has a check for 5.6, I can add this back in.
use Test::More tests => 6;
my $CLASS = 'Text::xSV';
use_ok( $CLASS );
my $obj;
$obj = $CLASS->new( ... );
isa_ok( $obj );
ok( $obj->set_sep(';'), "Set separator" );
$obj = $CLASS->new( ... );
isa_ok( $obj );
ok( $obj->set_sep(';'), "Set separator" );
ok( $obj->set_filename("popularixCombined.csv"), "Set filename" );
- In general, if you think something isn't in Perl, try it out, because it usually is. :-)
- "What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.