Double link to requirement after excel import to RQM
Hello everyone,
We are using n:m mapping, this means one test case to one or more requirements.
I would like to create "new" test cases in RQM with content of an excel file and they already have an existing link to a requirement in DNG. (like a migration)
For this solution I use in the config file:
testcase.requirement=LinkByExistingID(COLUMN_NAME)
for the n:m mapping I use ‘new line’ or 'coma' in the column of Req. ID - so far so good
But after the import of test cases, the test case has an double link of the same requirement ID to DNG and I don't know why.
for example:
DNG Req-ID 1234
DNG Req-ID 3456
after
Excel import to RQM
TC link to DNG "1234", "1234", "3456", "3456"
if I have an only one requirement ID it is the same
DNG Req-ID 1234
after
Excel import to RQM
TC link to DNG "1234", "1234"
Has anybody an idea?
sorry, i can't upload a picture ( >60 reputation points)
|
Accepted answer
Hi Sandro
As Ian replied, there are base and module requirements in DNG.
Please refer to the article in ETMExcelImporter
[LinkByExistingID] has the below
Note: The following points are specific to the module identifier support in v701 and later.
Sandro Gross selected this answer as the correct answer
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
In DOORS Next you have core (base) artifacts and when you reuse one of these in a module (any number of times into any number of modules) these are all valid targets for links - so it can appear you have multiple links to an artifact with the same ID but they should all be distinct entries in a module and/or there can be one to the base artifact. So try opening these artifacts and look at the context they open in.