Re: run-tests.php options

From: Date: Mon, 04 May 2009 18:41:23 +0000
Subject: Re: run-tests.php options
References: 1 2  Groups: php.qa 
Request: Send a blank email to php-qa+get-64866@lists.php.net to get a copy of this message
Nuno Lopes wrote:
I've been trying to figure out what all the configuration settings (command line and ENV) do in run-tests.php. I have documented them here:http://wiki.php.net/wiki.php.net/qa/runtests/configuration; some settings can be specified by bit command line and ENV variables. There are two points to this: 1) I'd like regular users to tell me what they would really like to see re-implemented in the new version, I have a view on some already but I'm don't want to make a 'yes/no' decision without some feed back. Please would you reply with your 'must have' options?
So my must have list also includes the following: - TEST_PHP_ARGS: necessary when you run 'make test' but you still want to pass some extra options. btw this is not about passing arguments to the php binary, but to inject options in the run-tests.php script itself Yes - mistake in my doc. And I knew that because I had already implemented it, correctly :-)
- keep-all - absolutelly necessary for the gcov thing and for any other data mining program Ok - that is implemented too.
- I also would add a new option to specify arguments to valgrind. Currently the approach involves messing with a valgrind environment variable that gets lost sometimes when spawning new processes. A must have, that should have been implemented loong ago. Right - will add to the list :-) may need a bit of help with a test case later on...
Zoe

« previous php.qa (#64866) next »