MantisBT - TestLink
View Issue Details
0008625TestLinkMigration/Upgrade Testlinkpublic2019-04-08 08:312019-04-10 13:08
WindowsWindows 10 Pro1709
0008625: TestLink Migration: Feature to include test case execution history while migration
We need to include the complete test execution history while migrating from older instance of TestLink(TestLink Prague 1.9.5) to TestLink 1.9.14 (Padawan).
No tags attached.
Issue History
2019-04-08 08:31stuti.thakurNew Issue
2019-04-08 15:06fmanNote Added: 0028684
2019-04-08 15:06fmanQA Team - Task Workflow Status => TBD
2019-04-08 15:06fmanPriorityurgent => normal
2019-04-08 15:06fmanSeverityfeature request => trivial
2019-04-09 09:27stuti.thakurNote Added: 0028687
2019-04-09 09:27stuti.thakurNote View State: 0028687: private
2019-04-09 09:27stuti.thakurNote View State: 0028687: public
2019-04-09 09:29stuti.thakurNote Edited: 0028687bug_revision_view_page.php?bugnote_id=28687#r5797
2019-04-09 18:22fmanNote Added: 0028690
2019-04-10 13:08stuti.thakurNote Added: 0028697

2019-04-08 15:06   
migrating to 1.9.14 is a big error when 1.9.19 exists
are you sure that history is missed?
you have not provided enough details.
2019-04-09 09:27   
(edited on: 2019-04-09 09:29)
Thanks for the response.

We are currently using 2 instances of TestLink at our organization. One is TestLink Prague 1.9.5 and another is TestLink 1.9.14 (Padawan).

Now, we want to shut down the older instance that is 1.9.5 and carry on with 1.9.14. But, we also want to make sure that while migrating test cases to newer TestLink their execution history is retained individually which is not the case when we are importing test cases manually.

Please guide us how this can be achieved.

2019-04-09 18:22   
This kind of guidance is not provided via mantis, because is not an issue.
please request a user for and post there to have support from other users.

As in any migration project, you have normally to do some minor test before starting the definitive one.

Issue will be that you need to mix two different instances, and you will need to adjust db ID that will be duplicated in the destination DB.
There is nothing developed to do this kind of DB 'blend', this is not a simple migration.
2019-04-10 13:08   
Ok. Thanks for the help.