Testopia -unresponsive script-

[Cindi Adams]

Testopia,

Running on centos5.7
Bugzilla 4.2.4

1)I am a Nubian to this and I am having trouble. (I do have the manual) I have cut and pasted a test plan to testopia. Now when I try to access it this plan it gives the following error and I am not sure why:

Warning: Unresponsive script
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
Script: https://in.aframedigital.com/bugzilla/extensions/Testopia/extjs/ext-all.js:7

When I select continue continue it did populate the test plan.
However if I made and Edit and select Submit it gives me the following System error:
Request-URI Too Large

The requested URL's length exceeds the capacity limit for this server.
Apache/2.2.3 (CentOS) Server at in.aframedigital.com Port 443

—


Other questions:

2)Is there a demo site with a demo Testopia running. I am having a hard time understanding the layout and maybe seeing one that is a demo would help me.

3) From Product Dashboard there is a Classifications Column, underneath is Unclassified and I am not sure why but I am assuming this is from the Bugzilla products category settings. All our products are listed.

Thank you,
Cindi Adams

[Gregary Hendricks]

You can see a demo at http://landfill.mozilla.org/testopia

The unresponsive script issue is often problematic with IE. Which browser
are you using? I would recommend trying it with Firefox and see if you
still see the message.

Usually, the URI too long comes when some large amount of data is trying to
be sent via a GET instead of a POST. I am not sure how you would get this
on the test plan page. I assume you are pasting this into the body of the
test plan. Do you get this when you save it initially or just on update?

The classifications is an optional level that can be turned on in Bugzilla
settings. We needed a root level for products and Unclassified serves this
purpose. If you add classifications to bugzilla, you will see them in the
product dashboard.

++Greg

> _______________________________________________
> support-webtools mailing list
> support-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-webtools
>

[Ralph Siemsen]

On Tue, Feb 12, 2013 at 10:48:10PM -0700, Gregary Hendricks wrote:
>
> Usually, the URI too long comes when some large amount of data is trying to
> be sent via a GET instead of a POST. I am not sure how you would get this
> on the test plan page. I assume you are pasting this into the body of the
> test plan. Do you get this when you save it initially or just on update?

Hi Greg,

Some of my users also run into the URI too long issue. It occurs when
editing details of a test case via the "Test Runs" (tr_show_run.cgi).
If you paste too much text, or use a lot of HTML tables and/or formatting,
the limits for a GET request are easily exceeded.

It works fine when editing via the tr_show_case.cgi script, but for the same
test case, it fails via the tr_show_run.cgi script.

I've see this both with Testopia 2.2 on Bugzilla 3.2.3, and also with
Testopia 2.5 on Bugzilla 4.2.4.

-Ralph

[rfs...@gmail.com]

On Wednesday, February 13, 2013 9:05:27 AM UTC-5, Ralph Siemsen wrote:

> Some of my users also run into the URI too long issue. It occurs when
> editing details of a test case via the "Test Runs" (tr_show_run.cgi).
> If you paste too much text, or use a lot of HTML tables and/or formatting,
> the limits for a GET request are easily exceeded.

I finally dug into the code and figured out the cause of this particular problem. The Test Case Runs page (tr_show_run.cgi) indeed uses GET instead of POST to update. The following patch fixes the issue:

diff a/testopia/js/caserun.js b/testopia/js/caserun.js
--- a/testopia/js/caserun.js
+++ b/testopia/js/caserun.js
@@ -1111,6 +1111,7 @@ CaseRun = function(){
params.case_id = Ext.getCmp('caserun_grid').getSelectionModel().getSelected().get('case_id');
params.action = 'update_doc';
testopia_form.submit({
+ method: 'POST',
url: 'tr_process_case.cgi',
params: params,
success: function(){

It's also necessary to regenerate the testopia.all.js and/or testopia.all.ycomp.js files, since these are used by default on production server, rather than the individual *.js files.

Thanks,
-Ralph