MantisBT - TestLink
View Issue Details
0005873TestLinkContribution Maintained BY USERpublic2013-08-22 09:052018-10-06 15:41
1.9.9 (2013 Q4 - bug fixing) 
1.9.17 (2018 Q1) 
Tested with MySQL
0005873: User contribution : Add/Remove Testcases Navigation REQUIREMENTS
All provided modifications have been done from stable version TL 1.9.7.

In Add/Remove TestCases section, TestLink order TestCases only by TestSuite.
The content of the attached files "" add the ability to order TestCases by Requirement Coverage in TL 1.9.7.

The attached file "NewStrings.txt" provide new lines that has to be created to display the new functionnality. You have to update the file "strings.txt" in the folder "locale\en_GB\".
The attached PNG file is provided to show how to access the functionnality in TL GUI.
No tags attached.
related to 0000231new  Requirements based testing - allow add TC to TP via REQ 
child of 0005870closed fman User contribution : Req Based Report in MS Excel format, Query Metrics and Group TestCases by Coverage in Add/Remove Testcases 
zip (116,667) 2013-08-22 09:05
txt NewStrings.txt (168) 2013-08-22 09:05
png TL-1.9.7_testsGroupedByReqCov.PNG (23,225) 2013-08-22 09:05

pdf UserView.pdf (1,246,063) 2014-04-26 00:14
docx EvolutionsOverview.docx (288,190) 2017-02-27 10:06
? OrderByReq.odt (459,141) 2017-04-02 13:15
? DocOrderByRequirement.odt (397,228) 2017-12-17 13:34
Issue History
2013-08-22 09:05Mr.BricodageNew Issue
2013-08-22 09:05Mr.BricodageFile Added:
2013-08-22 09:05Mr.BricodageFile Added: NewStrings.txt
2013-08-22 09:05Mr.BricodageFile Added: TL-1.9.7_testsGroupedByReqCov.PNG
2013-09-01 17:24fmanAssigned To => fman
2013-09-01 17:24fmanStatusnew => feedback
2013-09-01 17:26fmanRelationship addedchild of 0005870
2014-04-25 20:10Mr.BricodageNote Added: 0020888
2014-04-25 20:10Mr.BricodageStatusfeedback => assigned
2014-04-25 20:19Mr.BricodageNote Added: 0020890
2014-04-26 00:14Mr.BricodageFile Added: UserView.pdf
2014-04-26 00:15Mr.BricodageNote Added: 0020891
2014-04-26 06:52fmanNote Added: 0020892
2014-04-27 08:01fmanNote Added: 0020895
2014-04-27 08:01fmanProduct Version => 1.9.9 (2013 Q4 - bug fixing)
2014-04-27 09:11fmanNote Added: 0020896
2014-04-27 13:54fmanNote Added: 0020898
2014-04-27 15:22fmanNote Added: 0020900
2014-04-27 16:47Mr.BricodageNote Added: 0020907
2014-04-27 20:08fmanNote Added: 0020908
2014-05-10 08:25fmanSummaryUser contribution : Group TestCases by Requirements Coverage in Add/Remove Testcases => User contribution : Add/Remove Testcases Navigation REQUIREMENTS
2015-04-26 15:53Mr.BricodageRelationship addedrelated to 0000231
2017-02-25 15:27Mr.BricodageNote Added: 0026033
2017-02-25 19:43fmanNote Added: 0026034
2017-02-26 10:46Mr.BricodageNote Added: 0026035
2017-02-27 10:06Mr.BricodageFile Added: EvolutionsOverview.docx
2017-02-27 10:07Mr.BricodageNote Added: 0026039
2017-02-27 14:41Mr.BricodageNote Added: 0026044
2017-02-27 18:34fmanNote Added: 0026045
2017-03-22 08:53Mr.BricodageNote Added: 0026163
2017-04-02 13:15Mr.BricodageFile Added: OrderByReq.odt
2017-12-17 13:34Mr.BricodageFile Added: DocOrderByRequirement.odt
2017-12-17 13:35Mr.BricodageNote Added: 0027095
2017-12-26 21:53Mr.BricodageNote Added: 0027107
2018-05-14 21:32Mr.BricodageNote Added: 0027461
2018-05-15 18:03fmanQA Team - Task Workflow StatusTBD => READY FOR TESTING
2018-05-15 18:03fmanStatusassigned => resolved
2018-05-15 18:03fmanFixed in Version => 1.9.17 (2018 Q1)
2018-05-15 18:03fmanResolutionopen => fixed
2018-10-06 15:41fmanStatusresolved => closed

