congrats on behalf of Test Runner

[Benton, Kevin]

Albert - Test Runner is not a tinderbox.  Test Runner is a documentation
facility that helps validation and QA teams go through the process of
testing.  Test Runner and Tinderbox can work well together, but their
focus is about as far apart as the sun and the moon.  One does testing
and provides results it gets, the other records how to do testing and
the results people got when they did the testing.

Should there be a Tinderbox / Test Runner interface?  Probably :)

Ed - I suggest you consider changing the name of Test Runner to Test
Case Planner or Test Case Manager (or something similar).  It may
confuse existing users a little for a while, but I think it will prevent
more confusion in the long run.

For those interested in learning more about Test Runner, you can go to
the web site at

http://sourceforge.net/projects/testrunner/

---
Kevin Benton
Perl/Bugzilla Developer, Perforce SCM Administrator
Advanced Micro Devices
 
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.

> -----Original Message-----
> From: developers-owner at bugzilla.org
[mailto:developers-owner at bugzilla.org]
> On Behalf Of Ed
> Sent: Thursday, September 29, 2005 1:18 PM
> To: developers at bugzilla.org
> Subject: Re: congrats on behalf of Test Runner
> 
> Yes, I do read it. It's just that I sent my initial post from the
> wrong email account. Sorry.
> 
> Asking to Albert, in a nutshell Test Runner is a test case management
> tool that organizes test cases. A test case is a set of steps that
> define some actions over the "thing" you are testing and the espected
> results. Some tests are automated others are manual. This might be the
> root of the confusion because Test Runner actually doesn't run tests!
> Test cases are organized into test plans. You can "run" a test plan,
> meaning that your testers are going to exercise its test cases and
> record the outcome, for a specific combination of platform, OS, etc.
> Since everything gets recorded you or the product manager of the
> "thing" can get a good idea of its quality level and make decisions.
> There are many synergies between Bugzilla and Test Runner since when a
> test case "fails" means that a bug has been discovered and you
> probably would like to record and manage that bug.
> 
> I believe TinderBox is a different beast with a different mission.
> 
> Hope this clarifies,
> 
>     Ed
> 
> 
> On 9/29/05, David Miller <justdave at bugzilla.org> wrote:
> > Albert Ting wrote:
> >
> > >    This looks interesting.  Pardon my ignorance, but can you
explain
> the
> > >    difference between Test Runner and TinderBox.  I think both
offers
> > >    automated regression testing?
> > >
> > >    Been interested in integrating regression testing with Bugzilla
but
> > >    haven't had time to setup a good infrastructure for this.
> >
> > I don't think Ed actually reads this list.  I had to clear his post
from
> > the moderator queue when he posted it.
> >
> > --
> > Dave Miller
http://www.justdave.net/
> > System Administrator, Mozilla Foundation
http://www.mozilla.org/
> > Project Leader, Bugzilla Bug Tracking System
http://www.bugzilla.org/
> > -
> > To view or change your list settings, click here:
> > <http://bugzilla.org/cgi-bin/mj_wwwusr?user=ed.fuentetaja@gmail.com>
> >
> 
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=kevin.benton@amd.com>