Skip Menu |

This queue is for tickets about the Test-MockObject CPAN distribution.

Report information
The Basics
Id: 30811
Status: open
Priority: 0/
Queue: Test-MockObject

People
Owner: Nobody in particular
Requestors: biztos [...] mac.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Strange interaction with Test::MockObject
Date: Sat, 17 Nov 2007 15:33:49 -0800
To: bug-DateTime [...] rt.cpan.org
From: Kevin Frost <biztos [...] mac.com>
Greetings DateTimers! I've stumbled upon a weird interaction between DateTime (0.4.1) and Test::MockObject (1.08). There's a good chance it's actually a bug in Test::MockObject, but since the error points to DateTime I'm sending it your way. Here's a demo: use strict; use warnings; require 5.8.8; use Test::More 0.72 tests => 3; BEGIN { use_ok( 'Test::MockObject', 1.08 ); use_ok('DateTime'); # this works, but not: use_ok( 'DateTime', 0.4.1 ); } ...which gets me this result: 1..3 ok 1 - use Test::MockObject; ok 2 - use DateTime; not ok 3 - use DateTime; # Failed test 'use DateTime;' # at t.pl line 10. # Tried to use 'DateTime'. # Error: "" is not exported by the DateTime module # Can't continue after import errors at (eval 12) line 2 # BEGIN failed--compilation aborted at t.pl line 10. # Looks like you failed 1 test of 3. This is, for me at least, an extremely minor issue, as the things for which I use mock objects are generally not dealing with DateTime directly. But an error's an error and so on. Please pass it on to chromatic if it's a MockObject-only problem. cheers -- frosty
Considering that this problem only manifests if you load Test::MockObject first, I can't see how it could be a problem with DateTime itself. chromatic, do you want to look into this?