Re: Testers & PASS

On 2003-07-19, Leon Brocard <[EMAIL PROTECTED]> wrote: > Hello, > > I've been looking at the testers database (well, downloading the list > via nntp.perl.org really) for Module::CPANTS recently. > > In the current version of Module::CPANTS I report the count of PASSes > and FAILs for each distribut

Phalanx & Devel::Cover

I'm excited to see that the Phalanx project is happening. On the website I see this unfiled item: "Use Devel::Cover and gconv". One way that seems useful to use Devel::Cover is to have an automated coverage testing system that would test the 100 module periodically. All the phalanx page, an ex

Recommendations for testing e-mail output

est script output could remind me to read...or perhaps even open for me. - ?? I'm curious to know what others are doing to address this that they have been satisfied with. Thanks! Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrinci

thinking about variable context for like()

I have a suggestion for "Test::More" that is especially useful with WWW::Mechanize. I'm frequently using 'like' to test $agent->content against a regular expression. When I have a lot of these in a new test script and they are all failing, I get a boatload of HTML source floating by, which ma

thinking about Test::HTML::Form

ains at least these fields Additionally, I could see shortcuts for randomly or methodically selecting possible value combinations from selection lists, possibly with a focus on testing the edge cases, such as the first and last items in the group. Mark -- . . . . . . . . . . . . . . . .

recommendation for website HTML validation tool?

ating HTML validation into their work flow? I want a solution that's easy so it actually gets used. :) Thanks! Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL PROTECTED] Summersault, LLC

Re: recommendation for website HTML validation tool?

valid HTML # originally by Mark Stosberg on 02/05/04 # based on code by Andy Lester use Test::More; use strict; use XML::LibXML; use File::Spec; use File::Find::Rule; my $startpath = $ARGV[0] || die "usage: $0 path/to/www"; my $rule = File::Find::Rule->new; $rule->or( $rule->n

RFC: Test::XML::Valid

nd to accept lots of different inputs besides file path names. In a test today, it validated 15 XHTML files in about 1 second. Thanks! Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL PROTECTED]

testing a shell command which prompts for output?

How can I write an automate test for a shell command that prompts for output. I first tried just using backticks, but that hangs waiting for input. Thanks, Mark -- http://mark.stosberg.com/

Re: testing a shell command which prompts for output?

On 2004-10-17, Andy Lester <[EMAIL PROTECTED]> wrote: > > On Oct 16, 2004, at 8:02 PM, Mark Stosberg wrote: > >> How can I write an automate test for a shell command that prompts for >> output. I first tried just using backticks, but that hangs waiting for >> input

Quality from the Beginning: Better Estimates

ld", the good the bad and ugly. Thanks! Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . .

Re: Quality from the Beginning: Better Estimates

speeds up a lot of boring re-testing. In part, I haven't been using automated testing as long as I've been programming, so I simply don't have as much experience to pull from when estimating it as a factor. Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark S

Re: Quality from the Beginning: Better Estimates

On 2004-11-01, chromatic <[EMAIL PROTECTED]> wrote: > On Mon, 2004-11-01 at 07:45, Mark Stosberg wrote: > >> So, what resources are recommended to consult to make great estimates? >> What habits to develop? > > I have two primary rules: > > 1) Don't make

Re: dor and backwards compat (was Re: [ANNOUNCE] Test::Simple 0.49)

uot;foo" } print err' > Ambiguous call resolved as CORE::err(), qualify as such or use & at -e line 1. > syntax error at -e line 1, at EOF > Execution of -e aborted due to compilation errors. This seems like an important difference. It would be nice if my 'err'

Re: Quality from the Beginning: Better Estimates

sk factors" 4. Reward good estimates. :) Comments? Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . .

estimating other people's work (was Re: Quality from the Beginning: Better Estimates)

for programming work that I didn't contribute to myself. Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . .

Re: Differences between output of 'make test' and 'prove'

On 2004-11-05, Jeff Bisbee <[EMAIL PROTECTED]> wrote: > > I remember mentioning something to Andy, but at the time he didn't like > it. I'm also curious how other folks run coverage, update modules > and rerun coverage. Using Module::Build, it's easy to run coverage: ./Build testcover [test opt

Re: Phalanx update

On 2004-12-02, Andy Lester <[EMAIL PROTECTED]> wrote: > I've reorganized all the trees in http://svn.perl.org/phalanx. A > description of how things should be is at > http://svn.perl.org/phalanx/structure.pod. I think I missed something. This clearly has something to do with SVN hosting and the P

