Query Metrics report

LATEST Official version.
Questions and discussions - NO ISSUES
FOR ISSUES => http://mantis.testlink.org

Moderators: Amaradana, TurboPT, TL Developers

Post Reply
deepakarora79
TestLink user
Posts: 4
Joined: Thu Aug 13, 2009 3:07 pm

Query Metrics report

Post by deepakarora79 »

Hi,

I just installed 1.9 Beta 4 version on a windows system and noticed that when I'm generating the Query Metrics report, it is not showing any data in the "Bugs" column. Rest all the columns are fine.
I do've a successful integration of Bugzill and TestLink as I can enter bugs on the execution page.

Any idea if it's a know issue? Is there something I can do to fix it?

Not sure if it's related but I can see below messages in the log:

[10/May/5 21:00:07][WARNING][4d8tlfs9r6c9f88j2uim1dl2v7][GUI]
E_NOTICE
Undefined property: newResults::$totalbsForPlan - in C:\wamp\www\Testlink\lib\functions\results.class.php - Line 720
[10/May/5 21:00:07][WARNING][4d8tlfs9r6c9f88j2uim1dl2v7][GUI]
E_WARNING
Invalid argument supplied for foreach() - in C:\wamp\www\Testlink\lib\results\resultsMoreBuilds_buildReport.php - Line 162

-Rgds
Deepak
deepakarora79
TestLink user
Posts: 4
Joined: Thu Aug 13, 2009 3:07 pm

Re: Query Metrics report

Post by deepakarora79 »

Ok I think I found one problem that there is a typo at line 720 in results.class.php. The name should "$totalsForPlan" whereas it is "$totalbsForPlan".
I removed the typo but still I can't see any bugs in the bugs column..
sreedhar
TestLink user
Posts: 2
Joined: Fri May 21, 2010 2:25 pm

Re: Query Metrics report

Post by sreedhar »

Did you find any solution? I am also facing the same problem ( we integrated with JIRA), the bug details are not displaying in Query Metrics report.
Yhn
TestLink user
Posts: 1
Joined: Thu Jun 17, 2010 10:43 am

Re: Query Metrics report

Post by Yhn »

We've also runned across this issue when trying to integrate with Mantis (to check for other integration options).

The workaround I found for 'fixing' this was to add the following to lib/results/resultsMoreBuilds_buildReport.php after require_once('displayMgr.php'); and before
testlinkInitPage($db,false,false,"checkRights"); :

Code: Select all

require_once(TL_ABS_PATH. 'lib' . DIRECTORY_SEPARATOR . 'bugtracking' . DIRECTORY_SEPARATOR . 'int_bugtracking.php');
This would initiate the bug tracking system for that page; and allow it to see the bugs.

Edit: after looking through the bug tracker for testlink I found the following: http://mantis.testlink.org/view.php?id=3438
Ok... so after a little bit of debugging/analysis, I was able to resolve this issue. I had to add below code just after the comments section to lib/functions/results.class.php.

if (config_get('interface_bugs') != 'NO')
{
require_once(TL_ABS_PATH. 'lib' . DIRECTORY_SEPARATOR . 'bugtracking' .
DIRECTORY_SEPARATOR . 'int_bugtracking.php');
}

Now the query metrics report is working fine and I can see all the bugs I logged against the respective test cases.
This would work for all reports using the bug tracker functionality :)
sreedhar
TestLink user
Posts: 2
Joined: Fri May 21, 2010 2:25 pm

Re: Query Metrics report

Post by sreedhar »

Thank you!
testlinkiscool
Advanced user
Posts: 24
Joined: Mon May 24, 2010 2:24 am

Re: Query Metrics report

Post by testlinkiscool »

Thank you!
radhoo
Advanced user
Posts: 19
Joined: Wed Jul 28, 2010 12:00 pm
Contact:

Re: Query Metrics report

Post by radhoo »

Hello Yhn,

I tried both solutions but no luck. I am using bugzilla too. I have to do something after editing the files ?

Thanks.
Post Reply