On Tue, Dec 14, 2004 at 03:56:04PM +0200, Yuval Kogman ([EMAIL PROTECTED])
wrote:
> I've started prelimenary work on Test::Harness::Daemon, which is
> supposed to let you make various clients to testing. Some will
> report, others will schedule, some will do both.
Unless it's a sub-part of Test::
Howdy... Sorry for ad hoc reply, i wasn't subscribed to the list
before this.
I've started prelimenary work on Test::Harness::Daemon, which is
supposed to let you make various clients to testing. Some will
report, others will schedule, some will do both.
My plan was to write a client that starts
On Dec 13, 2004, at 11:10 AM, Jason Gessner wrote:
David Cantrell wrote:
Jason Gessner wrote:
Andy Lester wrote:
So it's sort of adding make functionality with prove. The way the
check
is running in the patch, the only criteria for updating it is
changes
in the .t file, but what if what you're u
On 13.Dec.2004 09:49AM -0600, Andy Lester wrote:
> I'm in love with (well, maybe just a crush on) the idea of
> having a continual prove in a window while you're running
> tests. I'm just trying to think of how best to do it.
There is an MIT study on using test-driven development in the
classroo
David Cantrell wrote:
Jason Gessner wrote:
Andy Lester wrote:
So it's sort of adding make functionality with prove. The way the check
is running in the patch, the only criteria for updating it is changes
in the .t file, but what if what you're updating is the source file?
Detecting a change in the
Jason Gessner wrote:
Andy Lester wrote:
So it's sort of adding make functionality with prove. The way the check
is running in the patch, the only criteria for updating it is changes
in the .t file, but what if what you're updating is the source file?
Detecting a change in the mod time for a .t fil
Andy Lester wrote:
On Sun, Dec 12, 2004 at 12:24:26AM -0600, Jason Gessner ([EMAIL PROTECTED])
wrote:
This is not designed as a replacement for a cron'd prove. The way i see
it being used is in a terminal window adjacent to an editing session
while trying to nail down a problem.
So it's sort o
On Sun, Dec 12, 2004 at 12:24:26AM -0600, Jason Gessner ([EMAIL PROTECTED])
wrote:
> This is not designed as a replacement for a cron'd prove. The way i see
> it being used is in a terminal window adjacent to an editing session
> while trying to nail down a problem.
So it's sort of adding make
