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.
I think the naming thing would be a better idea for something that's
just starting out. It's a less good idea for a test suite that already
exists IMHO.
Agreed. If we were to go this route, I'd actually consider adding a
run-tests.ini or some such that allows you to configure things like
excluded file patterns.
That might not be a bad idea.
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
