Closed Bug 632392 Opened 15 years ago Closed 15 years ago

Reports fail for everything besides Test Plans

Categories

(Testopia :: Reports, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jalphonso, Assigned: gregaryh)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9 Build Identifier: 2.4 The Ajax symbol keeps spinning, after clicking on Reports-->Tabular Reports-->Test Case, Test Run, Test Results. Works for Test Plans. Noticed from the logs there are errors received when clicking on these other tabs that fail. [error] [client IP] Premature end of script headers: tr_query.cgi, referer: http://IP/bugzilla/tr_show_product.cgi Reproducible: Always Steps to Reproduce: 1.Click Product Dashboard 2.Select a Product 3.Click Reports-->Tabular Reports-->Test Case, Test Run, Test Results. 4.Fails for all but Test Plans Actual Results: Ajax symbol keeps spinning. Error as mentioned in summary appears in error.log Expected Results: Should bring up a dialog to build a report.
I am having similar problem. Same way you go to the Dashboard, then click Reports or Search, either way same. Selecting Test Plan works, but not Test Case, Test Run or Test Results. IE8 script debugger pointing out in Testopia.Search.fillInForm = function... in the file testopia.all.ycomp.js, E is null, where getting it by document.getElementById(C + "_search_form"). At this point, document is empty and nothing to get. Then go though the endless loop of "for" using E.lenght where object E is null.
I found a similar bug report for this. That is 591065. I applied it on to my Testopia 2.4 + bugzilla 3.6.4 and search and report were started working for Runs and Results, but not Test Case search or report. I do not really need case search at this point. So I am happy with the fix for 591065. You should look at it.
Thanks alot! This fixed my problem.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.