develooper Front page | | Postings from August 2007

a "standard" place for extra tests

Thread Next
Eric Wilhelm
August 16, 2007 20:14
a "standard" place for extra tests
Message ID:
Returning to something that came up in the 'testing pod' thread...

# from Adam Kennedy on Tuesday 31 July 2007 08:23 pm:
>A small nit, if we end up converging around the use of a relatively
>standard directory name, can we at least use something relatively
>self-evident? For example "author/"?

I would like to suggest that we adopt, recommend, (and support with 
tools, etc) a "standard" (convention) for storing additional tests.


Or something along those lines.  At this point, 'author' is the only 
child directory I'm fairly certain of.

I am certain that more than one 'extra tests' directory is needed, thus 
the thought to make them into subdirectories (objections?)

(They cannot live under 't/' due to compatibility issues.)

As for the 'xt' name:  it tends to sort pretty soon after 't', as in 
'these come next'.  I think anything starting with 't' would get 
annoying as far as tab-complete goes.  Similarly, 't2' might conflict 
with primitive version-control habits.

Better suggestions?

Aside:  I've been playing with using non-'.t' file extensions for this 
and storing them under t/, but this requires extra support from 
Module::Build, runtests, prove, ack, etc.  The only drawback to putting 
them outside of the 't/' directory seems to be that refactoring habits 
like 'grep $method -r t' might need adjustment.  Vs. this "more .t 
files one directory to the right" approach where you can easily get a 
bug report by asking the user to simply run `prove xt/network/`.

"Matter will be damaged in direct proportion to its value."
--Murphy's Constant

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About