--- Kirrily Robert [EMAIL PROTECTED] wrote:
Does anyone here understand fixtures as a testing concept, and could
they please explain it to me in a Perlish way?
At least half of what I've heard described is what I usually achieve
with a t/data/ directory, and another half is what I'd do
On Feb 12, 2007, at 10:35 PM, Kirrily Robert wrote:
Does anyone here understand fixtures as a testing concept, and could
they please explain it to me in a Perlish way?
One definition of a fixture comes from the Fitnesse system which is
a framework for collaboration on acceptance testing.
--- Matisse Enzer [EMAIL PROTECTED] wrote:
Typically the programmers provide a Fixture for each category of
testing and the non-programers edit a wiki page to add rows to a
table. Each row in the table on the wiki page is interpreted as a
assertion and when you click the test button the
On Tuesday 13 February 2007 08:24, Ovid wrote:
Really? :)
java.lang.NullPointerException
Oh please, everyone knows Java doesn't have pointers!
-- c
OT - there are a lot of definitions of fixtures. The best I've found
is stuff tests share, which is exactly what Skud said.
On Tue, Feb 13, 2007 at 09:20:29AM -0800, chromatic wrote:
On Tuesday 13 February 2007 08:24, Ovid wrote:
Really? :)
java.lang.NullPointerException
Oh please, everyone knows Java doesn't have pointers!
Of course it does. They may not be accessible to the programmer
due to the design of the
[EMAIL PROTECTED] wrote:
On Tue, Feb 13, 2007 at 09:20:29AM -0800, chromatic wrote:
On Tuesday 13 February 2007 08:24, Ovid wrote:
Really? :)
java.lang.NullPointerException
Oh please, everyone knows Java doesn't have pointers!
Of course it does. They may not be accessible to the
# from Ovid
# on Tuesday 13 February 2007 01:16 am:
--- Kirrily Robert [EMAIL PROTECTED] wrote:
Does anyone here understand fixtures as a testing concept, and
could they please explain it to me in a Perlish way?
At least half of what I've heard described is what I usually achieve
with a
On 2/12/07, Kirrily Robert [EMAIL PROTECTED] wrote:
Does anyone here understand fixtures as a testing concept, and could
they please explain it to me in a Perlish way?
In terms of etymology only, it was explained to me that the term
fixture comes from the idea of testing hardware components.
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; would anyone else be able to
provide confirm that I'm making sense in the following
Test::Harness/Test::More style
Ruby has a nice description at
http://manuals.rubyonrails.com/read/chapter/26
To quote
Fixtures is a fancy word for ‘sample data’. Fixtures allow you to populate
your testing database with predefined data before your tests run.
Think about how something like Test::MockDBI's set_retval_arry()
--- Kirrily Robert [EMAIL PROTECTED] wrote:
2. Assume a directory t/data (or t/fixtures if you will -- I just
call
it data in my own tests).
3. Create a file t/data/foo.yml (or whatever data format) containing
the
data needed by the tests in foo.t
4. At the beginning of foo.t, load
Hi!
On Wed, Feb 14, 2007 at 09:46:19AM +1100, Kirrily Robert wrote:
example used Test::Class's setup/teardown; would anyone else be able
to
provide confirm that I'm making sense in the following
Test::Harness/Test::More style example:
I had to do something similar just yesterday. I wrote a
12 matches
Mail list logo
