Mantis Bugtracker          
testlink.org

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006743TestLinkNew Featurepublic2014-11-12 10:472014-12-31 14:22
Reporterlml 
Assigned Tofman 
PrioritynormalSeverityfeature requestReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.9.12 (2014 Q3) 
Fixed in Version1.9.13 (2015 #1) 
Summary0006743: XML-Export: Include ID of test suites
DescriptionWhen exporting test suites, they lack the possibility of displaying their internal ID (whilst test cases show them).

In order to clearly identify a test suite (e.g. when exporting a subset of test suites), there should be an ID given.

A possible solution is to add a single line (<internal_id/>) in "lib/functions/testsuite.class.php" under "function exportTestSuiteDataToXML":
$xmlTC = "<testsuite name=\"" . htmlspecialchars($tsuiteData['name']). '" >' .
         "\n<node_order><![CDATA[{$tsuiteData['node_order']}]]></node_order>\n" .
         "<internal_id><![CDATA[{$container_id}]]></internal_id>\n" .
     "<details><![CDATA[{$tsuiteData['details']}]]></details> \n{$kwXML}{$cfXML}";

Steps To ReproduceExport test suite as XML
TagsNo tags attached.
Database (MySQL,Postgres,etc)na
Browser
PHP Version
TestCaseID
QA Team - Task Workflow StatusREADY FOR TESTING
Attached Files

- Relationships
child of 0006609closedfman Availables hot-fixes for 1.9.12 & How To get full fixed package from gitorious 

-  Notes
(0022120)
fman (administrator)
2014-11-12 17:11

can be added, but use case is not clear.
Will not be used on IMPORT
(0022121)
lml (reporter)
2014-11-12 18:11

Thanks for the fast reply!

Use case is as followed:

We are using TestLink, some clients use different tools (like HP QC) and want to have all our test suites and cases transferred.
I want to have the ability to incrementally update if needed, so if a new test suite deep within my test structure is created with new test cases, only this suite and its cases shall be transferred (and beforehand exported as XML). This test suite can have a name equal to a different test suite at another point in my test structure, so I can't automatically decide if it's new or not by just looking at the exported XML.

And of course, not to be used on import!
(0022123)
fman (administrator)
2014-11-12 19:18

Format will be
<testsuite id="2726" name="TS-200" >
(0022124)
fman (administrator)
2014-11-12 19:20

If you find testlink useful support work through donation
(0022125)
fman (administrator)
2014-11-12 19:23

https://gitorious.org/testlink-ga/testlink-code/commits/db2cdd65887e2b01b8e022afc9b05047f04a78f0 [^]

- Issue History
Date Modified Username Field Change
2014-11-12 10:47 lml New Issue
2014-11-12 17:11 fman Note Added: 0022120
2014-11-12 18:11 lml Note Added: 0022121
2014-11-12 19:18 fman Note Added: 0022123
2014-11-12 19:20 fman Note Added: 0022124
2014-11-12 19:23 fman QA Team - Task Workflow Status => READY FOR TESTING
2014-11-12 19:23 fman Note Added: 0022125
2014-11-12 19:23 fman Status new => resolved
2014-11-12 19:23 fman Fixed in Version => 1.9.13 (2015 #1)
2014-11-12 19:23 fman Resolution open => fixed
2014-11-12 19:23 fman Assigned To => fman
2014-11-12 19:24 fman Relationship added child of 0006609
2014-12-31 14:22 fman Status resolved => closed



Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker