On 2/13/07, Kirrily Robert <[EMAIL PROTECTED]> wrote:
can someone explain it to me *in a perlish way*.
I think of fixtures as code that helps make testing data driven. I haven't
used Test::Class (though I probably should sometime), but instead, I
refactor my unit tests into the simplest thin
On 13 Feb 2007, at 18:49, Eric Wilhelm wrote:
[snip]
How about, "a thing into which the item under test gets inserted"?
The
c2 wiki (http://c2.com/cgi/wiki?TestFixture) has it as analogous to an
electronics test fixture. They should probably include "light
fixture"
as a very simple metaph
Hiya,
On 13 Feb 2007, at 22:46, Kirrily Robert wrote:
Thanks all, especially Ovid who came closest to answering the actual
question, i.e. can someone explain it to me *in a perlish way*.
Ovid's
example used Test::Class's setup/teardown;
You saying that T::C isn't Perlish? Wanna make somet
--- Thomas Klausner <[EMAIL PROTECTED]> wrote:
> I guess with some more fiddling the END-block could be made smart
> enough
> to only tear down stuff that was actually set up, but it worked for
> me...
If you're using a DB, you can use transactions (AutoCommit => 0) and
rollback at the end.
If
