Return-Path: Delivered-To: apmail-httpd-test-dev-archive@httpd.apache.org Received: (qmail 47955 invoked by uid 500); 13 Dec 2001 03:20:46 -0000 Mailing-List: contact test-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: test-dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list test-dev@httpd.apache.org Received: (qmail 47944 invoked from network); 13 Dec 2001 03:20:45 -0000 Message-ID: <3C181E8F.2040903@stason.org> Date: Thu, 13 Dec 2001 11:20:47 +0800 From: Stas Bekman Organization: Hope, Humanized User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011012 X-Accept-Language: en-us MIME-Version: 1.0 To: test-dev@httpd.apache.org Subject: Re: httpd-test/perl-framework tests bug report References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Doug MacEachern wrote: > On Tue, 11 Dec 2001, Stas Bekman wrote: > > nice. but again, build/bugreport.pl would have to be copied for every > project that uses Apache-Test. would be better if there was an > Apache::TestReport module and tiny generated t/REPORT script. ok, the only problem with this specific script is that it doesn't belong to Apache::Test. It's a bug reporting tool. Hmm, bugreport in modperl doesn't use Apache::Test at all. bugreport in httpd-test/perl-framework need Apache::Test only to get the environment. I think that once modperl gets released we want build/bugreport.pl be installed somewhere on the system and accept only bug reports that use this script. Otherwise it always takes 3 to 10 emails to get the required info from the user in trouble :( > i'm also thinking we should have: > > Apache::TestRun->generate_script that can be called from Makefile.PL > that generates t/TEST rather than require each project to have a TEST.PL > same for: > > Apache::TestRunPerl > Apache::TestSmoke > Apache::TestSmokePerl > Apache::TestReport agreed, when you create t/TEST how do you know whether you should call Apache::TestRunPerl (mod_perl) or Apache::TestRun (non-modperl)? Should it be something like this: Apache::TestRun->generate_script(t/TEST => Apache::TestRunPerl) or should the generate_script be implemented by all these classes: Apache::TestRunPerl Apache::TestSmoke Apache::TestSmokePerl Apache::TestReport so each can supply a tuned script. If you look at t/TEST and t/SMOKE they aren't the same, as they use a different @INC fixups. _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/