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

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Wednesday September 22, 2004
03:04 PM

Stupid Test Behavior

[ #21011 ]

Debugging, debugging, debugging. What's going on? I have the filename being passed at $ARGV[0], but I didn't set it. This is annoying, but I can't find what's setting that behavior. OK, let's do this methodically and see when it's getting set. The first two lines of my (xUnit style) test:

sub TEST_DATASET_CONTAINS_THE_CORRECT_FIELDS
{
    use Data::Dumper::Simple;
    warn Dumper(@ARGV);
    ...
}

Which merrily produces:

TEST_DATASET__LOOKS_GOOD ..FAILED!!
-- @ARGV = (
  'SixMonthGrossesByDMAExportRunner.pm'
);

After working here for a year, I only discover today that our in-house test harness thoughtfully and silently alters the contents of @ARGV, but naturally this behavior is not replicated by the code which runs these exports.

Update: A bit of through reveals the reason. We run our test program and pass the name of the class as the argument, but never explicitly clear @ARGV. I think a slight tweak to our test suite is in order.

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.