MantisBT - TestLink
View Issue Details
0005401TestLinkReportspublic2012-12-07 09:302013-05-30 19:40
mbar 
fman 
lowminoralways
closedfixed 
1.9.4 (2012 Q3 - bug fixing) 
1.9.6 (2013 Q1 - bug fixing) 
MySQL
READY FOR TESTING
0005401: Closed redmine issues are not considered Resolved in TestLink
This happened lately, like within last 2 weeks. I'm using latest 1.9.4 QA code from git (5193 issue) downloaded on 03.12.2012. Today I noticed that bug reports in Redmine that are set to Closed are no longer considered Resolved by TestLink. Please see screenshot.

That report was OK in November.
Bugs per Test Case report, one has to have some TCs with connected redmine issues with status Closed.
report by tester per build
has duplicate 0005449closed fman [Bugzilla] Bugs closed, verified, resolved not counted in correct way on report Bugs for Test Case 
related to 0005417closed fman Closed/Resolved issues are not considered Resolved AND THEN NOT COUNTED in TestLink 
child of 0005406closed fman Availables hot-fixes for 1.9.5 & How To get full fixed package from gitorious 
png tl_bugs_per_tc.png (36,411) 2012-12-07 09:30
http://mantis.testlink.org/file_download.php?file_id=3032&type=bug
png

png tl_bugs_per_tc2.png (51,031) 2012-12-10 09:49
http://mantis.testlink.org/file_download.php?file_id=3038&type=bug
png

png issue-5401.png (34,451) 2012-12-10 19:29
http://mantis.testlink.org/file_download.php?file_id=3039&type=bug
png

png tl_bugs_per_tc3.png (46,245) 2012-12-11 08:30
http://mantis.testlink.org/file_download.php?file_id=3041&type=bug
png
Issue History
2012-12-07 09:30mbarNew Issue
2012-12-07 09:30mbarFile Added: tl_bugs_per_tc.png
2012-12-07 09:54fmanPriorityhigh => low
2012-12-07 09:54fmanDescription Updatedbug_revision_view_page.php?rev_id=2255#r2255
2012-12-07 09:55fmanNote Added: 0017986
2012-12-07 09:56fmanStatusnew => feedback
2012-12-07 10:11mbarNote Added: 0017988
2012-12-07 10:11mbarStatusfeedback => new
2012-12-07 14:28fmanNote Added: 0017992
2012-12-07 18:09fmanNote Added: 0017998
2012-12-07 18:10fmanStatusnew => feedback
2012-12-09 17:20fmanStatusfeedback => closed
2012-12-09 17:20fmanAssigned To => fman
2012-12-09 17:20fmanResolutionopen => won't fix
2012-12-10 09:49mbarNote Added: 0018007
2012-12-10 09:49mbarStatusclosed => assigned
2012-12-10 09:49mbarResolutionwon't fix => reopened
2012-12-10 09:49mbarFile Added: tl_bugs_per_tc2.png
2012-12-10 11:11fmanNote Added: 0018008
2012-12-10 11:25mbarNote Added: 0018009
2012-12-10 11:27mbarNote Added: 0018010
2012-12-10 19:17fmanNote Added: 0018013
2012-12-10 19:17fmanRelationship addedchild of 0005406
2012-12-10 19:17fmanStatusassigned => feedback
2012-12-10 19:29fmanFile Added: issue-5401.png
2012-12-11 06:57ThayalanNote Added: 0018016
2012-12-11 08:29mbarNote Added: 0018017
2012-12-11 08:29mbarStatusfeedback => assigned
2012-12-11 08:30mbarFile Added: tl_bugs_per_tc3.png
2012-12-11 10:48fmanNote Added: 0018019
2012-12-11 12:06ThayalanNote Added: 0018023
2012-12-12 07:02fmanIssue cloned: 0005417
2012-12-12 07:02fmanRelationship addedrelated to 0005417
2012-12-12 07:04fmanTask Workflow StatusTBD => READY FOR TESTING
2012-12-12 07:04fmanStatusassigned => resolved
2012-12-12 07:04fmanFixed in Version => 1.9.6 (2013 Q1 - bug fixing)
2012-12-12 07:04fmanResolutionreopened => fixed
2013-01-03 20:25fmanRelationship addedhas duplicate 0005449
2013-01-07 21:50aostadTag Attached: report by tester per build
2013-05-30 19:40fmanStatusresolved => closed

