[Webtest] Re: Bug trackin tool for webtest?

Lisa Crispin webtest@lists.canoo.com
Fri, 07 Jan 2005 15:36:49 +0000


--NextPart_Webmail_9m3u9jl4l_22818_1105112209_0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

I personally haven't felt the need for a bug tracking tool for WebTest, but I only use the basic functionality, I'm not trying to do anything very sophisticated with it.  I agree with Mittie, there really aren't so many bugs that the overhead of a bug tracking tool is worthwhile.  Also, if there's a bug that affects a lot of people, there will be lots of postings to the mailing list about it, which will alert someone capable of fixing the bug that it's a high priority.  
-- Lisa


-------------- Original message from "Dierk Koenig" <dierk.koenig@canoo.com>: -------------- 


> I used several bug-tracking tools (Remedy, ClearQuest, Peregrine, 
> Bugzilla, Gnats, Jira) and I found them all more difficult to use 
> than a mere Wiki Page. 
> Sure, when you have to manage a large amount of bugs then you may 
> need such a support, but I always felt that entering bugs is 
> really complicated. What type of bug is it? What part of the 
> system is concerned? What is its priority? and so on 
> Most of the time I don't know what to fill in and what happens 
> if I fill in nothing or something wrong. 
> 
> Watching the bug-fixing activities of an open-source project 
> can definitely reveal something about the project. 
> (Not only how active they are, but also how buggy the 
> Software is.) 
> 
> cheers 
> Mittie 
> 
> > -----Original Message----- 
> > From: webtest-admin@lists.canoo.com 
> > [mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot 
> > Sent: Freitag, 7. Januar 2005 13:47 
> > To: webtest@lists.canoo.com 
> > Subject: [Webtest] Re: Bug trackin tool for webtest? 
> > 
> > 
> > I fear that it's too basic and to complicated: to enter a bug a 
> > user needs to create a new page as well as to update the 
> > overview page. 
> > 
> > Furthermore, a bug tracking tool can be used by visitors to see 
> > the activity of the project: how many issues opened and 
> > fixed in the last x months. 
> > 
> > Marc. 
> > 
> > Dierk Koenig wrote: 
> > > Hi, 
> > > 
> > > Yes, having such a tool is sometimes convenient. 
> > > 
> > > On the other hand, installation, maintenance, etc. again add 
> > > to the workload. So it needs to pull its weight. 
> > > 
> > > Currently we only have few Bugs open in Canoo WebTest and everything 
> > > that is not immediately solved and is in jeopardy of being lost 
> > > can be added to 
> > > http://webtest-community.canoo.com/wiki/space/Bug+Reports 
> > > This solution has the additional benefit, that you can google for 
> > > it. 
> > > 
> > > Do you think, we need more than that? 
> > > 
> > > cheers 
> > > Mittie 
> > > 
> > > 
> > >>-----Original Message----- 
> > >>From: webtest-admin@lists.canoo.com 
> > >>[mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot 
> > >>Sent: Freitag, 7. Januar 2005 10:59 
> > >>To: webtest@lists.canoo.com 
> > >>Subject: [Webtest] Bug trackin tool for webtest? 
> > >> 
> > >> 
> > >>Hi, 
> > >> 
> > >>what about making a bug tracking tool available on webtest website? 
> > >> 
> > >>Currently the problems reported on the mailing list have a high 
> > >>risk to be lost if not quickly solved. A special tool (à 
> > >>la bugziall, mantis, jira or other) would allow users to query 
> > >>existing bug reports, to enter new ones if they find some 
> > >>news issues and for developers it would give an overview of the 
> > >>current problems. 
> > >> 
> > >>Marc. 
> > >> 
> > >>_______________________________________________ 
> > >>WebTest mailing list 
> > >>WebTest@lists.canoo.com 
> > >>http://lists.canoo.com/mailman/listinfo/webtest 
> > >> 
> > 
> > _______________________________________________ 
> > WebTest mailing list 
> > WebTest@lists.canoo.com 
> > http://lists.canoo.com/mailman/listinfo/webtest 
> > 
> 
> _______________________________________________ 
> WebTest mailing list 
> WebTest@lists.canoo.com 
> http://lists.canoo.com/mailman/listinfo/webtest 
--NextPart_Webmail_9m3u9jl4l_22818_1105112209_0
Content-Type: text/html
Content-Transfer-Encoding: 8bit

<html>
<!-- BEGIN WEBMAIL STATIONERY -->
<head></head>
<body>
<!-- WEBMAIL STATIONERY noneset -->
<DIV></DIV>
<DIV>I personally haven't felt the need for a bug tracking tool for WebTest, but I only use the basic functionality, I'm not trying to do anything very sophisticated with it.&nbsp; I agree with Mittie, there really aren't so many bugs that the overhead of a bug tracking tool is worthwhile.&nbsp; Also, if there's a bug that affects a lot of people, there will be lots of postings to the mailing list about it, which will alert someone capable of fixing the bug that it's a high priority.&nbsp; </DIV>
<DIV>-- Lisa</DIV><BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message from "Dierk Koenig" &lt;dierk.koenig@canoo.com&gt;: -------------- <BR><BR><BR>&gt; I used several bug-tracking tools (Remedy, ClearQuest, Peregrine, <BR>&gt; Bugzilla, Gnats, Jira) and I found them all more difficult to use <BR>&gt; than a mere Wiki Page. <BR>&gt; Sure, when you have to manage a large amount of bugs then you may <BR>&gt; need such a support, but I always felt that entering bugs is <BR>&gt; really complicated. What type of bug is it? What part of the <BR>&gt; system is concerned? What is its priority? and so on <BR>&gt; Most of the time I don't know what to fill in and what happens <BR>&gt; if I fill in nothing or something wrong. <BR>&gt; <BR>&gt; Watching the bug-fixing activities of an open-source project <BR>&gt; can definitely reveal something about the project. <BR>&gt; (Not only how active they are, but also how buggy the <BR>&gt; Software is.) <BR>&gt; <BR>&gt; cheers <BR>&gt; Mittie <BR>&gt; <BR>&gt; &gt; -----Original Message----- <BR>&gt; &gt; From: webtest-admin@lists.canoo.com <BR>&gt; &gt; [mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot <BR>&gt; &gt; Sent: Freitag, 7. Januar 2005 13:47 <BR>&gt; &gt; To: webtest@lists.canoo.com <BR>&gt; &gt; Subject: [Webtest] Re: Bug trackin tool for webtest? <BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; I fear that it's too basic and to complicated: to enter a bug a <BR>&gt; &gt; user needs to create a new page as well as to update the <BR>&gt; &gt; overview page. <BR>&gt; &gt; <BR>&gt; &gt; Furthermore, a bug tracking tool can be used by visitors to see <BR>&gt; &gt; the activity of the project: how many issues opened and <BR>&gt; &gt; fixed in the last x months. <BR>&gt; &gt; <BR>&gt; &gt; Marc. <BR>&gt; &gt; <BR>&gt; &gt; Dierk Koenig wrote: <BR>&gt; &gt; &gt; Hi, <BR>&gt; &gt; &gt; <BR>&gt; &gt; &gt; Yes, having such a tool is sometimes convenient. <BR>&gt; &gt; &gt; <BR>&gt; &gt; &gt; On the other hand, installation, maintenance, etc. again add <BR>&gt; &gt; &gt; to the workload. So it needs to pull its weight. <BR>&gt; &gt; &gt; <BR>&gt; &gt; &gt; Currently we only have few Bugs open in Canoo WebTest and everything <BR>&gt; &gt; &gt; that is not immediately solved and is in jeopardy of being lost <BR>&gt; &gt; &gt; can be added to <BR>&gt; &gt; &gt; http://webtest-community.canoo.com/wiki/space/Bug+Reports <BR>&gt; &gt; &gt; This solution has the additional benefit, that you can google for <BR>&gt; &gt; &gt; it. <BR>&gt; &gt; &gt; <BR>&gt; &gt; &gt; Do you think, we need more than that? <BR>&gt; &gt; &gt; <BR>&gt; &gt; &gt; cheers <BR>&gt; &gt; &gt; Mittie <BR>&gt; &gt; &gt; <BR>&gt; &gt; &gt; <BR>&gt; &gt; &gt;&gt;-----Original Message----- <BR>&gt; &gt; &gt;&gt;From: webtest-admin@lists.canoo.com <BR>&gt; &gt; &gt;&gt;[mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot <BR>&gt; &gt; &gt;&gt;Sent: Freitag, 7. Januar 2005 10:59 <BR>&gt; &gt; &gt;&gt;To: webtest@lists.canoo.com <BR>&gt; &gt; &gt;&gt;Subject: [Webtest] Bug trackin tool for webtest? <BR>&gt; &gt; &gt;&gt; <BR>&gt; &gt; &gt;&gt; <BR>&gt; &gt; &gt;&gt;Hi, <BR>&gt; &gt; &gt;&gt; <BR>&gt; &gt; &gt;&gt;what about making a bug tracking tool available on webtest website? <BR>&gt; &gt; &gt;&gt; <BR>&gt; &gt; &gt;&gt;Currently the problems reported on the mailing list have a high <BR>&gt; &gt; &gt;&gt;risk to be lost if not quickly solved. A special tool (à <BR>&gt; &gt; &gt;&gt;la bugziall, mantis, jira or other) would allow users to query <BR>&gt; &gt; &gt;&gt;existing bug reports, to enter new ones if they find some <BR>&gt; &gt; &gt;&gt;news issues and for developers it would give an overview of the <BR>&gt; &gt; &gt;&gt;current problems. <BR>&gt; &gt; &gt;&gt; <BR>&gt; &gt; &gt;&gt;Marc. <BR>&gt; &gt; &gt;&gt; <BR>&gt; &gt; &gt;&gt;_______________________________________________ <BR>&gt; &gt; &gt;&gt;WebTest mailing list <BR>&gt; &gt; &gt;&gt;WebTest@lists.canoo.com <BR>&gt; &gt; &gt;&gt;http://lists.canoo.com/mailman/listinfo/webtest <BR>&gt; &gt; &gt;&gt; <BR>&gt; &gt; <BR>&gt; &gt; _______________________________________________ <BR>&gt; &gt; WebTest mailing list <BR>&gt; &gt; WebTest@lists.canoo.com <BR>&gt; &gt; http://lists.canoo.com/mailman/listinfo/webtest <BR>&gt; &gt; <BR>&gt; <BR>&gt; _______________________________________________ <BR>&gt; WebTest mailing list <BR>&gt; WebTest@lists.canoo.com <BR>&gt; http://lists.canoo.com/mailman/listinfo/webtest </BLOCKQUOTE>
<!-- END WEBMAIL STATIONERY -->

</body>
</html>

--NextPart_Webmail_9m3u9jl4l_22818_1105112209_0--