On Jul 20, 2006, at 13:38, Adriano Ferreira wrote:
When I made changes, I usually
decreased radically the size of the sample to not be drowned in "not
ok". When everything was alright, I returned to sample sizes of 100 or
so. It would have been easier if I could count with simple expressions
and
On Jul 15, 2006, at 11:35, Ovid wrote:
That was my initial thought, but there's nothing explicitly wrong
with having a numeric skip message.
No, I said make sure that the *second* argument is numeric. It must
always indicate the number of tests to be skipped.
Best,
David
On Jul 15, 2006, at 10:52, Ovid wrote:
That's incorrect, even though saying "skip X tests" reads
naturally to me. Since "skip this many for tis reason" is how I
mentally think of SKIP: blocks, I keep writing them like that, even
though it's wrong. As mentioned, it fails silently.
Perha
On Jul 13, 2006, at 05:56, Fergal Daly wrote:
That's funny, it looks like I did put some code in to disable the END
block if it's "require"d rather than "use"d. Turns out I did this to
make MakeMaker happy, so MakeMaker does actually do a full require,
Well, IIRC, both MakeMaker and Module::Bu
On Jul 12, 2006, at 03:41, Gabor Szabo wrote:
perl -MModule -e'print $Module::VERSION'
I have this alias set up:
function pv () { perl -M$1 -le "print $1->VERSION"; }
I think that calling ->VERSION is more correct.
Best,
David
On Jul 11, 2006, at 09:21, Ovid wrote:
Java programmers typically use jUnit. C programmers have libtap
available. PHP tests often use TAP (don't know the name) and
Javascript has Test.Simple, though it parses the test results
directly and then outputs TAP (if I recall correctly).
It bot
On Jul 10, 2006, at 11:59, chromatic wrote:
It's the grammatical equivalent of tucking your shirt tail into
your underwear
before trying to get a date at your family reunion.
That's the best place to *get* a date!
D
On Jul 10, 2006, at 11:34, chromatic wrote:
"got" still sucks. Is there any chance to change it to "received"?
It's not a gift package delivered by FedEx. What sucks about "got"?
Best,
David
On Jun 29, 2006, at 07:26, Michael Peters wrote:
This is a general problem with the way some of the testing modules
work.
Only because they all use Test::Builder's output methods.
This doesn't resolve the problem of non-test modules emitting
things to STDERR
that could be useful when track
On Jun 28, 2006, at 21:13, Andy Lester wrote:
Any bugs that we especially need to work on?
This might be Test::Builder, but I've seen many times on my Mac where
STDERR and STDOUT output is out of sync. For example, info about why
a test failed can be miles from the line where the "no ok" a
On Apr 19, 2006, at 12:14, Fergal Daly wrote:
One other reason (that I didn't see mentioned) is that objects imply
that the harness and tests are in the same process which means that
the tests can corrupt the harness and that the harness can fail to
report if the test process dies,
Well, the h
On Apr 17, 2006, at 06:03, Andy Lester wrote:
Can you please give me a short couple of sentences on it for
someone who has no idea how/why you'd use TAP outside of Perl?
It's a direct port of Test::Builder, ::Simple, and ::More, along with
a harness for showing test results in a browser. Wh
On Apr 16, 2006, at 20:08, Andy Lester wrote:
I'm adding a section to Test::Harness::TAP on non-Perl TAP.
http://svn.perl.org/modules/Test-Harness/trunk/lib/Test/Harness/
TAP.pod
If you know of one, please send me some text to add.
Test.Simple—JavaScript. It looks and acts just like tap, a
On Mar 5, 2006, at 13:52, Chris Dolan wrote:
Advice? While this example is contrived, the "eval
{ require ... }" idiom is used often in the wild, so this is not a
wholly unrealistic scenario.
Of course it should be
eval { require Bar; 1; } or die $@;
But I agree that it seems like if t
On Mar 4, 2006, at 05:58, Gabor Szabo wrote:
When installing a module ( in this case Sub-Uplevel-0.09 on 5.8.8)
using CPANPLUS I saw many warnings passing by but as all the tests
were successful the report to the CPAN Testers was sent as PASS.
it would be useful to capture warnings printed on t
On Feb 8, 2006, at 12:41, Geoffrey Young wrote:
with your suggestion I'm almost there:
1..1
ok 1 - this was a passing test
# No tests run!
What parts do you want left out?
Best,
David
On Feb 8, 2006, at 11:41, Geoffrey Young wrote:
so, I guess my question is whether the plan->is linkage can be
broken in
Test::Builder/Test::Harness/wherever and still keep the bookkeeping in
tact so that the library behaves the same way for the bulk case. or
maybe at least provide some optio
On Jan 9, 2006, at 2:18 AM, Adrian Howard wrote:
Y'want Test::Builder's failure_output(), e.g.:
use Test::More tests => 1;
binmode Test::More->builder->failure_output, ':utf8';
diag "\x{201c}";
ok 1;
Ah, right, error_output, too.
Thanks!
David
On Jan 8, 2006, at 9:23 PM, Matisse Enzer wrote:
I'm working on getting a large amount of "legacy code" under test
harnesses, and I'm wondering why Test::Unit isn't more widely used.
Andy Lester suggested I pose the question on this list.
Do people think Test::Unit sucks? Simply not very we
Fellow QAers,
This script:
use strict;
BEGIN { binmode STDERR, ':utf8' }
use Test::More tests => 1;
diag "\x{201c}";
ok 1;
Outputs a warning when it runs:
Wide character in print at /usr/local/lib/perl5/5.8.7/Test/
Builder.pm line 1199.
This is annoying. I had thought that I cou
Fellow Testers,
I give you Test.Simple 0.20. This latest version of my port of
Test::Simple and Test::Harness to JavaScript now supports pure .js
test scripts in the browser harness. Details and change log here:
http://www.justatheory.com/computers/programming/javascript/
test_simple-0.2
On Jun 24, 2005, at 11:43 , Adrian Howard wrote:
It probably says something quite sad about my personality that this
is the most persuading argument I personally have now for switching
to Firefox from Safari :-)
Oh, those work in Safari. It's just that Safari doesn't support
file:// in
On Jun 24, 2005, at 01:21 , Tels wrote:
I am a bit confused, does this mean you can run Perl tests from your
browser? Or run javascript tests in javascript, and get the same test
output like in Perl?
The latter.
A short sentence "what does it do and how does it work" would been
very
useful
I’m pleased to announce the first beta release of Test.Simple, the
port of Test::Builder, Test::Simple, Test::More and (drum roll
please!) Test::Harness to JavaScript. Get details here:
http://www.justatheory.com/computers/programming/javascript/
test_simple-0.10.html
See Test.Harness.Br
On May 5, 2005, at 04:26 , Adrian Howard wrote:
Here's a weird idea: how about the option of AJAXing the test
harness results back to a receiving server somewhere that
understands TAP? Bingo: TAP testing of JS embedded in web pages
in its native habitat.
That's just evil. Maybe when Schwern
On May 3, 2005, at 14:27 , Joe McMahon wrote:
Here's a weird idea: how about the option of AJAXing the test
harness results back to a receiving server somewhere that
understands TAP? Bingo: TAP testing of JS embedded in web pages in
its native habitat.
That's just evil. Maybe when Schwern or
On Apr 19, 2005, at 6:07 PM, Adam Kennedy wrote:
Consider the idea of creating a Document that doesn't actually exist
in a window and is thus not seen. (I believe this is possible).
Yes, I think that this is what I'll do for the harness.
Your tests can write out to this document, and the harness c
Hi All,
I've released TestSimple 0.03, the port of
Test::Simple/::More/::Builder to JavaScript. You can find the details
here:
http://www.justatheory.com/computers/programming/javascript/
test_simple-0.03.html
The most significant change in this version is the addition of control
over
FYI
Begin forwarded message:
From: Marshall Roch <[EMAIL PROTECTED]>
Date: April 18, 2005 5:44:26 PM PDT
To: Michael G Schwern <[EMAIL PROTECTED]>
Cc: jesse <[EMAIL PROTECTED]>, David Wheeler <[EMAIL PROTECTED]>, Adam
Kennedy <[EMAIL PROTECTED]>, "Sean M.
On Apr 17, 2005, at 5:05 PM, Michael G Schwern wrote:
http://dynapi.sourceforge.net/dynapi/
Perhaps, But then the mail lists are simply hosted by SourceForge.
Ick.
Sorry, the point was more "drag these guys into this" as they have
obviously
thought about the problem of includes and library paths.
On Apr 18, 2005, at 12:50 PM, Adrian Howard wrote:
Personally I prefer separate version numbers per-module, but some
people don't. I've yet to read anything /really/ convincing for either
side - so I'd do whatever you're comfortable with myself.
I used to do it per-module, but then I kept forge
On Apr 17, 2005, at 3:12 PM, Michael G Schwern wrote:
Perhaps the DynAPI folks might be interested.
http://dynapi.sourceforge.net/dynapi/
Perhaps, But then the mail lists are simply hosted by SourceForge. Ick.
And then there's the whole Ajax thing which I'm not really up on enough
to detect if ther
On Apr 16, 2005, at 3:00 PM, Adam Kennedy wrote:
It's going to totally depend on what you want to wrap around it...
Do you want the human interacty mode? Or the machine county mode.
"machine county mode"? Just that, I think.
Forget the document object for a moment, you are more accurately in
the e
On Apr 16, 2005, at 2:53 PM, Adam Kennedy wrote:
JSPANTS, you mean? I think we need a CJSPAN, first. Alias?
Yes well... I'm getting there slowly.
JavaScript::Librarian + Algorithm::Dependency + YAML ought to be
enough to get some basics sorted out...
Well, you should know that there are a now a nu
On Apr 13, 2005, at 1:27 AM, Clayton, Nik wrote:
Feel free to use (and extend) this set of reference tests. You can see
the tests at:
Thanks, I'll do that. I'll also look at what it would take to simply
port the Test::Simple test scripts directly. :-)
Cheers,
David
On Apr 12, 2005, at 2:07 PM, David Wheeler wrote:
I'm pleased to announce the second alpha release of TestSimple, the
port of Test::Builder, Test::Simple, and Test::More to JavaScript.
And you can download it from here:
http://www.justatheory.com/downloads/TestSimple-0.02.tar.gz
Cheers,
David
I'm pleased to announce the second alpha release of TestSimple, the
port of Test::Builder, Test::Simple, and Test::More to JavaScript. This
release has the following changes:
- Removed eqArray() and eqAssoc() functions from TestMore per
suggestion from Michael Schwern. The problem
On Apr 8, 2005, at 10:28 AM, Michael G Schwern wrote:
Nahh, I'll start slamming now. :) The eq_* salad was a mistake and
I've
been planning on deprecating them for a while now. No sense in
parroting
mistakes forward.
By the way, I've just removed those from my svn repository, and changed
eqSet
On Apr 8, 2005, at 9:36 AM, Geoffrey Young wrote:
as someone familiar with T::M and not javascript, were I to try to use
this
it's an additional barrier to call it "Test::More in JavaScript" but
not
provide _the exact same functions_ as Test::More. now before everyone
starts slamming this let me
On Apr 8, 2005, at 8:23 AM, Adrian Howard wrote:
I did once hack JSUnit to output TAP - so you never know :-)
You are a very sick man. :-)
D
On Apr 7, 2005, at 2:41 PM, Ovid wrote:
It's my understanding that the Ecmascript standard leaves garbage
collection up to the implementation. I suspect this means we can't be
sure exactly when an object is destroyed, though whether or not this
has any bearing on David's problem is not clear to me
On Apr 7, 2005, at 5:55 PM, Michael G Schwern wrote:
If you have isDeeply() there's little point to the eq* salad.
Hrm, fair enough. I'll comment them out, then...
Cheers,
David
On Apr 7, 2005, at 1:40 PM, Michael G Schwern wrote:
Zee goggles, zey do nothing!!!
I thought I eliminated the radiation...
Not so different, that's what I would have done were it not for the
fact
that it alters caller(). If Javascript has no such problems then do
it,
but I suspect it does.
I ha
On Apr 7, 2005, at 12:46 PM, Ovid wrote:
Great work!
Thanks.
Output them to a Results object which, by default, sends the output to
document.write() but allows the user to redirect the output. For
example, it might be nice to have test results pop up in a separate
window while the main page loads.
On Apr 7, 2005, at 12:19 PM, Fergal Daly wrote:
Were you aware of JsUnit?
http://www.edwardh.com/jsunit/
Yes, it's in the "See Also" section of my docs.
I prefer the Test::More style of testing most of the time. I count
myself
lucky I've never had to use a testing framework for javascript!
I guess
On Apr 7, 2005, at 11:32 AM, Christopher H. Laco wrote:
OK, now whos gonna build JPANTS? :-)
JSPANTS, you mean? I think we need a CJSPAN, first. Alias?
Cheers,
David
On Apr 7, 2005, at 11:28 AM, Andy Lester wrote:
You are a crazy man.
Best feedback I ever had. Brilliant!
D
Greetings fellow Perlers,
I'm pleased to announce the first alpha release of my port of
TestSimple/More/Builder to JavaScript. You can download it from:
http://www.justatheory.com/downloads/TestBuilder-0.01.tar.gz
Please feel free to give it a try and let me know what you think. You
can see
On Mar 28, 2005, at 4:21 PM, Randy W. Sims wrote:
I think someone had proposed a year or two ago that there should be a
test_requires options and I argued against it. Now, I think maybe it
was a good idea; especially, since the number of extra testing modules
being used have increased a lot over
On Mar 21, 2005, at 1:32 PM, Christopher H. Laco wrote:
When you say test JavaScript, what kinds of files are we testing?
Server side web scripting using JavaScript?
Shell scripts files?
And JS that runs in a browser, yes.
Regards,
David
Hi All,
Is anyone aware of an implementation of Test::Builder/Simple/More and
Test::Harness in JavaScript? The testing scene in JS appears pretty
sad, but I don't want to do much in JavaScript without a nice testing
framework. And Test::More would be my preferred way to go. (Yes, I know
that th
On Feb 24, 2005, at 2:19 PM, Michael G Schwern wrote:
Is this associated with the recent versions of TH that attempt to
capture
STDERR?
No, all my patch did was turn off buffering in the same way that
Test::Builder does.
Regards,
David
On Feb 23, 2005, at 6:42 PM, chromatic wrote:
The way Test::Builder works, diagnostics always go to STDERR. Is there
a reason for this beyond "It's tricky to correlate diagnostics to the
appropriate test numbers"? (I agree with that, but I'm willing to take
my chances on certain occasions.)
Perso
On Feb 14, 2005, at 9:01 PM, chromatic wrote:
Here's my list of suggestions for each:
1) label, description
2) directive, instruction
3) diagnostic
I want to avoid the word "comment" altogether, making the optionalness
of #1 and #3 evident in their words, the activeness of #2 evident in
its
word,
On Dec 20, 2004, at 6:44 PM, David Wheeler wrote:
PS Somebody should drag autrijus into this.
I'll try to grab him on IRC in the morning...
I got him this morning. Here's the discussion:
09:50am] Theory: seen autrijus
[09:50am] purl: autrijus was last seen on #p5p 1 hour and 32 mi
On Dec 20, 2004, at 6:41 PM, Michael G Schwern wrote:
PS Somebody should drag autrijus into this.
I'll try to grab him on IRC in the morning...
Regards,
David
On Dec 20, 2004, at 6:19 PM, Michael G Schwern wrote:
Is there a module or function in Perl that can provide this
information?
Why does it matter what it was set to before? I'm always going to be
shoving text out through this filehandle.
It matters because if I'm using Big5 in my module, I *don't
On Dec 20, 2004, at 6:13 PM, David Wheeler wrote:
If there was a way to tell what mode was on STDERR before you duped
it, you could just set it to the same. Something like:
my $mode = what_binmode(STDERR);
my $fh = $builder->failure_output;
binmode $fh, $mode;
Is there a module or funct
On Dec 20, 2004, at 6:06 PM, Michael G Schwern wrote:
use Test::Builder;
BEGIN {my $fh = Test::Builder->new->failure_output; binmode $fh,
':utf8';}
Test::Builder should do something like this internally, its not like
anyone's
going to drive binary data through a TB filehandle. The question
On Dec 9, 2004, at 1:48 PM, Rafael Garcia-Suarez wrote:
It's probably better adapted to text pages.
I wrote Test::LongString to debug and test a
serialization/deserialization protocol that was
producing long binary strings. For this purpose,
it was most helpful :)
Ah, yeah. Test::Differences is lin
On Dec 9, 2004, at 7:22 AM, Andy Lester wrote:
Test::LongString is one of those modules that you should be using if
you're doing testing against large data elements, especially web pages.
There are now examples in the docs that I hope make you say "Wow, this
is cool, thanks RGS!"
I use Text::Differ
On Nov 26, 2004, at 12:13 AM, Michael G Schwern wrote:
This means Test::More has no more critical or important bugs open.
I figured it was a good place to pause and kick out an alpha.
Works for me, although I did get some warnings:
Running [/usr/bin/make UNINST=1 uninst=1 test]...
PERL_DL_NONLAZY=1
On Oct 5, 2004, at 12:53 PM, Geoffrey Young wrote:
yeah, I think that's all the required up front pieces. authors still
need
to configure Devel::Cover over in httpd.conf land, but there's not
much we
can do from a makefile to help with that.
I think we're good to go, then.
Regards,
David
On Oct 5, 2004, at 12:43 PM, Geoffrey Young wrote:
no, it is required. but only cvs currently supports -one-process as an
option - earlier versions will explode.
Okay. So I just added this to the testcover action:
local $ENV{APACHE_TEST_EXTRA_ARGS} = "-one-process";
Is that all it needs?
Regar
On Oct 5, 2004, at 12:36 PM, Geoffrey Young wrote:
somewhere in here it looks like -one-process is missing, though I
wouldn't
know where it would go.
I'll put it in, though it isn't needed if you use A-T in CVS, eh?
you're the only one with commit access who uses or understand
Module::Build,
so g
On Oct 5, 2004, at 11:51 AM, Geoffrey Young wrote:
basically it goes into $HOME because it stores the A-T preferences for
a
specific user. but this is all part of the endless 'sticky
preferences' foo
that I really don't want to be associated with ;) lots of to and fro
in the
httpd-test archive
On Oct 5, 2004, at 11:51 AM, Geoffrey Young wrote:
basically it goes into $HOME because it stores the A-T preferences for
a
specific user. but this is all part of the endless 'sticky
preferences' foo
that I really don't want to be associated with ;) lots of to and fro
in the
httpd-test archive
On Oct 5, 2004, at 11:32 AM, Geoffrey Young wrote:
Ah, cool. But $(HOME) doesn't correspond to ~/ here, does it?
yeah - it's equivalent to $ENV{HOME} in make-land. I guess there is
always
the danger that $HOME isn't populated, but internally A-T uses
$ENV{HOME}
when it generates the .apache-test
On Oct 5, 2004, at 11:25 AM, Paul Johnson wrote:
I wonder whether we shouldn't try to standardise the target name before
it's too late to do so. Module::Build uses covertest, I've always used
cover, and Geoff has just used test-cover.
Actually, Module::Build uses "testcover".
I'm not overly concer
On Oct 5, 2004, at 11:08 AM, Geoffrey Young wrote:
I think that all Apache::TestMB would need to do is add a make target
that
looks like this:
test-cover ::
@cover -delete
@HARNESS_PERL_SWITCHES=-MDevel::Cover=+inc,$(HOME)/.apache-test
APACHE_TEST_EXTRA_ARGS=-one-process $(MAKE) t
On Oct 2, 2004, at 2:30 PM, Geoffrey Young wrote:
I started to maintain Apache-Test skeletons, but I never quite got
them up
to speed. give me a few days and I'll roll a tarball with a test-cover
target so that folks can have an entire working example of the way I
would
do it.
Perhaps I should a
Hi Paul et al.,
In an iterator class I've written, I have this method:
sub do {
my ($self, $code) = @_;
while (local $_ = $self->next) {
return unless $code->($_);
}
}
I've written tests for when the code reference returns true and when it
returns false. However, Devel::Cover
On Sep 17, 2004, at 7:48 AM, Ricardo SIGNES wrote:
Presumably the problem is that by runtime, lib and blib directories are
already in @INC, so the things in your ./distro/lib/ won't be covered,
defeating the point.
Ah, good point.
As to whether there is a simple way to resolve this, I haven't thoug
Hi Paul (and everyone else),
The Devel::Cover documentation says:
The inc directories are initially populated with the contects
of the
@INC array at the time Devel::Cover was built. You may reset
these
directories using -inc, or add to them using +inc.
However, now that new
Finally replying to this; sorry for the delay.
On Jun 17, 2004, at 12:50 PM, Paul Johnson wrote:
On Thu, Jun 17, 2004 at 09:31:48AM -0700, David Wheeler wrote:
I checked in a bunch of changes to my module last night, and then the
nightly process that runs cover on it output these lines:
Devel
On Jul 19, 2004, at 8:09 AM, Michael G Schwern wrote:
The exit code information adds unnecessary extra information to an
already
crowded set of diagnostics. Observe the difference.
Oh, yeah, it's nice that you lose the extra two lines that I, for one,
never paid attention to, anyway.
Regards,
D
On Jul 11, 2004, at 11:09 AM, Michael G Schwern wrote:
I document private code like this:
=begin private
put your normal POD here
=end private
perldoc won't show the POD but someone reading through the code (and
thus
needing to know about private functions) will see it. And POD is very
readable i
On Jul 10, 2004, at 12:35 PM, Robert Rothenberg wrote:
The reason is that I would like to integreate this with testing
information from the CPAN Testers. So if I find that there are no
testing results for platform 'x' for a specific module, I can check to
see if one of the dependent modules fai
Hi All,
I checked in a bunch of changes to my module last night, and then the
nightly process that runs cover on it output these lines:
Devel::Cover: ignoring extra subroutine
Devel::Cover: ignoring extra statement
Devel::Cover: ignoring extra statement
Devel::Cover: ignoring extra subroutine
Dev
On May 24, 2004, at 4:02 AM, Tim Bunce wrote:
Any idea when the next release of Test::More will be available?
We could use a new version of Test::Harness, too, given this bug:
https://rt.cpan.org/NoAuth/Bug.html?id=5649
It bit me again yesterday. I first noticed it with DBI.
Regards,
David
On Mar 1, 2004, at 9:12 AM, Philippe 'BooK' Bruhat wrote:
Which means the server and client could communicate as IRC bots,
with Net::IRC or a similar module?
Jabber.
David
On Feb 23, 2004, at 6:40 AM, Thomas Klausner wrote:
Is there a way to abort a whole testsuite?
I use control-c.
David
On Feb 6, 2004, at 9:25 AM, Mark Stosberg wrote:
How are other people integrating HTML validation into their work flow?
I want a solution that's easy so it actually gets used. :)
I use XML::LibXML to validate against a DTD:
$parser = XML::LibXML->new;
$parser->validation(1);
$parser->
this one when I need to see
what tests have passed (I've avoided looking in the past because of the
poor performance).
Nice one, Leon.
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
nks All!
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Kineticode. Setting knowledge in motion.[sm]
eeds. I think that this issue can be
circumvented by requiring a string to be returned from a method when
you want to skip the remainder of the tests. A silent return would fail.
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED]
ronment variable to print out
> the name
> of each test before it's run.
Ah, and that's a little different, since here it *is* an environment
variable. Interesting.
Thanks,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED]
NV{TEST_VERBOSE} ? 1 : 0;
But what am I missing? I know that a lot of people on the cpan-testers
list ask for tests to be re-run with TEST_VERBOSE=1, but I can't see
that it actually makes much difference. Should it?
Thanks,
David
--
David Wheeler
aste much in the way of resources once they'
ve been installed, I personally think it's no big deal to install them.
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/
89 matches
Mail list logo
