On Fri, Apr 02, 2010 at 12:03:13AM -0700, Ovid wrote:
I see no one's answered this yet. I was hoping for more clarification
lest my (mis)understanding hampers things. You have a large data
structure to share across tests and I assume either some code builds it
and others than need it or it's
On Fri, Apr 02, 2010 at 09:26:46AM +0200, nadim khemir wrote:
Same for me. I simply didn't understand what the original mail meant. Not at
all!
Apologies. There were some (dumb) typos that I didn't see when I
re-read the email, and I didn't do a very good job of illustrating what
the problem
So at $WORK we have a bunch of really large data (immutable) data
structures which a ton of our source code uses. As such, most tests
that we write need to access these data structures to run. These
structures can't (currently) be serialized with Storable due to having
LibXML objects in them
On Mon, Nov 09, 2009 at 02:11:23AM -0800, Ovid wrote:
For the life of me, I can't really see any utility to use_ok() or
require_ok(). Not only are both fragile and a source of strange
action at a distance bugs, but the constructs they replace not only
work correctly, but can be viewed as
On Mon, Nov 09, 2009 at 04:32:18PM +, David Cantrell wrote:
Why not test that the script *works*, not just that it compiles?
That's a good idea. Maybe something like run_ok()?
-- Erik
On Tue, Jul 07, 2009 at 10:10:19AM +0200, Steffen Schwigon wrote:
Maybe it's not the latest version you attached, I think it's only the
skeleton from module::starter.
Well, I suppose it's better that I sent the wrong tarball here, rather
than uploading it to CPAN, but it's still embarrassing.
On Tue, Jul 07, 2009 at 01:42:23PM -0700, Michael G Schwern wrote:
At best you have the ability to group statements together into a test, but I
already have that without any intervening pseudo-block to get in the way of
debugging.
Do you not have problems with tests dying? I may be dealing
Greetings!
This email is to announce a new testing framework that I wrote (based
on Test::Builder), which I have tentatively called Test::Functional (as
in functional programming). Before finalizing it and uploading it to
CPAN and I figured I'd email you folks to get your thoughts on the
module
