Mantis Bugtracker 

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008046TestLinkRequirement Managementpublic2017-08-09 07:172017-09-01 08:00
Assigned Tofman 
PrioritynormalSeverityfeature requestReproducibilityalways
StatusresolvedResolutionnot fixable 
PlatformApache/2.4.18OSUbuntuOS Version16.04.2 LTS
Product Version1.9.16 (2016 Q4) 
Fixed in Version 
Summary0008046: Field value "Number of test cases needed" should be zeroable
DescriptionIn some cases it is important to keep track of a requirement not yet mandatory / testable.
This could be ensured by setting the "Number of test cases needed" field to the value 0.
Else there would be invalid missing RQ-linkages reported if a currently untestable, not yet mandatory or not implemented requirement would need to have at least one test case linkage.
Steps To Reproduce1) Open the requirement management view
2) Create a new requirement
3) Verify the "Number of test cases needed" value cannot be zero
TagsNo tags attached.
Database (MySQL,Postgres,etc)MySQL (5.7.18-0ubuntu0.16.04.1 - (Ubuntu))
BrowserFirefix 54.0 (64-Bit) and Google Chrome Version 59.0.3071.115 (64-Bit)
PHP Version7.0.1.8-0ubuntu0.16.04.1
QA Team - Task Workflow StatusTBD
Attached Files

- Relationships

-  Notes
fman (administrator)
2017-08-14 15:54

Right now you have a workaround: if you set req type 'Informational', you do need to provide the number of test case needed.
IMHO this can be a better solution that allows 0.

You can configure this (ask or not for coverage) using

$tlCfg->req_cfg->type_expected_coverage = array(TL_REQ_TYPE_INFO => false);

Please let me know.
fman (administrator)
2017-08-14 15:58

Another option can be to work in OR mode using Req Status or Req Type, to enable/disable the control, and setting it to Zero when writing the value to DB.
fman (administrator)
2017-08-16 09:46

Your feedback will be really appreciated
fman (administrator)
2017-08-26 09:46

no more user feedback
Falk_L (reporter)
2017-09-01 07:53
edited on: 2017-09-01 08:00

Sorry for the late reply. I was on holidays most of the last month.

Will provide more detailled feedback after project phase (around 2017-10-01)

Unfortunately "Informational" would not be appropirate as we heavily use this status for several requirements complementing the following requirements (this will be filtered for to get a better overview about the neccessary test procedures).

- Issue History
Date Modified Username Field Change
2017-08-09 07:17 Falk_L New Issue
2017-08-14 15:54 fman Note Added: 0026704
2017-08-14 15:58 fman Note Added: 0026705
2017-08-16 09:46 fman Note Added: 0026723
2017-08-16 09:46 fman Assigned To => fman
2017-08-16 09:46 fman Status new => feedback
2017-08-26 09:46 fman QA Team - Task Workflow Status => TBD
2017-08-26 09:46 fman Note Added: 0026783
2017-08-26 09:46 fman Status feedback => resolved
2017-08-26 09:46 fman Resolution open => not fixable
2017-09-01 07:53 Falk_L Note Added: 0026813
2017-09-01 08:00 Falk_L Note Edited: 0026813 View Revisions
2017-09-01 08:00 Falk_L Note Edited: 0026813 View Revisions

Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker