Re: Testing with concurrent sessions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Testing with concurrent sessions
Date
Msg-id 1262815709.14688.6.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Testing with concurrent sessions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Testing with concurrent sessions  ("David E. Wheeler" <david@kineticode.com>)
Re: Testing with concurrent sessions  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
List pgsql-hackers
On ons, 2010-01-06 at 15:52 -0600, Kevin Grittner wrote:
> "David E. Wheeler" <david@kineticode.com> wrote:
>  
> > Last I heard, Andrew was willing to require Test::More for
> > testing, so that a Perl script could handle multiple psql
> > connections (perhaps forked) and output test results based on
> > them. But he wasn't as interested in requiring DBI and DBD::Pg,
> > neither of which are in the Perl core and are more of a PITA to
> > install (not huge, but the barrier might as well stay low).
>  
> OK, I've gotten familiar with Perl as a programming language and
> tinkered with Test::More.  What's not clear to me yet is what would
> be considered good technique for launching several psql sessions
> from that environment, interleaving commands to each of them, and
> checking results from each of them as the test plan progresses.  Any
> code snippets or URLs to help me understand that are welcome.  (It
> seems clear enough with DBI, but I'm trying to avoid that per the
> above.)

Then I don't see much of a point in using Perl.  You might as well fire
up a few psqls from a shell script.



pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: unresolved bugs
Next
From: "David E. Wheeler"
Date:
Subject: Re: Testing with concurrent sessions