|Anonymous | Login | Signup for a new account||2019-01-19 05:18 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007990||TestLink||Test Execute - Export Test Plan||public||2017-06-24 22:27||2018-10-15 13:27|
|Product Version||1.9.16 (2016 Q4)|
|Fixed in Version|
|Summary||0007990: Exporting test results from the current plan|
Please, implement a new feature - Export the current build result. This will be helpful when you have for example short Smoke cycle and another Full cycle which has all TCs from Smoke.
I have used a stable for my purpose fork from your repository - Commit on May 18, 2017 @fmancardi Fix Ticket 0007936: Unable to display Charts - PHP 7.1 and created a new branch with the functionality - https://github.com/wildkity/testlink-code/tree/Export-results. [^]
It does not work for the Steps and Custom fields.
There is one issue - when bug_id is empty - we add an empty bug in the DB and then in Testlink is shown - TestLink Internal Message: getIssue() FAILURE on issueTrackerInterface::buildViewBugLink.
Maybe several thinks should be changed in the import function
- it should not take the project, plan, platform and build from the xml - it should replace them with current ones - from the place we are currently
- it should not add rows in DB if the tags are empty
Have a nice and smiley day!
|Tags||No tags attached.|
|QA Team - Task Workflow Status|
it's not clear what the export generates, please provide details that can be used from an user point of view.
without this info no action can be taken.
also you have to fix all know issues on your code before send contributed code
It is already possible to export and import whole Testplans with relations to Testcases. Anyway all Builds and Executions gets lost. It would be amazing to support builds and execution results in this Export/Import Feature.
In our use case after we have created a huge bunch of Testprojects we dont want to maintain this anymore, cause of Exports/Imports to external databases are expensive. So we want to merge existent Testprojects.
If you need some more informations, feel free to ask :)
Thanks for your support.
>> Anyway all Builds and Executions gets lost
please provide really detailed steps to reproduce , I need a whole scenario that i can create and test.
edited on: 2018-10-13 08:34
1. Create two Testprojects and fill with Testspecifications, Create and assign to Testplans, create builds and make executions here.
2. Create a new Testproject. In this Testproject we want to merge all the datas and stuff from step 1. in further steps
3. Export Testspecifications created in step 1 (Prefixes and Requirements checkboxes are used)
4. Export Testplans created in step 1
5. In Testproject created in step 2 we import Testcases and Testplans
Now execution results from execution History is missing. I hope you can reproduce my steps. If its not clear enough i can check for more detailed steps.
>> Now execution results from execution History is missing.
q1. in xml file generated?
q2. not on testlink db anymore?
thanks for your collaboration
|I can answer your questions in detail on monday. Have a nice weekend.|
In my step 4 above i meaned the test execution from testplan and click on "Export for results import" button. In this XML i got some dummy datas like that:
<notes>test link rocks </notes>
<tester>put login here</tester>
<!-- if not present now() will be used -->
<bug_id>put your bug id here</bug_id>
<notes>your step exec notes</notes>
In Testlink Version 1.9.19 the Export window is empty and i cant get this xml file anymore.
Anyway... the solution from wildkitty in https://github.com/wildkity/testlink-code/tree/Export-results [^] works great. I got an XML with all the results. I just have to update the IDs and naming in XML as i want and can use the existent "Import Results (XML)" button from executions window to get all my results imported in the new testproject.
XML looks like this now:
I would vote to merge wildkittys solution in testlink branch.
Export for import has DUMMY data that is intended to provide clues of how to provide the data, not to export WHAT HAS HAPPENED.
Going to check if wildkitty has ever done a Pull Request.
|2017-06-24 22:27||wildkity||New Issue|
|2017-07-03 15:17||fman||Note Added: 0026543|
|2018-10-12 09:21||ChuckNorrison||Note Added: 0027994|
|2018-10-12 18:07||fman||Note Added: 0027998|
|2018-10-13 08:33||ChuckNorrison||Note Added: 0028002|
|2018-10-13 08:34||ChuckNorrison||Note Edited: 0028002||View Revisions|
|2018-10-13 08:35||fman||Note Added: 0028003|
|2018-10-13 09:02||ChuckNorrison||Note Added: 0028004|
|2018-10-15 10:37||ChuckNorrison||Note Added: 0028016|
|2018-10-15 13:27||fman||Note Added: 0028017|
|Copyright © 2000 - 2019 MantisBT Team|