Notes
(0017986)
fman   
2012-12-07 09:55   
In order to consider the isseu we need a complete textual description of steps, with expected results and actual results, i.e. a complete test case.
(0017988)
mbar   
2012-12-07 10:11   
I will cut to the chase here: let's say we already have a test project, test suite with test cases. Also let's assume we have a test plan with added test cases ready to execute.
- on test case execution page add new bug report, use Redmine tracker with rest interface (enter Redmine ID of an existing Redmine issue). The redmine issue can be in "New" status
- save test case execution
- go to Bugs per Test Case report, see that the Redmine issue is connected to your saved test case, and note that TestLink considers it as Open (all is OK here: New is kinda Open)
- change Redmine issue status to Closed
- go to Bugs per Test Case report, see that the Redmine issue is connected to your saved test case, and note that TestLink STILL considers it as Open (wrongly), even if the real status is shown as [Closed]

Expected result: TestLink should consider Closed Redmine issue as Resolved and print it with strikeout font on the Bugs per Test Case report. It did that before :)
(0017992)
fman   
2012-12-07 14:28   
Ok, a lot better.
I'm going to give a look and then provide here the exact model of how we need issues will be reported
(0017998)
fman   
2012-12-07 18:09   
if all the issue is the strikeout font , then IMHO this is not an really issue
because we can change the way we use to represent on video different status.
May be the strikeout font was original author choice, but this does not means we will support this, Not matter what have done before.
I will consider this an issue if report is presenting WRONG DATA , from
the figures point of view.

Please provide feedback.
You can think about an option to choose how to display resolved issue at GUI LEVEL
(0018007)
mbar   
2012-12-10 09:49   
I agreee that "strikeout" font is not an issue here.
The real issue is wrong count of Open/Resolved bugs in Bugs per test Case report in Test Link on data from Redmine interface.
Please see new tl_bugs_per_tc2.png screenshots with red highlights.
(0018008)
fman   
2012-12-10 11:11   
OK, got the idea and found the issue
Original implementation use this code
if ((!strpos($bugInfo['link_to_bts'],"<del>")) && 
    (!strpos($bugInfo['link_to_bts'],"</del>")))


To identify issue status, and IMHO This SUCKS because there is NO CLEAR
indication on dev docs of THIS.

I'm going to try to find a better solution.

You will be informed AUTOMATICALLY by mantis, when work will be done on this issue.

Thanks for your help
(0018009)
mbar   
2012-12-10 11:25   
Thanks!
Today we migrated to latest 1.9.5 QA, i.e. TestLink Development Prague 1.9.6 (Q1 2013), so you can update Product Version of this issue if it's better for you.
(0018010)
mbar   
2012-12-10 11:27   
Product version should be "1.9.5 (2012 Q4 - bug fixing)" but I cannot change it.
(0018013)
fman   
2012-12-10 19:17   
Try with latest commit (use instructions provided on 0005406 ), and provide feedback
(0018016)
Thayalan   
2012-12-11 06:57   
I downloaded and deployed. But When I tried to link a failed Test cases with an existing mantis defect. It's not getting added properly. Build Column updated but 'Relevant bugs' column is blank. Please confirm whether I'm missing anything here.
(0018017)
mbar   
2012-12-11 08:29   
Latest commit works OK for Redmine :) Consider this case solved.
Thanks a lot!
(0018019)
fman   
2012-12-11 10:48   
@thayalan
For mantis db this has not been implemented yet
only for mantis soap and redmine rest
(0018023)
Thayalan   
2012-12-11 12:06   
Thanks fman. You info shed light on the issue I faced with earlier.