testopia-users Mailing List for Testopia (Page 3)
Brought to you by:
efuentetaja,
gregaryh
Menu
▾
▴
testopia-users — Testopia users
You can subscribe to this list here.
| 2004 |
Jan
(5) |
Feb
(2) |
Mar
(1) |
Apr
(6) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
(2) |
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(2) |
| 2006 |
Jan
(4) |
Feb
(1) |
Mar
(5) |
Apr
(4) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(12) |
Dec
(2) |
| 2007 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Melvin L. <mla...@fa...> - 2005-12-22 02:16:32
|
Has anyone had much luck using this function? I am pretty sure this is
how I want it if I want to create check boxes:
=20
Print make_selection_widget('groupname', 'source', "", $multiple =3D 1,
$preferlist =3D 0, $size =3D 6);
=20
I've tried various combinations and have gotten just pull down menus or
multi select boxes.
=20
Any help would be appreciated?
=20
Thank you,
=20
Melvin Laguren
SQA Analyst
Fast Track Systems, Inc.
|
|
From: lynne <lyn...@ca...> - 2005-12-12 19:26:23
|
Is there a way to create and print reports from Test Runner? Thanks, Lynne Brown |
|
From: Gopi K. M <go...@in...> - 2005-10-11 05:58:29
|
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 |
|
From: Benton, K. <kev...@am...> - 2005-10-10 14:41:05
|
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 =20 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 >=20 > 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.. >=20 > 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? >=20 > Any suggestions on using testrunner for this application or pointers to > other tools are welcome. >=20 > thanx > gopi >=20 >=20 >=20 >=20 > ------------------------------------------------------- > 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 |
|
From: Gopi K. M <go...@in...> - 2005-10-10 09:45:08
|
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
|
|
From: Ernest N. <jur...@ju...> - 2005-07-15 21:32:16
|
We've got a plan with around 350 or so test cases connected to it. We've found that when doing a test run with this the system starts to lag horribly, it can take a minute or more for the page to refresh. Has anyone else had similar problems? |
|
From: Scott G. <sg...@in...> - 2005-05-17 19:08:09
|
Hi there, I've installed test runner on bugzilla 2.18, and my SQA group is trying it out and seem to really like it. One thing I'm a bit concerned about is that test runner modifies the bugzilla database schemas directly. Does that mean that when I want to upgrade from bugzilla 2.18 to 2.20 (or 2.18.x point releases in between), that everything is going to break? Also, if I decide I don't want to use test runner anymore, is there a script that would scrub the test runner data and modifications from the bugzilla database? Thanks for your time, Scott -- Scott Garman sgarman at iname dot com |
|
From: Benton, K. <kev...@am...> - 2005-04-21 20:56:33
|
Is there a devel mailing list for Test Runner? I'm interested in offering any assistance I can in getting Test Runner incorporated into Bugzilla 3.0 when it comes out. Is that something this team is interested in? It's very likely that Bugzilla 2.22 will become 3.0. I read on your page (http://www.willowriver.net/TestRunner/tr_testrunner/doc/todo.html) that you're looking for help switching to template technology. It's really easy once you get the hang of it. =20 I would also hope that TestRunner would eventually support the ability to run automated testing as a pre-cursor to manual testing. I'm very heavily involved in developing a LWP platform to test Bugzilla simulating a user and TestRunner not only will help me develop the test cases, but after the test cases are developed, I want to automate as much of the testing as time allows. This will save me tremendous amounts of time in the development/QA cycle and more importantly, help reduce the number of times I would send my software over to my QA team to make sure I'm ready to publish. By reducing the man-hours required to get testing done, the development to release cycle will be cut short dramatically. =20 --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices =20 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. =20 =20 =20 |
|
From: Maciej M. <ma...@xd...> - 2005-04-06 12:25:34
|
malin eek said the following on 2005-02-28 15:09: > 1) Do I have to use Bugzilla when using Bugzilla testrunner? Yes > 2) Is Bugzilla Test runner possible to connect to another Bug tracking > tool? > No |
|
From: malin e. <ma...@ho...> - 2005-02-28 14:10:09
|
1) Do I have to use Bugzilla when using Bugzilla testrunner? 2) Is Bugzilla Test runner possible to connect to another Bug tracking tool? Thank you _________________________________________________________________ Hitta rätt på nätet med MSN Sök http://search.msn.se/ |
|
From: Dush B <dus...@ya...> - 2005-02-15 15:06:52
|
I wanted to try Bugzilla TestRunner and went to the website http://testrunner.citat.se/bugzilla/tr_edittestplans.cgi Well, the only problem that I had with this demo is importing test cases.... I tried with all kind of test cases, but I always got some error message. The first one was: "No file was provided, or it was empty." When I tried couple of days later the message was: "Content-type: text/html Software error: Can't call method "upload" on an undefined value at /var/www/bugzilla/tr_import.cgi line 627, <STDIN> line 107." Is it because this is the demo version, or am I doing something wrong? Thanx Dush ===== Dush __________________________________ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250 |
|
From: eduardo f. <edu...@ho...> - 2004-07-08 21:01:06
|
It is a bug, sorry about that,
If you are using Bugzilla 2.16.*, to fix it: edit tr_buglist_to_plan.cgi,
replace
line 158:
SendSQL("SELECT product_id from bugs where bug_id=$id");
by:
SendSQL("SELECT po.id from bugs b, products po where b.bug_id=$id and
b.product=po.product");
and
line 260:
SendSQL( "SELECT component_id, short_desc from bugs where bug_id=$id" );
by:
SendSQL("SELECT co.id, b.short_desc from bugs b, components co where
b.bug_id=$id and co.value=b.component");
That should do it. I'll fix it more properly on the next version.
Thanks for reporting this problem, I didn't see it,
Ed
>From: "SourceForge.net" <no...@so...>
>To: no...@so...
>Subject: [testrunner - Help] Adding Bugs to Test Plan
>Date: Tue, 06 Jul 2004 15:44:58 -0700
>
>
>Read and respond to this message at:
>https://sourceforge.net/forum/message.php?msg_id=2651761
>By: pyarish
>
>Hello!
>
>I am new to test runner and trying it out for one of our projects. We have
>bugzilla 2.16.5. My problem is when I attempt to add bugs via the "Add
>Bugs
>to Test Plan" link which is on bugzilla query results list, I get the
>following
>error:
>"Adding list of bugs to test plan as test cases
>
>
>You have choosen to add the following bugs to test plan as test cases:
>
>970
>Software error:
>SELECT product_id from bugs where bug_id=970: Unknown column 'product_id'
>in
>'field list' at globals.pl line 276."
>
>Our network guy has not been able to investigate, so I'm asking if anyone
>can
>tell me what the problem is.
>
>Thanks in advance,
>Priscilla
>
>
>______________________________________________________________________
>You are receiving this email because you elected to monitor this forum.
>To stop monitoring this forum, login to SourceForge.net and visit:
>https://sourceforge.net/forum/unmonitor.php?forum_id=331476
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
|
|
From: <ben...@id...> - 2004-05-25 08:10:04
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: <Sha...@ia...> - 2004-04-26 01:10:18
|
I'm using a Chinese localization bugzilla template that the name is = still 'en'. When I'm patching, some fails, e.g.:=20 patching file template/en/default/bug/create/create.html.tmpl Hunk #1 FAILED at 323. 1 out of 1 hunk FAILED -- saving rejects to file = template/en/default/bug/create/create.html.tmpl.rej So what's the meaning of the above patching info? Then I use the 2.17.6 original template 'en' to replace the Chinese one, = the patch is all OK. And test-runner has no software error again. But = where are the HTMLarea icons? I could not find them when I write test = plan or edit test case.=20 Best Regards, Michael -----=AD=EC=A9l=B6l=A5=F3----- =B1H=A5=F3=AA=CC: Fuentetaja, Ed [mailto:ed....@tt...]=20 =B1H=A5=F3=A4=E9=B4=C1: 2004=A6~4=A4=EB23=A4=E9 21:45 =A6=AC=A5=F3=AA=CC: Shao, Michael (=AA=F2=AE=B6 IAC-S); = tes...@li... =A5D=A6=AE: RE: [Testrunner-users] ??: Testrunner-users digest, Vol 1 #8 = - 1 ms g I the problem is that the patching of Bugzilla's files failed for some = weird reason. I understand that you have bugzilla 2.17.6 running. Could you try to = undo the patch (patch -R -bp 1 -i testrunner/patch-2.17.6) (or even = better, restore from your backup) and apply it again? Please report any = problems in the output. You shouldn't have any, Thanks, Ed > -----Original Message----- > From: tes...@li...=20 > [mailto:tes...@li...] On=20 > Behalf Of Sha...@ia... > Sent: Friday, April 23, 2004 12:38 AM > To: tes...@li... > Subject: [Testrunner-users] ??: Testrunner-users digest, Vol=20 > 1 #8 - 1 msg >=20 >=20 > Hi Ed, >=20 > Thanks for your update. I'm using BTR with perl 5.8.0=20 > installed(RedHat9.0). When I add a test case, the software=20 > error occurs: Can't find param named new-case-action-template=20 > at Bugzilla/Config.pm line 124. >=20 > The following is the information when I run ./checksetup.pl.=20 > And before that, I ran the command: patch -bp 1 -i=20 > tr_testrunner/patch-2.17.6 and tr_testrunner/install.pl >=20 > [root@master-dtisqf1e bugzilla]# ./checksetup.pl >=20 > Checking perl modules ... > Checking for AppConfig (v1.52) ok: found v1.52 > Checking for CGI (v2.93) ok: found v3.04 > Checking for Data::Dumper (any) ok: found v2.12 > Checking for Date::Format (v2.21) ok: found v2.22 > Checking for DBI (v1.32) ok: found v1.32 > Checking for DBD::mysql (v2.1010) ok: found v2.9003 > Checking for File::Spec (v0.82) ok: found v0.82 > Checking for File::Temp (any) ok: found v0.14 > Checking for Template (v2.08) ok: found v2.08 > Checking for Text::Wrap (v2001.0131) ok: found v2001.0929 >=20 > The following Perl modules are optional: > Checking for GD (v1.20) ok: found v2.11 > Checking for Chart::Base (v0.99) ok: found v0.99 > Checking for XML::Parser (any) ok: found v2.34 > Checking for GD::Graph (any) ok: found v1.43 > Checking for GD::Text::Align (any) ok: found v1.18 > Checking for PatchReader (any) ok: found v0.9.2 >=20 > Checking user setup ... > Removing existing compiled templates ... > Precompiling templates ... > The following parameters are no longer used in Bugzilla, and=20 > so have been removed from your parameters file and appended=20 > to old-params.txt: cut-cases-texts-in-list,=20 > bug-to-test-case-action, bug-to-test-case-summary,=20 > private-cases-log, cut-cases-texts-limit,=20 > show-bug-status-in-case-log, print-tag-in-case-log,=20 > new-case-action-template, new-case-effect-template,=20 > bug-to-test-case-effect > Checking for MySQL Server (v3.23.41) ok: found v3.23.58 >=20 > Populating duplicates table... > Reminder: Bugzilla now requires version 8.7 or later of sendmail. >=20 >=20 > Best Regards, > Michael (in Shanghai, China.) >=20 > -----=AD=EC=A9l=B6l=A5=F3----- > =B1H=A5=F3=AA=CC: tes...@li...=20 > [mailto:tes...@li...]=20 > =B1H=A5=F3=A4=E9=B4=C1: 2004=A6~4=A4=EB23=A4=E9 11:23 > =A6=AC=A5=F3=AA=CC: tes...@li... > =A5D=A6=AE: Testrunner-users digest, Vol 1 #8 - 1 msg >=20 > Send Testrunner-users mailing list submissions to > tes...@li... >=20 > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/testrunner-users > or, via email, send a message with subject or body 'help' to > tes...@li... >=20 > You can reach the person managing the list at > tes...@li... >=20 > When replying, please edit your Subject line so it is more=20 > specific than "Re: Contents of Testrunner-users digest..." >=20 >=20 > Today's Topics: >=20 > 1. Version 0.5.1 released (Fuentetaja, Ed) >=20 > --__--__-- >=20 > Message: 1 > Date: Thu, 22 Apr 2004 14:17:34 -0500 > From: "Fuentetaja, Ed" <ed....@tt...> > To: <tes...@li...> > Subject: [Testrunner-users] Version 0.5.1 released >=20 > Hi all, >=20 > I was able to arrange a couple of good days of work for Test=20 > Runner. As a result I just released version 0.5.1. It includes: >=20 > * Fixed numerous warnings from the apache's error log. >=20 > * Replaced text areas by HTMLArea, a WYSIWYG html editor. >=20 > * Added the component column to the list of test cases. >=20 > * 'Update test case logs' now only updates confirmed test=20 > cases. =3D20 > * Added automated regresion test scripts from Sytze. >=20 > The HTMLArea is a great "eye-candy" feature. Really easy to=20 > implement and visually compelling. It is an exciting feature,=20 > I hope people like it as much as I do. >=20 > I got several weird problems reported lately. I'm pretty sure=20 > they are all related to Perl 5.8. I use Perl 5.6.1 for=20 > development and I haven't been able to test Test Runner on=20 > any other versions. Thanks to Mr. Johnston's help I could fix=20 > some of the problems. Apparently many of the warnings that I=20 > had in Apache's error log are not warnings anymore on Perl=20 > 5.8, but errors. That's why I decided to finally clean up all=20 > those nasty warnings, I had a million. >=20 > If anybody tries Test Runner 0.5.1 with Perl 5.8, please report. >=20 > I'll be relocating during the next week and I won't be=20 > available. The web site www.willowriver.net might go down at=20 > some point. >=20 > Thanks, >=20 > Ed >=20 >=20 >=20 > --__--__-- >=20 > _______________________________________________ > Testrunner-users mailing list Tes...@li... > https://lists.sourceforge.net/lists/listinfo/testrunner-users >=20 >=20 > End of Testrunner-users Digest >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: The Robotic Monkeys at=20 > ThinkGeek For a limited time only, get FREE Ground shipping=20 > on all orders of $35 or more. Hurry up and shop folks, this=20 > offer expires April 30th!=20 > http://www.thinkgeek.com/freeshipping/?cpg=12297 > _______________________________________________ > Testrunner-users mailing list Tes...@li... > https://lists.sourceforge.net/lists/listinfo/testrunner-users >=20 |
|
From: Fuentetaja, E. <ed....@tt...> - 2004-04-23 13:45:06
|
I the problem is that the patching of Bugzilla's files failed for some weird reason. I understand that you have bugzilla 2.17.6 running. Could you try to undo the patch (patch -R -bp 1 -i testrunner/patch-2.17.6) (or even better, restore from your backup) and apply it again? Please report any problems in the output. You shouldn't have any, Thanks, Ed > -----Original Message----- > From: tes...@li... > [mailto:tes...@li...] On > Behalf Of Sha...@ia... > Sent: Friday, April 23, 2004 12:38 AM > To: tes...@li... > Subject: [Testrunner-users] ??: Testrunner-users digest, Vol > 1 #8 - 1 msg > > > Hi Ed, > > Thanks for your update. I'm using BTR with perl 5.8.0 > installed(RedHat9.0). When I add a test case, the software > error occurs: Can't find param named new-case-action-template > at Bugzilla/Config.pm line 124. > > The following is the information when I run ./checksetup.pl. > And before that, I ran the command: patch -bp 1 -i > tr_testrunner/patch-2.17.6 and tr_testrunner/install.pl > > [root@master-dtisqf1e bugzilla]# ./checksetup.pl > > Checking perl modules ... > Checking for AppConfig (v1.52) ok: found v1.52 > Checking for CGI (v2.93) ok: found v3.04 > Checking for Data::Dumper (any) ok: found v2.12 > Checking for Date::Format (v2.21) ok: found v2.22 > Checking for DBI (v1.32) ok: found v1.32 > Checking for DBD::mysql (v2.1010) ok: found v2.9003 > Checking for File::Spec (v0.82) ok: found v0.82 > Checking for File::Temp (any) ok: found v0.14 > Checking for Template (v2.08) ok: found v2.08 > Checking for Text::Wrap (v2001.0131) ok: found v2001.0929 > > The following Perl modules are optional: > Checking for GD (v1.20) ok: found v2.11 > Checking for Chart::Base (v0.99) ok: found v0.99 > Checking for XML::Parser (any) ok: found v2.34 > Checking for GD::Graph (any) ok: found v1.43 > Checking for GD::Text::Align (any) ok: found v1.18 > Checking for PatchReader (any) ok: found v0.9.2 > > Checking user setup ... > Removing existing compiled templates ... > Precompiling templates ... > The following parameters are no longer used in Bugzilla, and > so have been removed from your parameters file and appended > to old-params.txt: cut-cases-texts-in-list, > bug-to-test-case-action, bug-to-test-case-summary, > private-cases-log, cut-cases-texts-limit, > show-bug-status-in-case-log, print-tag-in-case-log, > new-case-action-template, new-case-effect-template, > bug-to-test-case-effect > Checking for MySQL Server (v3.23.41) ok: found v3.23.58 > > Populating duplicates table... > Reminder: Bugzilla now requires version 8.7 or later of sendmail. > > > Best Regards, > Michael (in Shanghai, China.) > > -----原始郵件----- > 寄件者: tes...@li... > [mailto:tes...@li...] > 寄件日期: 2004年4月23日 11:23 > 收件者: tes...@li... > 主旨: Testrunner-users digest, Vol 1 #8 - 1 msg > > Send Testrunner-users mailing list submissions to > tes...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/testrunner-users > or, via email, send a message with subject or body 'help' to > tes...@li... > > You can reach the person managing the list at > tes...@li... > > When replying, please edit your Subject line so it is more > specific than "Re: Contents of Testrunner-users digest..." > > > Today's Topics: > > 1. Version 0.5.1 released (Fuentetaja, Ed) > > --__--__-- > > Message: 1 > Date: Thu, 22 Apr 2004 14:17:34 -0500 > From: "Fuentetaja, Ed" <ed....@tt...> > To: <tes...@li...> > Subject: [Testrunner-users] Version 0.5.1 released > > Hi all, > > I was able to arrange a couple of good days of work for Test > Runner. As a result I just released version 0.5.1. It includes: > > * Fixed numerous warnings from the apache's error log. > > * Replaced text areas by HTMLArea, a WYSIWYG html editor. > > * Added the component column to the list of test cases. > > * 'Update test case logs' now only updates confirmed test > cases. =20 > * Added automated regresion test scripts from Sytze. > > The HTMLArea is a great "eye-candy" feature. Really easy to > implement and visually compelling. It is an exciting feature, > I hope people like it as much as I do. > > I got several weird problems reported lately. I'm pretty sure > they are all related to Perl 5.8. I use Perl 5.6.1 for > development and I haven't been able to test Test Runner on > any other versions. Thanks to Mr. Johnston's help I could fix > some of the problems. Apparently many of the warnings that I > had in Apache's error log are not warnings anymore on Perl > 5.8, but errors. That's why I decided to finally clean up all > those nasty warnings, I had a million. > > If anybody tries Test Runner 0.5.1 with Perl 5.8, please report. > > I'll be relocating during the next week and I won't be > available. The web site www.willowriver.net might go down at > some point. > > Thanks, > > Ed > > > > --__--__-- > > _______________________________________________ > Testrunner-users mailing list Tes...@li... > https://lists.sourceforge.net/lists/listinfo/testrunner-users > > > End of Testrunner-users Digest > > > > ------------------------------------------------------- > This SF.net email is sponsored by: The Robotic Monkeys at > ThinkGeek For a limited time only, get FREE Ground shipping > on all orders of $35 or more. Hurry up and shop folks, this > offer expires April 30th! > http://www.thinkgeek.com/freeshipping/?cpg297 > _______________________________________________ > Testrunner-users mailing list Tes...@li... > https://lists.sourceforge.net/lists/listinfo/testrunner-users > |
|
From: <Sha...@ia...> - 2004-04-23 05:38:14
|
Hi Ed, Thanks for your update. I'm using BTR with perl 5.8.0 = installed(RedHat9.0). When I add a test case, the software error occurs: = Can't find param named new-case-action-template at Bugzilla/Config.pm = line 124. The following is the information when I run ./checksetup.pl. And before = that, I ran the command: patch -bp 1 -i tr_testrunner/patch-2.17.6 and = tr_testrunner/install.pl [root@master-dtisqf1e bugzilla]# ./checksetup.pl Checking perl modules ... Checking for AppConfig (v1.52) ok: found v1.52 Checking for CGI (v2.93) ok: found v3.04 Checking for Data::Dumper (any) ok: found v2.12 Checking for Date::Format (v2.21) ok: found v2.22 Checking for DBI (v1.32) ok: found v1.32 Checking for DBD::mysql (v2.1010) ok: found v2.9003 Checking for File::Spec (v0.82) ok: found v0.82 Checking for File::Temp (any) ok: found v0.14 Checking for Template (v2.08) ok: found v2.08 Checking for Text::Wrap (v2001.0131) ok: found v2001.0929 The following Perl modules are optional: Checking for GD (v1.20) ok: found v2.11 Checking for Chart::Base (v0.99) ok: found v0.99 Checking for XML::Parser (any) ok: found v2.34 Checking for GD::Graph (any) ok: found v1.43 Checking for GD::Text::Align (any) ok: found v1.18 Checking for PatchReader (any) ok: found v0.9.2 Checking user setup ... Removing existing compiled templates ... Precompiling templates ... The following parameters are no longer used in Bugzilla, and so have = been removed from your parameters file and appended to old-params.txt: cut-cases-texts-in-list, bug-to-test-case-action, = bug-to-test-case-summary, private-cases-log, cut-cases-texts-limit, = show-bug-status-in-case-log, print-tag-in-case-log, = new-case-action-template, new-case-effect-template, = bug-to-test-case-effect Checking for MySQL Server (v3.23.41) ok: found v3.23.58 Populating duplicates table... Reminder: Bugzilla now requires version 8.7 or later of sendmail. Best Regards, Michael (in Shanghai, China.) -----=AD=EC=A9l=B6l=A5=F3----- =B1H=A5=F3=AA=CC: tes...@li... = [mailto:tes...@li...]=20 =B1H=A5=F3=A4=E9=B4=C1: 2004=A6~4=A4=EB23=A4=E9 11:23 =A6=AC=A5=F3=AA=CC: tes...@li... =A5D=A6=AE: Testrunner-users digest, Vol 1 #8 - 1 msg Send Testrunner-users mailing list submissions to tes...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/testrunner-users or, via email, send a message with subject or body 'help' to tes...@li... You can reach the person managing the list at tes...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Testrunner-users digest..." Today's Topics: 1. Version 0.5.1 released (Fuentetaja, Ed) --__--__-- Message: 1 Date: Thu, 22 Apr 2004 14:17:34 -0500 From: "Fuentetaja, Ed" <ed....@tt...> To: <tes...@li...> Subject: [Testrunner-users] Version 0.5.1 released Hi all, I was able to arrange a couple of good days of work for Test Runner. As a result I just released version 0.5.1. It includes: * Fixed numerous warnings from the apache's error log. * Replaced text areas by HTMLArea, a WYSIWYG html editor. * Added the component column to the list of test cases. * 'Update test case logs' now only updates confirmed test cases. =3D20 * Added automated regresion test scripts from Sytze. The HTMLArea is a great "eye-candy" feature. Really easy to implement and visually compelling. It is an exciting feature, I hope people like it as much as I do. I got several weird problems reported lately. I'm pretty sure they are all related to Perl 5.8. I use Perl 5.6.1 for development and I haven't been able to test Test Runner on any other versions. Thanks to Mr. Johnston's help I could fix some of the problems. Apparently many of the warnings that I had in Apache's error log are not warnings anymore on Perl 5.8, but errors. That's why I decided to finally clean up all those nasty warnings, I had a million. If anybody tries Test Runner 0.5.1 with Perl 5.8, please report. I'll be relocating during the next week and I won't be available. The web site www.willowriver.net might go down at some point. Thanks, Ed --__--__-- _______________________________________________ Testrunner-users mailing list Tes...@li... https://lists.sourceforge.net/lists/listinfo/testrunner-users End of Testrunner-users Digest |
|
From: Fuentetaja, E. <ed....@tt...> - 2004-04-22 19:17:37
|
Hi all, I was able to arrange a couple of good days of work for Test Runner. As a result I just released version 0.5.1. It includes: * Fixed numerous warnings from the apache's error log. * Replaced text areas by HTMLArea, a WYSIWYG html editor. * Added the component column to the list of test cases. * 'Update test case logs' now only updates confirmed test cases. =20 * Added automated regresion test scripts from Sytze. The HTMLArea is a great "eye-candy" feature. Really easy to implement and visually compelling. It is an exciting feature, I hope people like it as much as I do. I got several weird problems reported lately. I'm pretty sure they are all related to Perl 5.8. I use Perl 5.6.1 for development and I haven't been able to test Test Runner on any other versions. Thanks to Mr. Johnston's help I could fix some of the problems. Apparently many of the warnings that I had in Apache's error log are not warnings anymore on Perl 5.8, but errors. That's why I decided to finally clean up all those nasty warnings, I had a million. If anybody tries Test Runner 0.5.1 with Perl 5.8, please report. I'll be relocating during the next week and I won't be available. The web site www.willowriver.net might go down at some point. Thanks, Ed |
|
From: Fuentetaja, E. <ed....@tt...> - 2004-04-07 19:37:27
|
Weird. There are no problems reported so far on edit test cases. Have you seen the web server logs? Is anything there? I'm guess that you have version 5.0 and the file that you comment the Status line is tr_testcase_form.pl. Has this happened since the very first time that you installed Test Runner or is a new condition? Sorry if I'm not helping a lot. I need more information. Ed > -----Original Message----- > From: tes...@li...=20 > [mailto:tes...@li...] On=20 > Behalf Of Keith B. Johnston > Sent: Tuesday, April 06, 2004 1:14 PM > To: tes...@li... > Subject: [Testrunner-users] Hang in editing test case >=20 >=20 > I can't seem to edit test cases. The UI hangs at the=20 > "Status:" field (that is the last thing printed). I=20 > commented out that line in the cgi and then it hung at "Tags". >=20 > I tried the fix in one of the test runner rocks (changing the=20 > join to use quotes instead of \). This did nothing to help. >=20 > Keith >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President=20 > and CEO of GenToo technologies. Learn everything from=20 > fundamentals to system=20 > = administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck > _______________________________________________ > Testrunner-users mailing list Tes...@li... > https://lists.sourceforge.net/lists/listinfo/testrunner-users >=20 |
|
From: Keith B. J. <kjo...@ro...> - 2004-04-06 18:14:41
|
I can't seem to edit test cases. The UI hangs at the "Status:" field (that is the last thing printed). I commented out that line in the cgi and then it hung at "Tags". I tried the fix in one of the test runner rocks (changing the join to use quotes instead of \). This did nothing to help. Keith |
|
From: Fuentetaja, E. <ed....@tt...> - 2004-03-12 20:15:07
|
Hi Just let this list know that I'm working on replacing the <textarea> controls in Test Runner by HTMLArea. HTMLArea 3.0 is an amazing WYSIWYG html control that works on IE & Mozilla and is javascript based, so there is nothing to install. This is going to be a great added value for Test Runner and, hopefully, easy to implement. I would also like to incorporate to the release the scripts that Sytze made, really handy for the automation of test run data input. I have experimented and increased demand of Test Runner since Keith Zambelich linked it on http://www.sqa-test.com/toolpage.html. Anyway, numbers are still low :( If you must know I have a grand total number of 141 downloads for Test Runner. Once in a while I got some possitive comments, but I rather have bugs reported. A bug means that people really care about the product. At some point I would like to incorporate the UI that Myk made to the mainstream release. Myk made a really good job, a better, simplified interface for testers. Thanks, Ed Fuentetaja |
|
From: Fuentetaja, E. <ed....@tt...> - 2004-02-19 14:31:48
|
Well, the idea with the installation is that you copy the testrunner_0_5.tar.gz to the same directory where you have Bugzilla running, then you uncompress it and continue with the rest of the instructions. The patch should run fine as long as your Bugzilla is not heavily customized. And you don't need to configure the .sql and install.pl scripts. The scripts can find your Bugzilla installation because you are running them from the Bugzilla directory. Please let me know how any problems you might find. Don't forget to make backups of the Bugzilla folder and the database, so if there is any mishaps you can go back to square one safely. Thanks, Ed Fuentetaja > -----Original Message----- > From: tes...@li...=20 > [mailto:tes...@li...] On=20 > Behalf Of Neil Wills > Sent: Wednesday, February 18, 2004 11:39 PM > To: tes...@li... > Subject: [Testrunner-users] Installing Testrunner >=20 >=20 > Hi there, >=20 > =20 >=20 > I am currently installing TestRunner with our implementation=20 > of Bugzilla to use as our test case management tool. >=20 > =20 >=20 > Can you confirm that the following files have to be=20 > configured for our default implementation of bugzilla: >=20 > =20 >=20 > - patch-2.16.3 >=20 > - create_db_0_4_5.sql >=20 > - install.pl >=20 > =20 >=20 > From what I can infer these files qill require updating to=20 > point to our installation of bugzilla...=20 >=20 >=20 |
|
From: Neil W. <nei...@ub...> - 2004-02-19 05:44:40
|
Hi there, =20 I am currently installing TestRunner with our implementation of Bugzilla to use as our test case management tool. =20 Can you confirm that the following files have to be configured for our default implementation of bugzilla: =20 - patch-2.16.3 - create_db_0_4_5.sql - install.pl =20 From what I can infer these files qill require updating to point to our installation of bugzilla...=20 |
|
From: Fuentetaja, E. <ed....@tt...> - 2004-01-27 16:45:11
|
I just released new version, 0.5. Although this version doesn't include any new functionality with respect to v 0.4.5, this is a major milestone for Test Runner, I think, because this is the first version than works with both Bugzilla 2.16* and 2.17*. This is going to simplify greatly maintenance and bug fixing. It also offers the possibility to those users running BTR 0.3 to upgrade to this version and benefit from user interface improvements introduced in versions 0.4. I included several scripts that detect the version of Bugzilla/BTR running and upgrade the database accordingly. To make Test Runner work on a Bugzilla 2.16* database I'm adding 'id' columns to both products and components tables. This should be harmless. Bugzilla 2.16 should ignore this new fields. Test Runner uses them to join with every other table. The upgrade script should migrate the BTR 0.3 database to 0.5 without any loss of information. I've spent a great deal of time testing the installation/upgrade procedures and they seem to be working fine. Anyway, I cannot emphasized strongly enough the importance of making a backup of the Bugzilla's database and directories, in case that bad things happen during the installation. Thanks, Ed Fuentetaja |
|
From: Fuentetaja, E. <ed....@tt...> - 2004-01-23 15:52:35
|
After releasing version 0.4.5 I'm currently working on facilitating a migration path from version 0.3 (bugzilla 2.16) to 0.4.5 (bugzilla 2.17) I got a patch working for version 2.16.3. But the biggest obstacle is the that there are some changes in the bugzilla's db that affect Test Runner: - Table components: version 2.17 added a new column ID, and VALUE was renamed to NAME - Table products: almost the same: new column ID and PRODUCT renamed to NAME My idea is to run a sql patch on 2.16 that adds ID columns to both tables. Type will be autoincrement, so even if Bugzilla 2.16 doesn't know about those columns, they will be automatically populated for new products. I think it's going to be safe. I won't rename the other two columns, I want to minimize patching Bugzilla's code. Rather than that, I'll detect the current version of the DB and use one name or the other on the Test Runner queries. I got a working version (modified code of 0.4.5 running on a Bugzilla 2.16.3) I just need to write some code to detect the version and change the content of the couple of global variables that contain the name of the columns, do more testing with both Bugzilla 2.16 and 2.17 and I'll be ready to go. Testing so far seems to be OK. I'm very excited because there are some people using Bugzilla 2.16 and if I can provide them with the advantages of Test Runner 0.4.5 is going to be great. And I'll only have one single version to maintain. Ed |
|
From: Vijayan.R.A.Reddy <vij...@ta...> - 2004-01-19 13:40:33
|
How do I subscribe to this list ? Thanks, Vijayan. |
1 message has been excluded from this view by a project administrator.
