Leaon, since you'll be at the QAH, maybe we can work a bit on Test::Exception.
I won't be physically present though.
Nadim.
> On Sun, Apr 10, 2011 at 5:26 PM, Ricardo Signes
>
> wrote:
> > The QA hackathon wiki suggests that directions to the hotels can be found
> > at http://2011.qa-hackathon
> I see no one's answered this yet. I was hoping for more clarification lest
my (mis)understanding hampers things. You have a large data structure to
share across tests and I assume either some code builds it and others than
need it or it's expensive to build? If it's the former, it implies an
On Sunday 15 February 2009 17.49.43 Ovid wrote:
> If you're struggling to understand a complex app, a graph of the
> inheritance hierarchy can be very useful. Here's an example for
> TAP::Parser:
>
> http://i82.photobucket.com/albums/j275/publius_ovidius/Geek%20Stuff/graph-5
>.png
> ...
>
Nice,
On Wednesday 11 February 2009 11.58.02 Steffen Schwigon wrote:
> Hi!
>
> [TAP Namespace Nonproliferation Treaty]
>
> Should I name a module that represents the result of a TAP parse as
> data structure
>
> TAP::Data
>
> or
>
> TAPx::Data
>
> before I upload to CPAN?
>
> T
Hi,
I was discussing one of my modules with a friend and he asked how many tests I
had. I answered 500 hundred but it then hit me that to have the module
working I had to rely on other modules written by other people.
The actual number of tests being the sum of all the tests for the module
dep
On Friday 08 August 2008 11.05.53 Gabor Szabo wrote:
> I am not sure if this is related to the recent ascii-art discussion
There was an ascii art discussion? where?
Cheers
Hi, sorry I didn't reply earlier but I deserved some sunny vacations;
On Friday 18 July 2008 10.29.10 Gabor Szabo wrote:
> I am about to book my flight to Copenhagen but I have to decide when
> to come back
> so I was wondering what's going on with the Hackathon?
>
> Is it going to take place?
Yes
On Saturday 07 June 2008 19.36.21 Gabor Szabo wrote:
> I just got a failure report from David Golden as this line
> did not work with "Permission denied"
>
> copy($0, "$0.tmp")
>
> He was running it on Windows (Strawberry Perl).
>
> I am sure I create temporary files in various test, so it might b
On Thursday 22 May 2008 12.56.02 brian d foy wrote:
> I've managed to edit the video from the closing remarks at the Oslo QA
> Hackathon.
>
> http://vimeo.com/1043143
>
> It's nothing fancy, but it's the first video I've made and next time it
> will be better :)
Nice. Now we all have to do that at
On Monday 12 May 2008 20.41.58 Bram wrote:
> > Leave your todo test as it was to start with.
> > Create a new test file "development_values_that_shoulnot_change.t" in
> > your developer test directory (that's not just for pod right).
> Which is not practical at all.
> That means maintaining an ext
On Monday 12 May 2008 16.23.46 Bram wrote:
> Then what happens if it starts returning 4?
> Then the test script will report a FAIL, and users will/might start
> ignoring failures.
> Which is a bad thing (IMHO).
>
> The todo test indicates that something doesn't behave as it should.
> If it suddenly
Thank you for explaining the thoughts behind $trap.
Cheers, Nadim.
On Tuesday 06 May 2008 13.21.17 Andy Armstrong wrote:
> I'm in :)
Of course this is first come - first served
> Once we know numbers and have a better idea of who's attending I'll
> volunteer for some duty or other.
What are you good at?
> As long as I don't have to clean the
> latrines...
Not
In Oslo I proposed to organize a hackathon the week after YAPC::EU.
Subject:
-QA
- tool: IDE, editors, _debugger_, CPAN::Mini::xxx
(I believe most toolchain ppl are on the QA list)
- your_idea_here
I'd like to make it possible to have this one "on a shoestrin
On Friday 02 May 2008 01.24.00 Eirik Berg Hanssen wrote:
> use Test::More tests => 1;
> use Test::Trap;
> trap { warn "1\n2\n3" };
> $trap->warn_like(0, qr/1\n2\n3/);
Ah! I like this. How did I miss this module??
is it possible to have trap{} return an object/sub/whatever that is created by
the
On Thursday 01 May 2008 20.06.52 Eirik Berg Hanssen wrote:
> What precisely must "something()" be? I tried the following:
> So. Where do I look?
Here is the (simplified) code that would generate the warning I thought was a
problem (read below)
my ($search_regex, $replacement_regex) = (qr/
On Tuesday 29 April 2008 19.52.08 Aristotle Pagaltzis wrote:
> If the warning is normal, how about disabling it? If a warning
> does not signify a problem, there is absolutely no point in
> having perl emit one anyway.
It's a perl warning (in an eval) not something I output.
Cheers, Nadim.
On Tuesday 29 April 2008 03.24.48 Michael G Schwern wrote:
> > BTW: Test::Warn suck a bit because it doesn't check the warning you emit
> > but the _first_ line of the warning you emit (hmm, time for a patch
> > maybe).
>
> All the warnings_* functions take an array ref of warnings.
You can't test
Hi,
I have had a problems with output when running tests, this happends, IE, when
perl output a warning.
warning_like
{
something() ;
} qr'Use of uninitialized value in substitution iterator' ;
I get the warning on the terminal which is boring when one works with a mod
On Friday 18 April 2008 20.06.32 Michael G Schwern wrote:
> I'd like to know if anyone has a way to make Devel::Cover work properly
> with the MakeMaker tests. Currently I get bizarre results from cover -test
> (see below) where it thinks there's no lines in the modules. This is
> probably the re
On Saturday 05 January 2008 20.21.59 Eric Wilhelm wrote:
> Even if it weren't a system handle, in what situation does print()
> return false?
>
> 1. Closed handle
> 2. Unopened handle
> 3. Disk full
>
> Unless I've missed one, you don't need to check the return value of
> print.
>
> I will
On Saturday 05 January 2008 15.08.55 Michael G Schwern wrote:
> nadim khemir wrote:
> > print 'hi' or carp q{can't print!} ;
>
> I'm not even going to wade into the layers of neurosis demonstrated in this
> post, but if you want to throw an error use croak
With the advent of intensive coverage tests and zealous Perl::Critic policies,
testing even simple things is getting messy.
even a moundain:
print 'hello' ;
triggers the wrath of InputOutput::RequireCheckedSyscalls with the
message "Return value of flagged function ignored".
This is
On Thursday 03 January 2008 19.42.26 nadim khemir wrote:
> I did send a mail to cabie author asking if he had made a comparison
> between cabie and other systems. I also invited him to join us on this
> mailing list. I'll forward his answer if he does answer me.
I received an an
On Thursday 03 January 2008 11.50.03 Andy Armstrong wrote:
> > Cabie seems to be as good, if not better (psst, it's written in Perl).
> Does that make it better? :)
RTFM! In the feature list the authors writes "* It's really cool!". Since cool
is better than good, I assume it is ;)
The "written
On Saturday 29 December 2007 10.11.41 Matisse Enzer wrote:
> I've spent some of this holiday season learning how to set up BuildBot
> ...
I've also found this one to be written in Perl:
http://www.johnkeiser.com/mozilla/tbox3.html
other links
http://en.wikipedia.org/wiki/Continuous_Integration
On Saturday 29 December 2007 10.11.41 Matisse Enzer wrote:
> I've spent some of this holiday season learning how to set up BuildBot
> ...
Cabie seems to be as good, if not better (psst, it's written in Perl).
http://cabie.tigris.org/
Cheers, Nadim.
On Sunday 16 December 2007 23.29.55 Michael G Schwern wrote:
> nadim khemir wrote:
> > On Saturday 15 December 2007 20.53.30 Michael Peters wrote:
> >> The uploaded file
> >>
> >> TAP-Harness-Archive-0.03.tar.gz
> >> ...
> >
> > Nice.
On Saturday 15 December 2007 20.53.30 Michael Peters wrote:
> The uploaded file
>
> TAP-Harness-Archive-0.03.tar.gz
> ...
Nice. Now, what do we do with it?
Cheers, Nadim.
Edwardson, Tony wrote:
> Anyone written any CPAN modules for which the testing coverage needs to
> be improved ?
Euuu, All of them.
Nadim.
FYI: http://socialtext.useperl.at/woc/index.cgi?todo_test_bounties
On Sunday 02 December 2007 18:48, Chris Dolan wrote:
> ...
>
> In this fashion, we use TODO tests to track when bugs in our
> dependent packages get fixed, and then when we can remove workarounds
> therefore.
>
> Chris
This discussion is interresting and it's always educating to understand why
o
On Sunday 02 December 2007 18:51, Eric Wilhelm wrote:
> # from Ovid
>
> # on Sunday 02 December 2007 07:47:
> >--- nadim khemir <[EMAIL PROTECTED]> wrote:
> >> The subject says it all. IE:
>
> ...
>
> >> t/20_policies.t 152 578 5
On Sunday 02 December 2007 16:47, Ovid wrote:
> --- nadim khemir <[EMAIL PROTECTED]> wrote:
> > The subject says it all. IE:
> >
> > All tests successful (2 subtests UNEXPECTEDLY SUCCEEDED), 7 tests
> > skipped.
> > Passed TODO
The subject says it all. IE:
All tests successful (2 subtests UNEXPECTEDLY SUCCEEDED), 7 tests skipped.
Passed TODO Stat Wstat TODOs Pass List of Passed
---
t/20_policies.t 152 578 583
(nice report
On Sunday 25 November 2007 20:47, Chris Dolan wrote:
> I've been working on Test::Virtual::Filesystem for a couple of
> weeks.
> ...
> filesystems (like Fuse filesystems -- I use it for Fuse::PDF)
> ...
> Thoughts?
Fuse::PDF caught my eyes a few days ago (how could it not with that name ;)
alth
Hi, This mail is not discussing what quality and what test quality is. It is
about what quality our 'test files' have.
I run Test::Fixme, Kwalitee, perl::Critic, etc ... on my modules but none of
them is ran on my tests. tests have a tendency to become a mess, be
undocumented, etc...
What are
Hi,
I spend a rather large amount of time writing and running tests. There are a
few things that could be better. I either don't know how or it may not
possible. I thought we could share some of questions and ideas that can make
working with tests more pleasent. This should go into a Q&A I gue
On Monday 29 October 2007 02:06, Chris Dolan wrote:
> On Oct 28, 2007, at 6:12 PM, Scott McWhirter wrote:
> > You could use an IO::Handle based object wrapped around STDOUT/STDERR.
>
> It doesn't really matter whether it's a glob filehandle or an
> IO::Handle or a tied handle. The important part i
On Tuesday 19 June 2007 17:52, Mike Malony wrote:
> So I'm working my project, and I've got one other more junior coder with
> me.
>
> Has anyone tried writing test files as part of their spec's?
>
> An overview document would also be needed, and some time walking through
> the expected testing. B
On Wednesday 01 August 2007 22:10, Andrew Ford wrote:
> I have corresponded with Ian Langworth and he has agreed that I should
> revise the Perl Testing quick reference. I shall be converting it to
> LaTeX and expanding it to be a two-sided card, which implies doubling
> the amount of information
On Friday 08 June 2007 00:04, Matisse Enzer wrote:
> I wonder how you all feel these days about the "put the pod at
> the __END__" approach? I've been trying it for over a year now
> and am not really sure its the best way to go (vs. having the pod
> for each method right next to it.)
I put the P
On Thursday 07 June 2007 12:54, David Cantrell wrote:
> Nadim Khemir wrote:
> > 'method docs have examples': I believe the examples should be tested.
>
> I have to disagree.
And that would be your priviledge. If you have code in you POD and that code
is not tested t
On Wednesday 06 June 2007 17:08, Ian Malpass wrote:
> I've been documenting lately, so I'm a bit POD-focussed at the moment :)
> I was pondering creating Pod::Critic, as a documentation analogue of
> Perl::Critic.
>
> Clearly it's not so easy to give hard-and-fast rules about
> documentation, but I
How do you plan to test things like:
my $url_base = "http://search.cpan.org/"; ;
for my $rest (qw(modlist/Graphics modlist/Database_Interfaces))
{
do_anything_with($ur_base . $rest);
}
Nadim.
On Sunday 03 June 2007 15:10, Ian Malpass wrote:
> ReneeB wrote:
> > Let this t
Can we get examples? first the POD then what you would like to extract.
Best would be to write your examples as tests.
Nadim.
On Saturday 02 June 2007 12:11, ReneeB wrote:
> Ian Malpass wrote:
> > I've started crafting Test::Pod::URI to extract URIs from POD and
> > check them to make sure they
Hi, I just uploaded POD-Tested to CPAN (It may take a few hours before it is
accessible). it's a fun little module to write cookbooks. It lets you test
the content of you cookbook and generate some sections dynamically.
There are a few schoolbook examples in the distribution but
Config-Hierarch
PAR has a module to find module dependencies. That might help.
Nadim.
On Sunday 04 March 2007 09:40, Shlomi Fish wrote:
> My solution to this is:
>...
> What I do is add comments in a small domain-specific language ...
>...
> # TEST
> is ($mystring, "Hello", "String is Hello");
>
> # TEST*3
> for my $i (0 .. 2)
> {
> ok ()
> }
>
Wouldn't Test::Block be bet
On Saturday 03 February 2007 09:04, chromatic wrote:
> > Can I use TAP for this? Can TAP be used to represent such hierarchy?
> Filesystem directories already represent a hierarchy.
Using the tagging scheme is bound to fail if you modify you test hierarchy
(well, you can always modify your tags
On Saturday 03 February 2007 07:48, Adam Kennedy wrote:
> And from all of us, I think a big Thank You and congratulations are in
> order.
Indeed, Jeffrey's work is of the highest value to the perl community.
It would be interresting to know how many ppl and new modules use
Perl::Critic. In any c
On Friday 02 February 2007 10:09, Adrian Howard wrote:
> [snip]
> I'm unconvinced that this should be the default behaviour because I'm
> fairly certain that a number of these new test failures - possibly
> the majority - won't actually be indications of code that doesn't work.
>
> For example. Mod
On Thursday 01 February 2007 22:37, Joshua ben Jore wrote:
> I'd be a happy guy if a paranoid T::E caused consternation and people
> to post "OMG! My stuff fails now!" to perlmonks or whatever.
I use T::E extensively and I, too, would like to see a complete paranoid
module.
Someone wrote, "don'
On Tuesday 30 January 2007 19:09, A. Pagaltzis wrote:
> * Nadim Khemir <[EMAIL PROTECTED]> [2007-01-30 18:20]:
> > # Check that a test runs without an exception
> > lives_and { is $foo->method, 42 } 'method is 42';
> > Isn't this equivalent to i
On Tuesday 30 January 2007 18:53, Pete Krawczyk wrote:
> snip
> No, you're not - but shunning all possible uses of dies_ok becasue you
> didn't write a test as complete as you could have isn't the fault of
> Test::Exception.
> How about code that dies with an object? dies_ok lets you inspect the
On Tuesday 30 January 2007 19:19, A. Pagaltzis wrote:
> * Pete Krawczyk <[EMAIL PROTECTED]> [2007-01-30 19:00]:
> > How about code that dies with an object? dies_ok lets you
> > inspect the object in $@, whereas throws_ok only lets you see
> > if it's part of a class. What if you want to see if $@
I like Test::Exception, it's a very fundamental test module with
Text::NoWarning, Test::Deep and other goodies. Still, I believe some of the
functions made available should not be there at all.
The good guys :
# Check that the stringified exception matches given regex
throws_ok { $foo->me
A, slightly, better way to handle diagnostics?
http://search.cpan.org/~nkh/Carp-Diagnostics-0.02/
Cheers, Nadim.
On Wednesday 17 January 2007 14:57, Christopher H. Laco wrote:
> Christopher H. Laco wrote:
> > While strolling through PlanetMVC, I noticed a free chapter about unit
> > testing using it's own testing library call Lime. Low and behold, my
> > eyes see TAP and some props to Test::More. Kewl. :-)
>
Hi,
On Friday 12 January 2007 01:49, [EMAIL PROTECTED] wrote:
> You don’t have to use objects to get the same end effects as mocking
> objects.
Right!
Now, as my "devil's advocate" signature tried to show, this thread is for the
fun of the discussion. I'm sure all of use, and Ovid more than th
On Thursday 11 January 2007 18:04, Ovid wrote:
>> Just one, Shouldn't the mailer "object" be mocked and the mail
>> sending checked?
>absolutely, but how do you know to mock it or really send the email
>unless you know that you're being run by tests?
Aren't you mixin contexts here? The code to be
On Thursday 11 January 2007 15:30, Ovid wrote:
> Quite often people will write code which tests to see if
> $ENV{HARNESS_ACTIVE} is true. For example, this allows them to not
> email support from their code while testing. This variable is set in
> Test::Harness. However, this causes a problem wh
Hi all,
PBP p. 134 and 286 advocates the use of a "=head1 DIAGNOSTICS" section.
Although this is a bit on the heavy side, I would tend to agree. I'm not sure
it would help a lot of users but it makes one feel good (which is why we
write module. Right?).
my latest modules confess at 30 differen
Hi Josh,
> Not true. If you real perldebguts you'll see that the debugger can be
> scripted or you could write your own debugger.
right and right but Devel::Ebug is simply much cleaner and I'd rather not mock
a debugger when I can use a real one.
Hi Adrian,
>> The first problem I have is captu
Hi,
I'm writing a module to help debug application. I have used it in PBS for a
while and I wanted to rewrite it "right" with tests and all.
= 1 =
The first problem I have is capturing the module output when it is loaded.
I tried:
my $capture ;
BEGIN
{
$capture = IO::Capture::Stdout->
65 matches
Mail list logo
