Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30070 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6772 invoked by uid 1010); 5 Jun 2007 14:46:23 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 6756 invoked from network); 5 Jun 2007 14:46:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jun 2007 14:46:22 -0000 Authentication-Results: pb1.pair.com header.from=zoe.slattery@googlemail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=zoe.slattery@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 66.249.92.174 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: zoe.slattery@googlemail.com X-Host-Fingerprint: 66.249.92.174 ug-out-1314.google.com Linux 2.4/2.6 Received: from [66.249.92.174] ([66.249.92.174:34006] helo=ug-out-1314.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8A/25-11953-C3775664 for ; Tue, 05 Jun 2007 10:46:22 -0400 Received: by ug-out-1314.google.com with SMTP id m2so201470uge for ; Tue, 05 Jun 2007 07:45:28 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=kIUlkKnmaBlA+YBNYz9xY2CdcvNYfpDQY5kwvDSZo3JLUb+6WenTDdC/uJuGs129xJ1uT07g5Ww6aVw1NbYtJ09vjkAIIFUe81lHoz/XIpBqCsTiMsI4ZbGVPQjD/hecUfg/4/KV4wgrx7by2YLyQLrOKHpPQ2sbgFoL3Gq/hVk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=LpGP2jGKLOrLakg0LnmOcdX5L3qvZr3l8MxdSNHxl9cikDnB2W4aPsDSOXBgaoID/WnwsDu8f67Fg77J09JRG8r/5pA9sAkOoGDg0Y9nZE8Kj45EHaGm6OnspQnrYJGTsWirVEBjxgQKtHlnqjWmLL4kZZXTL5qfzaTC/cQDXQ4= Received: by 10.67.106.3 with SMTP id i3mr501264ugm.1181054728295; Tue, 05 Jun 2007 07:45:28 -0700 (PDT) Received: from ?9.20.191.175? ( [195.212.29.75]) by mx.google.com with ESMTP id b33sm3554477ika.2007.06.05.07.45.27; Tue, 05 Jun 2007 07:45:27 -0700 (PDT) Message-ID: <46657707.4030809@googlemail.com> Date: Tue, 05 Jun 2007 15:45:27 +0100 User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Pierre CC: internals@lists.php.net References: <46652CE0.7060807@googlemail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Bugzilla category for test case bugs? From: zoe.slattery@googlemail.com (Zoe Slattery) Pierre wrote: > On 6/5/07, Zoe Slattery wrote: >> >> Hi all >> Would it be possible to have a Bugzilla category for test case bugs? >> The only alternative seems to be to raise a bug against the >> implementation - which doesn't seem quite right. > > Why not simply put them in the related category? For example GD for a > problem in a GD test. With an extra category, I will simply not see > any bugs related to my extension tests, even when I'm fetching the > 'GD' category bugs. That's reasonable. The reason that I asked was that all I'm doing is writing functional tests - so, for example - if I make a mistake in a functional test for "Filesystem" I don't necessarily see why the developer working on Filesystem should have to look at it, or spend their time fixing it. By the way, this came up because a colleague found a mistake in a test and couldn't work out the right way to raise a defect. I also noticed that there are separate categories for Documentation defects - so it seemed to me to be consistent to have one for tests. I'm happy to ask people to with raise them against the implementation - I just didn't want to cause unecessary work for the core developers. Of course I'm *hoping* that there won't be enough defects in the test cases to cause anyone major headaches :-) > > What would rock is a bug "type" field. A bug can be GD and Testing > related, or Ming and Documentation. > --Pierre >