[tap-l] pgTAP

[David E. Wheeler]

On Jun 15, 2008, at 09:12, Eric Wilhelm wrote:

> I still think the suffix thing tends to hurt.  In any case, you have  
> to
> find a way to configure the switches for psql from a few packages away
> to make it work with prove.

Yes, that's why I wrote pg_prove. But Module::Build doesn't use prove,  
it uses Test::Harness, IIRC.

> No.  It doesn't even need to assume that the platform supports  
> shebags.
> (trivia:  perl5 automagically interprets shebangs if given one which
> doesn't contain 'perl' -- Test::Harness 2 (ab)used that feature, but
> this is not the path I suggest because it also passes your perl
> switches to whatever that interpreter is.)

Yeah, that's not really desirable.

> Some languages may not even support a comment on the first line or a
> shebang-compatible comment, etc.

Right. These are SQL scripts. You can have --  or /* */ comments, but  
not #!.

> The idea is to inspect the file for shebangs (and shebang-like things
> (or any distinguishing directive/identifier on some line in the  
> file.))
> The harness would then choose the associated executable+switches (or
> Source subclass) to process it.  These would be configured via  
> plugins,
> which might register themselves with a shebang regexp or grep  
> callback.

That would be fine, especially if there were more than one way to map  
test files with plugins, such as shebang, file name suffix, or  
whatever. Could they all be put in there so that we can see what sorts  
of cow paths develop?

Best,

David