Hi! > For instance, it is painful to work with tests in PHP source tree when they > are called 001.phpt, 002.phpt and so on - you need to open each file and read > it to see what it intends to test. My tool uses file names instead, which > makes browsing source tree with tests more productive and makes --TEST-- > section redundant (simply ignored).
I think --TEST-- should absolutely be supported. Filename is not nearly enough to properly describe the content of the test. Something like "Test whether foo(bar($baz)) crashes if called more than twice (bug #1234)" is not going to be captured in a filename. Filenames and informative descriptions are not the same thing. I'll look more into what other requirements are needed (one suggestion would be try to keep option compatibility with the old tool if possible, so people could use their old habits) and write later, but I think supporting proper test descriptions would definitely be one of them. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
