H!
I tested with Bugzilla 3.4.8 on Apache 2.2 and Perl 5.10.0. Problem #2 does not occur with that version, however Testcomplete still does not find any projects (Problem #3).
Before setting up a test environment, I want to try to debug issue #3. I had a look at the traffic between Testcomplete and Bugzilla with a packet sniffer:
* TC accesses /query.cgi?GoAheadAndLogIn=1&Bugzilla_restrictlogin=&Bugzilla_password=password&Bugzilla_login=email@address using POST. "Password" and "email@address" being the data that was entered into the connection manager in TC. The specified account is an administrator.
* Bugzilla accepts the login, sends back a cookie and the "Find a Specific Bug" page (/query.cgi)
* TC then requests /query.cgi?format=advanced&js=1&rememberjs=1 using the cookie from above.
* Bugzilla replies with the "Advanced Search" page. I attached the HTML code of this reply.
* Then TC trys to access /relogin.cgi, without supplying any action parameter, so Bugzilla redirects to /index.cgi with the HTTP code 302
* As a last step, TC calls /index.cgi and Bugzilla sends back the requested index page. TC then reports that it made a successful connection but could not find any top-level projects.
Now my question is: What exactly is Testcomplete looking for on the Advanced Search page? I guess it's parsing the HTML code and by "top-level projects" the Bugzilla products are meant. However I added products, components and versions to the Bugzilla installation, yet Testcomplete seems unable to recognize them.