2014-04-25 20:10   
Merge request : [^]
2014-04-25 20:19   
"as stated on mantis I need detailed documentation about feature from an user point of view. Till I do not have the requeste info on mantis, I can not proceed with any code evaluation." : I wasn't aware of your need (user guide). I'll provide a doc ASAP.

2014-04-26 00:15   
File "UserView.pdf" uploaded to explain the feature from an user point of view
2014-04-26 06:52   
>> I wasn't aware of your need (user guide)
see note (0019469):
(excerpt here)
... would you mind to provide better details regarding this feature ?
more screen shoots that display the effect of this setting on right side of screen will be a must.
2014-04-27 08:01   
OK, please check if what i've understood is right

with new option, the tree on left pane is build using REQUIREMENT SPECIFICATION and not Test project.

best regards
2014-04-27 09:11   
There is an important aspect of contributions, comments on contributed code has to convey right information.
While reviewing this code at least on one file (lib/ajax/getreqcoveragenodes.php)
this requirement is not fullfilled.
You can not leave old comments inside because are garbage.
Take in condiserading next time.
Can sound silly but I do not want just working code, but code with a minimun
level of quality, and presence of right not misleading comments are a MUST.
2014-04-27 13:54   
Another important thing:
you can not use a different programming style.
Is like traveling to a foreing country, then you have to respect other customs.
At least on this project I want this kind of behaviour
2014-04-27 15:22   
More details are needed, when req to test case linking is not simple.

Req Spec RSP-100
RQ01 -> TC-01, TC-02
RQ02 -> TC-01, TC-03

1. What is displayed on right side pane when you click on Req. Spec RSP-100.
2. How do you provide info when clicking on RQ01, that removing TC-01 will affect also RQ02 ?
2014-04-27 16:47   
note 20892 :
"see note (0019469)" : I didn't find it, but not matters

note 20895 :
"OK, please check if what i've understood is right
with new option, the tree on left pane is build using REQUIREMENT SPECIFICATION and not Test project." => Yes, you have understood.

notes 20896 and 20898 :
OK, well understood. I'll inform the dev team, that will be taken in account for next contributions.

note 20900 :
1. The collection of all RQ (RQ01 and RQ02 in your example) can be selected. See page 5 of "UserView.pdf" for a screenshot.
2. No information is provided. The need hasn't been expressed by my test designers team. But you're right, the information should be usefull in some cases.
2014-04-27 20:08   
I've started code review. IMHO an important amount of work is needed in order
to eliminated lot duplicated code introduced by your development people.
in addition i think implementation for req spec done loop calling your new gen_*
can be bad effects on performance.
anyway i think your code can be a good strarting point, but will not be easier
2017-02-25 15:27   
@fman : one guy of my dev team has posted on TestLink forum about this feature and about the way to implement it (see : [^])

The code provided here has been reworked for TL 1.9.17 DEV and he is waiting your advice on forum to develop according to your wishes.

Our goal is to provide the implementation that will be merged by TestLink Dev Team.
2017-02-25 19:43   
I would prefer to discuss this HERE , that using forum.
do you think will be possible?

2017-02-26 10:46   
We'll attach a doc with planned modifications tomorrow.
When we'll agree about doc content, we will provide a Pull Request that add defined functionalities.

Then Github code review could be used.

Your feedback provided on previous version has already be taken in account.
2017-02-27 10:07   
EvolutionsOverview.docx attached
2017-02-27 14:41   
pull request link : [^]
2017-02-27 18:34   
OK, will need time to give a look => be patient
2017-03-22 08:53   

I recently made the last desired modifications.

Can you tell me if I have to realize other changes to be in accordance with your rules.

2017-12-17 13:35   
Documentation attached for the new merged feature
2017-12-26 21:53   
Should be logged as resolved in TestLink 1.9.17 : PR has been merged
2018-05-14 21:32   
Ticket status should be set as resolved, feature available in TestLink 1.9.17