User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:126.96.36.199) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729) Build Identifier: http://xxx/tr_query.cgi?current_tab=case returns a: 500 Error. Apache log shows only: [Thu Aug 26 07:58:05 2010] [error] [client 192.168.42.72] Premature end of script headers: tr_query.cgi, referer: http://xxx/tr_show_product.cgi?search=1 Same story goes for: http://xxx/tr_query.cgi?current_tab=run http://xxx/tr_query.cgi?current_tab=case_run Reproducible: Always Steps to Reproduce: 1. Login as an user; 2. Click on Testopia's "Search" link; Actual Results: An empty page shows up in Firefox. Expected Results: Test case search page expected.
this was introduced by revision 640 firstname.lastname@example.org moving $class->SUPER::new(@_); in TestRun.pm's constructor to before the empty object creation stuff breaks things. As there was a fair bit of this type of change in that revision, I suspect there are probably more conceptually-related problems in the other classes, but it certainly shows up for the Test Run Report.
Actually the problem I pointed out was only for the run and case_run tabs, for the case tab, just changing how the object constructor is called in tr_query.cgi might be the most apropriate solution...that's what I'm going with anyway. I'll attach a couple of patches.
That works. Actually I ended up monkeypatching the run and case_run tabs, but I think your patch is more educated :) Any chances to merge it into the trunk ?
Anyone knows when the fix for this bug will be incorporated to a version of Bugzilla and/or Testopia?
I'm seeing this problem as well.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I have been seeing similar problem with search and report. I can run the Plan search or report, but not others. After found this bug report and fix, I applied this fix and both Run and Case-Run or Results search and report worked, but not case as mentioned Jamie's comments. Thank you Jamie for this. I would love to see the case report and search working soon.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
This changes in the attachment worked for me!
You need to log in before you can comment on or make changes to this bug.