sults of those
assertions. Printing to STDERR/STDOUT, hijacking those and pretty
printing the
results is simply not enough in all cases. It is awesome in some cases. Just
not all.
sorry for the rant. I have seen an RT request for at least a data structure
returned for results. any movement on that?
-jason gessner
[EMAIL PROTECTED]
st::Harness!!!
-jason gessner
[EMAIL PROTECTED]
the script. I would be interested
in knowing if a cleaner way is possible, as this is kind of lame.
Thanks
Jason.
Hi,
On Wed, 8 Dec 2004 13:37:14 -0500, "Michael G Schwern"
<[EMAIL PROTECTED]> said:
> On Tue, Dec 07, 2004 at 07:21:09PM -0800, Jason Remillard wrote:
> > I ran the codestriker (http://codestriker.sourceforge.net/) test set
> > using Devel::Cover. The test
tests.
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.
Thoughts?
-jason gessner
[EMAIL PROTECTED]
23a24
> my $session = 0;
42a44
> 'session
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
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&#
is skip supposed to be case sensitive? is it Skip, skip or SKIP ?
TODO seems to be all caps.
-jason gessner
[EMAIL PROTECTED]
On Feb 19, 2005, at 8:48 PM, Andy Lester wrote:
The synopsis uses passive voice; <.> is called TAP.
Id turn that around.
TAP, the Test Anything Protoc
anyone done this before i figure out how to do it?
Many Thanks!
-jason gessner
[EMAIL PROTECTED]
or 'received' instead of 'got'.
Andy pointing out tap's use of 'got' makes me think prove should end
like:
1/9 tests ain't right.
Test no good. damn.
:)
-jason
On Oct 1, 2006, at 12:18 AM, Andy Lester wrote:
On Sep 30, 2006, at 4:02 PM, Jo
g the file as 0% covered.
Does anyone have better suggestions?
-Jason Pyeron
#!/usr/bin/perl -w
use Time::HiRes qw(time);
use Data::Dumper;
use File::Find;
use Cwd;
print "load\n";
use Devel::Cover::DB;
my $dbpath="cover_db";
my $db = Devel::Cover::DB->new(db => $
> -Original Message-
> From: Tina Muller
> Sent: Monday, December 26, 2016 07:04
>
> Hi Jason,
>
> On Sun, 25 Dec 2016, Jason Pyeron wrote:
>
> > Coverage works great as part on continuous integration,
> > until a new file is added and the unit t
ogwatch/ci/master/tree/)
-Jason
Title: File Coverage: scripts/logwatch.pl
File Coverage
File:scripts/logwatch.pl
Coverage:48.1%
linestmtbrancondsubpodtimecode
1#!/usr/bin/perl -w
225252525004000use strict;
3##
> -Original Message-
> From: Paul Johnson
> Sent: Tuesday, April 18, 2017 15:29
>
> On Tue, Apr 18, 2017 at 12:32:57PM -0400, Jason Pyeron wrote:
> > I am "require"ing a file but Devel::Cover is not logging
> the statements, only the sub, use, and ev
tart}{-1}{"__COVER__"}[0]{"time"}=undef;
93
$db->{structure}->{f}{$file}{start}{-1}{"__COVER__"}[0]{"statement"}=0;
94 $db->{structure}->{f}{$file}{file}=$file;
95 $db->{structure}->{f}{$file}{digest}=$toadd{$file};
96 $db->{structure}->{f}{$file}{statement}=[1];
97 $db->{runs}{$runKey}{"count"}{$file}{'statement'}=[0];
98 $db->{runs}{$runKey}{"digests"}{$file}=$toadd{$file};
99 }
100
101 $db->{runs}{$runKey}{"finish"}=time;
102
103 print "saving\n";
104
105 $db->write("$dbpath/runs/$runKey");
-Jason
> -Original Message-
> From: James E Keenan
> Sent: Tuesday, April 18, 2017 22:28
>
> On 04/18/2017 07:43 PM, Jason Pyeron wrote:
> > Currently we are using this script to find files (line 48)
> under the scripts directory and add them to the coverage report.
&
> It is currently an (apparent) no-no to add tests to perl that fail.
I seem to recall that Ilya put in a way to add tests that are known to
fail, and whose failures are ignored in normal installation mode, but
I forget offhand how it works.
dedicated. This person whould also have time to put
into implementation of the bug tracking system.
I don't want the job, but probably there are some people here who do.
If there needs to be an election or something like that, I will
volunteer to count the votes.
Mark-Jason Do
I've just found a bug in my module. The bug results in an
inappropriate infinite loop.
Before I fix the bug, I want to write up a test case.
I can reproduce the bug OK, but if I put that code into the module
tests, and the bug isn't fixed, or comes back for some reason, then
the test program w
Michael The Schwern <[EMAIL PROTECTED]> says:
> Use alarm and skip the test if $Config{d_alarm} is false (see
> t/op/alarm.t for an example). If you think the infinite loop is due
> to a programming glitch, as opposed to a cross-platform issue, this
> will be enough.
Thanks very much!
> The on
> I just thought of a clever way to do it without alarm!
So clever, it doesn't work!
> lock_file($foo);
> open(FH, $foo);
> ok( !flock(FH, LOCK_NB | LOCK_EX) );
Seriously, on most unix systems, the following:
flock(FH, LOCK_EX);
flock(FH, LOCK_EX|LOCK_NB) or die;
Supposing that Fcntl and O_RDONLY are known to be available, how
likely is it that O_ACCMODE will also be available? Are there any
platforms that have O_RDONLY but not O_ACCMODE?
> You probably already found out, but
>
> HP-UX 10.20 Has it defined as 003
> HP-UX 11.00 Has it defined as 003
> AIX 4.3.3.0 Has it defined as 3
> AIX 4.2.1.0 Has it defined as 3
Thanks for the information. It turns out some Win32 systems don't
have it at all, so I have to avo
I'm writing automated tests for the example code in my book, which
will go into production early next month. I have the harness and test
apparatus all set up; I wrote a complete set of tests for chapter 6,
and I think I know how I want it done. But I need help writing the
tests themselves, becau
24 matches
Mail list logo
