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
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
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
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
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
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
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
Hi All.
I was impressed recently with py.test, a new-ish testing tool in the
python world and wanted to snag one of their features for prove.
This patch adds a --session flag to prove that will make prove
continually run and re-run any modified tests. Ideally, it would also
re-run failed
