Re: changing make test for automatic testing

From: Date: Tue, 28 Jan 2003 09:43:22 +0000
Subject: Re: changing make test for automatic testing
References: 1 2 3 4  Groups: php.qa 
Request: Send a blank email to php-qa+get-8525@lists.php.net to get a copy of this message
On Tue, 28 Jan 2003, Derick Rethans wrote: > I spoke with Kai some days again on IRC, here the log: > > --- Log opened Mon Jan 20 13:04:48 2003 > 13:04 -!- Irssi: Starting query with CyberBLN > 13:04 <CyberBLN> please take a look: > http://php-qa.kai-schroeder.net/ > 13:05 <Derick> oooh :) > 13:05 <Derick> are you still parsing the output? > 13:06 <CyberBLN> tests are in a mysql ... 30 tables, 24.000 rows > 13:07 <Derick> so you can also have this details per testcase? > 13:08 <CyberBLN> right, I can complete restore the mail > 13:08 <Derick> ok > 13:08 <Derick> that is very good > 13:08 <Derick> so what we have to do is: > 13:08 <Derick> 1. stop mailing to the list > 13:09 <Derick> 2. change the script that recieves the post to store it in the db > 13:09 <Derick> 3. add a nice interface to see the test results > 13:09 <Derick> 4. mail summaries every week > 13:09 <Derick> does that sound sane? > 13:09 <CyberBLN> yes > 13:10 <CyberBLN> 0. repair output (line breaks on winnt) In addition to this that instead of asking for an email address, I think who should hand out 'keys' to different systems, so that we can track the testcases per system itself, and not only by email address. I plan to only hand out keys for people that are in QA, so that we can also select between tests done by users and by QA people. In order to be able to divert between different systems we should use the uname() output, which is a PHP function. We then can group by architecture, os and more. Derick -- ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ -------------------------------------------------------------------------

« previous php.qa (#8525) next »