|Anonymous | Login | Signup for a new account||2019-12-07 02:12 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006840||TestLink||Import results XML format||public||2014-12-15 22:53||2014-12-31 14:22|
|Product Version||1.9.12 (2014 Q3)|
|Fixed in Version||1.9.13 (2015 #1)|
|Summary||0006840: [Import test execution results] Ignore test results if already exists in TestLink (with same execution timestamp)|
|Description||During an import, if a result is already known in TestLink, the import function should ignore the imported data to avoid duplicates entries.|
|Steps To Reproduce||1) use "export for results import" function|
2) fill the xml file for one testcase
3) Import the xml file a 1st time => the result is saved by testlink import function
4) Import the xml file a 2nd time => the result is saved again by testlink import function
==> The 2nd import should be ignored (based on timestamp)
|Additional Information||It is usefull to import execution results even if all testcases of a TestPlan has not be executed yet (to use TestLink reports ans statistics).|
|Tags||No tags attached.|
|QA Team - Task Workflow Status||READY FOR TESTING|
|Attached Files|| ImportFilterTimestamp.JPG [^] (31,783 bytes) 2014-12-15 22:55
before.JPG [^] (69,348 bytes) 2014-12-15 22:58
>> During an import, if a result is already known in TestLink,
Can you kindly explaing what is an already known result ?
>> the import function should ignore the imported data to avoid duplicates entries.
The sentence on additional information does not make things clear (IMHO)
Try to spend a little more time when reporting explaining in a way other users can take advantage of this implementations.
ok, I'm sorry, second attempt :
During an import, if a result has already been imported into TestLink (comparaison based on execution timestamp), the import function should ignore the imported data to avoid duplicates entries. This 'ignore mecanism' allow to import the same file several times with 'old' execution data (already imported) and new execution data.
Additionnal information (use case):
I use a testplan export (4 months to test all functionnalities) and want to import partial result every month (to use TestLink reports ans statistics).
With actual comportment, execution data imported after 1 month is imported again during 2nd, 3rd and 4th import (each time with same information). Look at "before.jpg" to see a testcase execution history after several imports for the same testplan.
With modified comportment, execution data already imported during 1st month is not saved again during 2nd, 3rd and 4th import (comparaison of the execution timestamp to know if execution shoud be saved). All 'duplicates' entries in execution history are not present anymore.
OK thanks for the update of documentation.
I've just finished to refactor the code and I'm commiting.
Please get and test.
IMHO in your solution you have ignored platforms.
I've also done changes to standard methods on testcase class to reduce amount of data on query that seems to need only execution_ts
Thanks again for your collaboration
I just tested your code.
Works fine with English wide/UK.
However, problems are present using french :
1) variable name in string.txt for french hasn't been adapted :
"$TLS_import_results_filtered" must be replaced with "$TLS_import_results_skipped". The correct translation into the french string.txt of the text you have defined in English "string.txt" is :
$TLS_import_results_skipped = "Cas de test %s - Version %s - Testeur: %s - Resultat : %s - " .
"Horodage d'exécution : %s - NON IMPORTE (même cas de test, version, Horodatage)";
2) the result string (passed, failed, blocked) is always in English even if another language is selected. The same occurs when using $TLS_import_results_ok (I didn't noticed it before). Maybe that should be the subject of a new bug?
edited on: 2014-12-18 09:03
>> 1) variable name in string.txt for french hasn't been adapted :
OK, my fault I'm going to update
>> 2) the result string (passed, failed, blocked) is always in English
Need to check because theoricaly I use labels => are localized
|2014-12-15 22:53||Mr.Bricodage||New Issue|
|2014-12-15 22:55||Mr.Bricodage||Note Added: 0022373|
|2014-12-15 22:55||Mr.Bricodage||File Added: ImportFilterTimestamp.JPG|
|2014-12-15 22:58||Mr.Bricodage||File Added: before.JPG|
|2014-12-16 11:37||fman||Note Added: 0022374|
|2014-12-16 13:11||fman||QA Team - Task Workflow Status||=> TBD|
|2014-12-16 13:11||fman||Category||Export/Import => Import results XML format|
|2014-12-16 13:11||fman||Summary||[Import test execution results] Ignore test results if already known in TestLink => [Import test execution results] Ignore test results if already exists in TestLink (with same execution timestamp)|
|2014-12-16 17:58||Mr.Bricodage||Note Added: 0022377|
|2014-12-16 18:04||fman||Note Added: 0022378|
|2014-12-16 18:05||fman||Note Added: 0022379|
|2014-12-16 18:05||fman||Assigned To||=> fman|
|2014-12-16 18:05||fman||Status||new => feedback|
|2014-12-16 18:05||fman||Relationship added||child of 0006609|
|2014-12-17 20:18||Mr.Bricodage||Note Added: 0022384|
|2014-12-17 20:18||Mr.Bricodage||Status||feedback => assigned|
|2014-12-18 08:37||fman||Note Added: 0022386|
|2014-12-18 08:46||fman||Note Edited: 0022386||View Revisions|
|2014-12-18 09:03||fman||Note Edited: 0022386||View Revisions|
|2014-12-18 09:03||fman||QA Team - Task Workflow Status||TBD => READY FOR TESTING|
|2014-12-18 09:03||fman||Status||assigned => resolved|
|2014-12-18 09:03||fman||Fixed in Version||=> 1.9.13 (2015 #1)|
|2014-12-18 09:03||fman||Resolution||open => fixed|
|2014-12-31 14:22||fman||Status||resolved => closed|
|Copyright © 2000 - 2019 MantisBT Team|