Re: Test labels

> On Mon, Dec 06, 2004 at 10:28:45PM -0600, Andy Lester wrote: > I think even better than > > ok( $expr, "name" ); > > or > > ok( $expr, "comment" ); > > is > > ok( $expr, "label" ); > > RJBS points out that "comment" implies "not really worth doing", and I > still don't like "name" be

Re: Test::Harness HTML output

On 2005-01-23, Ian Langworth <[EMAIL PROTECTED]> wrote: > I'm attempting to create fancy HTML output from running a test suite > and thought others might find this interesting. I've tried using > Test::Harness::Straps to create a feedback report inspired by Tinderbox > and BuildBot. > > ht

Benefits of a Real World switch from CVS to darcs

Hello, Here's a story of how I've been able to improve the quality of my Perl development process significantly: Benefits of a Real World switch from CVS to darcs http://mark.stosberg.com/Tech/darcs/cvs_switch/ Switching my source control system has made a big difference in my ability t

Re: TAP Version (was: RE: Test comments)

On 2005-02-15, Clayton, Nik <[EMAIL PROTECTED]> wrote: > >ver 1.1 If you go this route, I would make it clear whose emitting the version string: TAP version 1.1 ### Mark -- http://mark.stosberg.com/

Re: TAP Version (was: RE: Test comments)

On 2005-02-18, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Fri, Feb 18, 2005 at 01:13:05AM +0000, Mark Stosberg wrote: >> On 2005-02-15, Clayton, Nik <[EMAIL PROTECTED]> wrote: >> > >> >ver 1.1 >> >> If you go this route, I would

Re: Foreign modules in test scripts?

On 2005-02-20, Steffen Schwigon <[EMAIL PROTECTED]> wrote: > Hi! > > General testing question: > > Is it ok for a CPAN module to use other modules from CPAN only for the > test scripts (e.g. "Text::Diff")? > > First, I'm not sure about the usage policy. Maybe it's more common to > write tests more

Re: TAP and STDERR

On 2005-02-25, Michael G Schwern <[EMAIL PROTECTED]> wrote: > > I'm going to call a big, fat YAGNI on this one for the time being. I looked that one up. :) You Aren't Going to Need It. http://c2.com/cgi/wiki?YouArentGonnaNeedIt I like it. Mark -- http://mark.stosberg.com/

Re: Test::WWW::Mechanize 1.04

On 2005-03-04, Andy Lester <[EMAIL PROTECTED]> wrote: > I've updated Test::WWW::Mechanize to add get_ok() and follow_link_ok() > methods. If you've been writing > > $mech->get( $url ); > ok( $mech->success, 'Fetched home page' ); > > you can now do that as > > $mech->get_ok( $mech->success,

testing darcs with Perl (was: Re: testing non-modules)

I have a fork of the 'testing non-modules' question. :) I help maintain some Perl test scripts for darcs [1]. 1. http://www.darcs.net/ Right now the tests are run one at a time, losing the benefit of the summary report. I got stuck trying to think of how to best make this work. I don't thin

Re: testing darcs with Perl (was: Re: testing non-modules)

