RE: [PHP-QA] 64-bit SGI account offer
| From: | Melvyn Sopacua | Date: | Fri, 01 Nov 2002 15:26:03 +0000 |
| Subject: | RE: [PHP-QA] 64-bit SGI account offer | ||
| References: | 1 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-6551@lists.php.net to get a copy of this message | ||
At 16:10 1-11-2002, Sebastian Nohn wrote:
Disagree. It's just a verification. You can also more easy see when something broke on a certain machine with a certain configuration. This evening im going to take a look at the make-tests.php+1 on SKIP+FAIL PASS = PASS - don't bother. Reason for SKIP: if test A SKIP's because of condition 'foo', but test B fails because of condition 'foo', test B is flawed.
A common separator should be all that's needed. Depending on packages like WDDX or XML, means they should be working. If you emulate these extensions with regexes or string functions, you depend on these two to be working. Let's keep the output parseable, but depending on as less functions as needed. Currently ./configure --disable-all ; make all test already doesn't work, because of preg_* functions. Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn SopacuaThe user should have the option to decide via a config-file to write the xml to disk or to directly submit it to the webserver.Why involve XML into this? We already have a facility to submit test via a POST request to the QA team and if that fails, the results are written to a plain text file a user can read and if they want email manually to QA. But it's unreadable. I don't have the time and the pleasure to compare 9 result-logs. It would be much easier to compare this via an web interface. XML (or especially WDDX) could easily be used to send the results to a website, store and in a database and write a interface to this database. This has already be done (see http://php.nohn.net/autotest-stats.php ) for an example.