umm.. tinderbox is more of a build manager. Not intended to be a tool for
logging and managing regression test results and interface to bugzilla kind
of tools for directly raising bugs..
That was the reason why I was inclined towards test runner (whether one runs
the tests manually or in an automated fashion, it still takes test results
and manages them...)
gopi
-----Original Message-----
From: tes...@li...
[mailto:tes...@li...]On Behalf Of
Benton, Kevin
Sent: Monday, October 10, 2005 8:11 PM
To: Gopi Krishna M; Tes...@li...
Cc: AMIT AGARWAL
Subject: RE: [Testrunner-users] Using test runner for logging nightly (
automated) test results
Seems to me it would be easier to use Tinderbox and modify it to do what
you're looking for with respect to history.
---
Kevin Benton
Perl/Bugzilla Developer, Perforce SCM Administrator
Personal Computing Systems Group
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: tes...@li... [mailto:testrunner-
> use...@li...] On Behalf Of Gopi Krishna M
> Sent: Monday, October 10, 2005 3:50 AM
> To: Tes...@li...
> Cc: AMIT AGARWAL
> Subject: [Testrunner-users] Using test runner for logging nightly (
> automated) test results
>
> Hi..
> I was looking for a tool which can manage test results of nightly
> regressions. By manage, I mean:
> + Dump the results to sql db
> + Give good queries for retrieving data such as
> -- Show all tests which are failing continously for 3-4 runs
> -- Tests which are failing intermittently
> -- If the tool understands s/w versions or branches, then
potentially
> show the progress for a branch (progress made every day)
> etc.
> + Raise bugs (in bugzilla) for a failed test case..
>
> TestRunner seems to be one tool which is close, but it looks more like
a
> "test case management" than "test result management".
> Is anybody using testRunner for the above mentioned application?
>
> Any suggestions on using testrunner for this application or pointers
to
> other tools are welcome.
>
> thanx
> gopi
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,
discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Testrunner-users mailing list
> Tes...@li...
> https://lists.sourceforge.net/lists/listinfo/testrunner-users
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Testrunner-users mailing list
Tes...@li...
https://lists.sourceforge.net/lists/listinfo/testrunner-users
|