On Tue, Mar 08, 2005 at 08:23:31AM -0800, Michael G Schwern wrote: > > perl -MTest::Harness -e 'runtests @ARGV' tests/*.pl Aha. Thanks. > Why would you distribute a private copy of Test::Harness? To use 'prove', which your example above illustrates I don't need. > Or do you mean you

testing STDOUT and STDERR at the same time with Test::Output

On 2005-03-08, Michael G Schwern <[EMAIL PROTECTED]> wrote: > > PS I took a look at one of the Perl tests (pull.pl) and its needlessly > Unix-centric making lots of shell calls which can easily be done with > Perl, particularly rm -rf and mkdir -p (File::Path). Best to make it > cross-platform as

Re: testing darcs with Perl (was: Re: testing non-modules)

On 2005-03-08, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Tue, Mar 08, 2005 at 11:33:30AM -0500, Mark Stosberg wrote: >> > I'd make life simpler and dump the shell scripts, see the note about >> > cross-platform compatibility below. >> >> The

Re: testing STDOUT and STDERR at the same time with Test::Output

On 2005-03-08, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Tue, Mar 08, 2005 at 05:27:34PM +, Fergal Daly wrote: >> On Tue, Mar 08, 2005 at 04:56:08PM +, Mark Stosberg wrote: >> > Hmm...maybe Test::Output just needs a new feature: >> > >> &g

Re: testing STDOUT and STDERR at the same time with Test::Output

On Tue, Mar 08, 2005 at 05:48:28PM +, Fergal Daly wrote: > > In the case of though darcs though, is Perl just testing the output of > commands that have been systemed? If so they could just add 2>&1 to the > command line and then ignore stderr, I thought that wouldn't be portable. Mark

benchmark darcs with Perl

darcs [1] is slow in a few places, and I'm working on benchmarking tool in Perl to help monitor the performance. I'm got some questions about the best way to proceed. 1. http://www.darcs.net/ So far: I've divided the task into a couple specific problems: A. What repos to use for testing? B. A

Re: benchmark darcs with Perl

On Sat, Mar 12, 2005 at 03:29:32PM -0800, Michael G Schwern wrote: > > Well, if you're just going to look at the wall clock, why use the shell? Err...because I forgot about the simple 'time' command? > my $start_time = time; > `$bin diff 1/1 2>&1`; > my $end_time = time; >

Re: [RFC] adding skip option directly to plan()

On 2005-03-13, Geoffrey Young <[EMAIL PROTECTED]> wrote: > > nevertheless, what you are replying to was just a discussion about a feature > that doesn't exist in the standard Test::More toolkit but was brought up > because Apache-Test's plan() works a bit differently and there are enough > people w

Re: benchmark darcs with Perl

On 2005-03-13, Michael G Schwern <[EMAIL PROTECTED]> wrote: > > We can just check. > > $ perl -MBenchmark -wle 'timethis(10, sub { `perl -wle "rand for 1..100"` > })' > timethis 10: 11 wallclock secs ( 0.01 usr 0.00 sys + 8.64 cusr 0.14 csys = > 8.79 CPU) @ 1000.00/s (n=10) > > So the tim

Re: benchmark darcs with Perl

On 2005-03-14, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Mon, Mar 14, 2005 at 01:25:16AM +0000, Mark Stosberg wrote: >> I'm sorry-- I could have made this more productive by posting my own >> Benchmark >> code in the first place. Look what happens when

Re: Fwd: [ANN: WWW::Agent 0.03 has entered CPAN: [EMAIL PROTECTED]

On 2005-03-19, Andy Lester <[EMAIL PROTECTED]> wrote: > > login: { # block to define > how to log in >url m|https?://james.bond.edu.au/.*| or die "there is nothing to > log in here" > and fill uid $username

a less fragile way to test when we need to read and write to STDOUT?

r two people something got slightly off, causing the test to hang indefinitely. Windows users weren't having problems with the first method, so maybe I should just go back to that. I'm I missing an easier and less fragile way to test interactive commands with Perl? Thanks! Mark

Re: a less fragile way to test when we need to read and write to STDOUT?

On 2005-04-01, Michael G Schwern <[EMAIL PROTECTED]> wrote: >> commands with Perl? > > When using open2 you have to be careful to close WRITE before you READ so > the program does not hang waiting for more input. Once you've fixed that > the technique above should be just fine. > > sub echo { >

Re: a less fragile way to test when we need to read and write to STDOUT?

On 2005-04-01, George Nistorica <[EMAIL PROTECTED]> wrote: > > For commands that need more than one input (i.e. shell installers) you > can use the Expect module, which you can use to test such programs, that > wait your input for more than one time. Thanks for the tip. It led me to Test::Expect,

Re: a less fragile way to test when we need to read and write to STDOUT?

On 2005-04-01, George Nistorica <[EMAIL PROTECTED]> wrote: > > For commands that need more than one input (i.e. shell installers) you > can use the Expect module, which you can use to test such programs, that > wait your input for more than one time. Thanks for the tip. It led me to Test::Expect,

best practices for returning a "technical failure" page to a web browser?

uot;Internal Server Error" than a normal result page. Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . .

examples of testing cookies with WWW::Mechanize ?

This is how I figured out how to test a cookie with WWW::Mechanize: my $ses_id_from_cookie = $a->cookie_jar->{COOKIES}->{".$CFG{SITE_DOMAIN}"}->{'/'}->{CGISESSID}->[1]; ok($ses_id_from_cookie, "admin - Login screen sets cookie ($ses_id_from_cookie)"); Surely there is an easier/better way th

Re: examples of testing cookies with WWW::Mechanize ?

On 2005-04-05, Mark Stosberg <[EMAIL PROTECTED]> wrote: > This is how I figured out how to test a cookie with WWW::Mechanize: > > my $ses_id_from_cookie = > $a->cookie_jar->{COOKIES}->{".$CFG{SITE_DOMAIN}"}->{'/'}->{CGISESSID}->[1]; >

prove with Devel::Cover example?

Ok, I'm feeling brain dead about this one-- this seems easy but I'm missing it. How can I use 'prove' and Devel::Cover together? I tried: perl -MDevel::Cover prove ... but didn't cover the scripts that ran. Mark

Re: prove with Devel::Cover example?

On 2005-06-04, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Fri, Jun 03, 2005 at 02:04:50PM -0500, Pete Krawczyk wrote: >> }How can I use 'prove' and Devel::Cover together? I tried: >> >> HARNESS_PERL_SWITCHES=-MDevel::Cover prove file.t > > Kinda surprised there's not a --cover switch. I w

How to get started with Test::TAP::HTMLMatrix

Hello, I'd like to use Test::TAP::HTMLMatrix to better visualize the state of large test runs. However, I can't tell from the docs how to run the test suite such that it gets involved in the process. Could someone provide an example? Thanks! Mark -- http://mark.stosberg.com/

Looking into integrating Test::TAP::HTMLMatrix with prove

t have meaningful data on them and aren't synchronized (STDOUT and STDERR). Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . .

AnnoCPAN and a wiki POD idea

If you haven't see AnnoCPAN, it's a new way to share comments on Perl POD: Example: http://www.annocpan.org/dist/Net-ICal-0.15/lib/Net/ICal.pm I have an idea about taking it a step further-- making it easier to close the loop with the author to integrate updates. CPAN documentation could be st

OT: integrating RSS with mail readers (was: Re: AnnoCPAN and a wiki POD idea)

On 2005-07-08, Michael G Schwern <[EMAIL PROTECTED]> wrote: > >> PS. An AnnoCPAN tip: Notice that if you are an author, you can subscribe >> to all comments on your modules: >> http://www.annocpan.org/~MARKSTOS/recent.rss > > Not knowing anything about RSS I put the URL into Firefox and it asked me

Re: prove with Devel::Cover example?

On Sat, Jun 04, 2005 at 02:10:37AM -0700, Michael G Schwern wrote: > On Fri, Jun 03, 2005 at 02:04:50PM -0500, Pete Krawczyk wrote: > > }How can I use 'prove' and Devel::Cover together? I tried: > > > > HARNESS_PERL_SWITCHES=-MDevel::Cover prove file.t > > Kinda surprised there's not a --cover s

A binary testing system with a log of system calls?

Hello, I help test the darcs ( http://www.darcs.net/ ) binary with Perl. The code itself is written in Haskell, but that doesn't matter here. A developer had an interesting request, which I would like to pursue. Where there is a test failure in the Perl test script, he would like to look at a se

testing Javascript applications ?

It used to be that WWW::Mechanize was a "good enough" testing tool for my web applications. It doesn't do Javascript, but I used very minimal Javascript and thus worked around that limitation. Along comes AJAX. It offers benefits that make JavaScript seem worth using. But now how I can test t

Re: testing Javascript applications ?

On 2005-11-28, Ovid <[EMAIL PROTECTED]> wrote: > --- Mark Stosberg <[EMAIL PROTECTED]> wrote: > >> What are other folks doing to test web applications that make heavy >> use >> of JavaScript? > > If you want to leverage your Perl testing knowledge,

Re: automated web testing with selenium

On 2005-11-02, Luke Closs <[EMAIL PROTECTED]> wrote: > > Also, yesterday Test::WWW::Selenium was uploaded to CPAN, so Selenium > can now be driven by perl! Test::WWW::Selenium seems interesting, but I could use an example it would be useful to use, versus the standard techniques. From the docs,

Re: Running test suites under PersistentPerl

On 2005-12-05, Michael Graham <[EMAIL PROTECTED]> wrote: > > This should be compatible with regular (non-PersistentPerl) use as well. > > ... > > Limitations and Caveats with the system: > > * Scripts that muck about with STDIN, STDOUT or STDERR will probably >have problems. > > * The usual p

integrating Selenium with a traditional perl test suite ?

Hello, So I'm now using and liking Selenium after several recommendations from this list. I'm interested to know how other people integrate it with a traditional perl test suite. It seems like there are two possibilities: http://selenium.thoughtworks.com/ 1. Use "prove" as the primary test sui

Re: Running test suites under PersistentPerl

On 2005-12-07, Mark Stosberg <[EMAIL PROTECTED]> wrote: >> >> Limitations and Caveats with the system: >> >> * Scripts that muck about with STDIN, STDOUT or STDERR will probably >>have problems. >> >> * The usual persistent environment cave

create test scripts that run from the web as well from the web

Now that I'm using Selenium, I wanted to integrate some of the perl testing tools I already like. http://selenium.thoughtworks.com/ I found one way to do this was to create a test script that runs as a CGI script. Adding just one line to the top of the script allows it to run from the web or fro

Re: TAP as XML

On 2005-11-22, Michael Peters <[EMAIL PROTECTED]> wrote: > > > Stevan Little wrote: >> Michael, >> >> You might want to look at some of the work on the Pugs test suite. >> >> http://m19s28.vlinux.de/cgi-bin/pugs-smokeserv.pl >> >> It uses (among other things) Test::TAP::Model and >> Test::TAP::

Re: TAP as XML

On Tue, Dec 13, 2005 at 02:01:18PM -0500, Michael Peters wrote: > >>>It uses (among other things) Test::TAP::Model and > >>>Test::TAP::HTMLMatrix, and uses YAML as an intermediate test-run format. > >> > >>Actually, Test::TAP::HTMLMatrix is what I currently use for test reports > >>that > >>get e

TODO test paradox: better TODO test management?

Here's my test-first TODO test management paradox: If I write a failing test and share it through the central repo, the smoke bot fails and keeps sending us e-mail until it is fixed, which can be annoying when these are un-implemented features and not bugs. The effect can be quit paying attention

Re: ANNOUNCE - Smolder 0.01

On 2006-03-05, Michael Peters <[EMAIL PROTECTED]> wrote: > > > Yuval Kogman wrote: >> On Sat, Mar 04, 2006 at 09:09:00 -0500, Michael Peters wrote: >>> It's very similar in nature to the Pugs smoke test server, but is completely >>> project agnostic. It's also completely self contained (contains lo

best way to migrate to Test::WWW::Selenium ?

(This message is targeted at the Test::WWW::Selenium maintainers, but I think the response will be of interest to others here ). I've got a test suite built with Selenium, but I would like to the output in TAP to centralize the reporting, perhaps using Smolder once I Smolder installed. It appear

Re: Backwards (?) kwalitee definition on qa.perl.org

On 2005-07-09, Nik Clayton <[EMAIL PROTECTED]> wrote: > http://qa.perl.org/phalanx/kwalitee.html says: > > What is kwalitee? > > Kwalitee is inexact quality. We don't know exactly what it is, > but we know it when we see it. > > Isn't that backwards? I thought 'kwalitee' was suppos

Re: how to get archname

Michael Peters wrote: > Matisse Enzer wrote: > >> forgive me but what is the magic variable to get archname? for example, >> on my system archname is >>darwin-thread-multi-2level > > use Config; > $Config{archname} If you just need to see it and don't need to use it directly in Perl, you c

favorite XML testing module?

What's your favorite Test:: module for checking of a given document is valid well-formed XML? When I looked several years ago I didn't find one that suited me, so I created and released Test::XML::Valid http://search.cpan.org/perldoc?Test::XML::Valid It has a shortcomings reflected in the bug

Feedback on the undocumented --rules option for 'prove'

In 2008 Alex Vandiver contributed a patch to "prove" that allowed you to specify that you wanted some tests to run in parallel and others in serial. This is a great feature for those of us with large test suites that would like to test advantage of parallism, but have suites that aren't 100% paral

[PATCH] for review: docs for the undocumented --rules option for 'prove' (and related TAP::* bits)

However, I see that 'rules' is the subject of testing in t/scheduler.t. Do the individual tests in that file give you any clue as to how to proceed? Thanks for the feedback, Jim. I believe I found what I needed over the weekend. First, I made a list of what needed to be done here as some r

Re: [PATCH] for review: docs for the undocumented --rules option for'prove' (and related TAP::* bits)

On 08/20/2012 07:29 AM, Mark Stosberg wrote: > >> However, I see that 'rules' is the subject of testing in t/scheduler.t. >> Do the individual tests in that file give you any clue as to how to >> proceed? > > Thanks for the feedback, Jim. > > I bel

Re: [PATCH] for review: docs for the undocumented --rules option for'prove' (and related TAP::* bits)

On 08/30/2012 06:56 PM, Eric Wilhelm wrote: > # from Mark Stosberg on Thursday 30 August 2012: >> I suspect there's a bug that works as follows, but I haven't isolated >> it yet. Here's my suspected trigger: >> >> - First start some tests that are pa

Re: [PATCH] for review: docs for the undocumented --rules option for'prove' (and related TAP::* bits)

On 09/03/2012 01:52 PM, Eric Wilhelm wrote: > # from Mark Stosberg on Friday 31 August 2012: >> I looked into the App/Prove.pm source code and immediately spotted the >> issue. It hardcodes that all "rules" should run in parallel. Thus, >> there would be no way t

Re: preforking prove

On 11/06/2012 01:25 PM, Karen Etheridge wrote: > On Tue, Nov 06, 2012 at 09:59:48AM -0800, Jonathan Swartz wrote: >> For each test run, instead of loading a .t file, you're making a request >> against the Starman server. So you can obviously hit it with multiple >> simultaneous requests. > > For

Re: preforking prove

On 11/07/2012 03:51 PM, Jonathan Swartz wrote: > Now on cpan. A much simpler solution than what I suggested :) and apparently > still works with parallel testing. Thanks miyagawa! > >https://metacpan.org/module/forkprove I did some benchmarking last night and found no real benefit over prove

Re: preforking prove

> I wasn't able to get forkprove to work with Test::Class, because of Test::Class's insistence that tests be declared at compile time. > >swartz> cat t/Sanity.t >#!/usr/bin/perl >use CHI::t::Sanity; >CHI::t::Sanity->runtests; > >swartz> forkprove t/Sanity.t >t/Sanity.t

Re: Anyone want Test::Class::Moose?

> So, does this look useful for folks? Is there anything you would change? > (It's trivial to assert plans for classes and the entire test suite rather > than rely on done_testing(), but I haven't done that yet). I would welcome it as an option. We use Test::Class now, but I have the sense tha

Re: Anyone want Test::Class::Moose?

On 12/15/2012 05:37 PM, Ovid wrote: > Hi Justin, > > This is something I've wondered as well. Several times when people asked me > about using Test::Class with Moose I pointed them to Test::Able, though I > confess I never used that code. Invariably they would not choose it. I think > what's go

Using NYTProf for code coverage?

Greetings, I was tasked with working on code coverage for a large project, but had difficulty getting Devel::Cover to run. We had Devel::NYTProf handy, and I realized that although that tool focuses on profiling, it produces data that appears that it can be used for code coverage instead. Having

speeding up Selenium testing with client-side caching?

Our team was recently benchmarking using Mechanize vs Selenium::Remote::Driver for a basic request pattern: - get a page - check the title - check the body content I expected Selenium to be slower, but was surprised it was about 8 times slower! As I look more closely at the inner workings, what

Best practices for TODO test management?

We have a large test suite with 20,000+ tests in it, and a number of passing TODO tests in it. Our problem is that once a test is marked as TODO, it falls off our radar, and we are unlikely to notice it again. What are some suggestions to make sure that passing TODO tests get regular attention?

interest in converting LWP / Mech hierarchy to roles?

There's perhaps no better illustration of the values of roles vs inheritance in CPAN modules than the mess than that the LWP inheritance tree. There's so many modules that extend LWP or Mechanize through sub-classing, but can't easily be combined with getting into diamond inheritance: Here's a s

Re: Best practices for TODO test management?

On 02/27/2013 09:44 AM, Ovid wrote: > Hi Mark, > > I know this isn't exactly what you want, but a long time ago I added a > --directives switch to 'prove' to help with this. If you do this: > > prove -lr --directives t/ > > 'prove' will *not* run in verbose mode, except for any tests with >

Re: Best practices for TODO test management?

On 02/27/2013 02:48 PM, Graham TerMarsch wrote: > On February 27, 2013 09:06:23 AM Mark Stosberg wrote: >> What are some suggestions to make sure that passing TODO tests get >> regular attention? >> > [.snip.] >> >> In case this context matters-- our

Re: Using NYTProf for code coverage?

On 02/28/2013 06:02 AM, Christian Walde wrote: > On Wed, 27 Feb 2013 14:49:44 +0100, Mark Stosberg > wrote: > >> I was tasked with working on code coverage for a large project, but had >> difficulty getting Devel::Cover to run. > > Can you maybe go into details as to

Re: interest in converting LWP / Mech hierarchy to roles?

On 02/28/2013 10:45 AM, Andy Lester wrote: > > On Feb 27, 2013, at 10:04 AM, Mark Stosberg <mailto:m...@summersault.com>> wrote: > >> Then you have the WWW::Mechanize sub-classes. Here's a sampling: >> >>Test::WWW::Mechanize > > As far as

Re: interest in converting LWP / Mech hierarchy to roles?

On 02/28/2013 11:29 AM, Andy Lester wrote: > > On Feb 28, 2013, at 10:26 AM, Mark Stosberg <mailto:m...@summersault.com>> wrote: > >> I'd like to have a Mechanize that has both the testing functions, and >> also JavaScript support, which the WWW::Scripter s

Re: interest in converting LWP / Mech hierarchy to roles?

On 02/28/2013 03:26 PM, Mike Doherty wrote: > On 13-02-28 09:07 AM, Yanick Champoux wrote: >> On 13-02-27 11:04 AM, Mark Stosberg wrote: >>> Perhaps if some of these get converted to extend-by-roles instead of >>> extend-by-inheritance, some others will follow along,

Re: TAP::Harness uses lots of RAM to store test results

> Which makes me wonder - just how much memory is TAP::Parser using. > In particular, is TAP::Parser using the same amount of memory to store 65850 > "ok"s as it would to store some mix of 65850 "ok"s and "not ok"s? > Which I'm starting to think, for large test suites, isn't that efficient. > Most

Re: Test::Builder, MakeMaker & Consensus QA Hackathon Achievements

On 04/15/2013 12:20 PM, Michael G. Schwern wrote: > I've just updated the wiki with the achievements around the projects I > was associated with. I'll paste them below. > http://2013.qa-hackathon.org/qa2013/wiki?node=Achievements Thanks to all the Hackathon contributors for these updates! As a CP

Re: How might we mark a test suite isn't parallalizable?

On 05/02/2013 03:39 PM, brian d foy wrote: > In HARNESS_OPTIONS we can set -jN to note we want parallel tests > running, but how can a particular module, which might be buried in the > dependency chain, tell the harness it can't do that? > > It seems to me that by the time the tests are running, i

Re: How might we mark a test suite isn't parallalizable?

> When can a test not be parallelizable? Most of the examples that I can > think of (depending on a file resource, etc) smell like a design failure. > Tests should usually be able to use a unique temp file, etc. Here's an example: Say you are testing a web application that does a bulk export of

Re: How might we mark a test suite isn't parallalizable?

> No, you can't have your tests clean up after themselves. For two > reasons. First, that means you have to scatter house-keeping crap all > over your tests. Second, if you have a test failure you want the > results to be sitting there in the database to help with debugging. There is another w

Re: How might we mark a test suite isn't parallalizable?

> OK, but you still have to clean out your database before you start each > independent chunk of your test suite, otherwise you start from an > unknown state. In a lot of cases, this isn't true. This pattern is quite common: 1. Insert entity. 2. Test with entity just inserted. Since all that

Re: How might we mark a test suite isn't parallalizable?

>> We have a cron job that runs overnight to clean up anything that was >> missed in Jenkin's runs. > > No offense, but that scares me. If this strategy was so successful, > why do you even need to clean anything up? You can accumulate cruft > forever, right? Ha. Like any database, smaller ones

Re: TAP::Harness and -w

On 09/17/2013 11:26 AM, Leon Timmermans wrote: > On Sun, Jul 7, 2013 at 11:45 AM, Ovid > wrote: > > I'm winding up with astonishingly little bandwidth due to launching > our company, so I was hoping to see a strong consensus from the > users. I would

Re: TAP::Harness and -w

On 09/17/2013 01:20 PM, chromatic wrote: > On Tuesday, September 17, 2013 01:13:26 PM Mark Stosberg wrote: > >> An attempting-to-be-neutral summary would be very helpful. > > Pro of adding -w to test runs: > - that's how Test::Harness has always worked, and people