Travis Swicegood wrote:
On Jun 19, 2008, at 9:03 AM, Steph Fox wrote:
There's nothing wrong with that approach. I'm trying to find
something that addresses the problem (i.e., "how can I not run tests
that are going to take a long time to run?"), while providing enough
flexibility to answer other problems (i.e., "how can I skip X tests
that I don't care about?").
If there's a way to address the problem without making it so
specific, I'm all for it.
I mostly agree - I'm just looking at 'here and now' rather than 'when
the nice new test suite stuff is done'. 'Here and now', there isn't a
reliable way to set this up and skipif looks like the cleanest option.
The only problem with that is everything you add I've got to add to my
GSoC project so PHPT :-)
That might not be a bad idea.
I think the long-term goal should be the ability to "force skip" files
based on an --exclude parameter, an ini conf file (looks for --ini-file
<file> or <cwd>/tests.ini), and an ENV variable. The first and last
would just be separated by the PATH_SEPARATOR for regex patterns.
The ini file is a great idea, as one can create groupings of test suites
independent of the tests.
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php