Mantis Bugtracker          
testlink.org

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008625TestLinkMigration/Upgrade Testlinkpublic2019-04-08 08:312019-04-10 13:08
Reporterstuti.thakur 
Assigned To 
PrioritynormalSeveritytrivialReproducibilityN/A
StatusnewResolutionopen 
PlatformWindowsOSWindows 10 ProOS Version1709
Product Version 
Fixed in Version 
Summary0008625: TestLink Migration: Feature to include test case execution history while migration
DescriptionWe 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).
TagsNo tags attached.
Database (MySQL,Postgres,etc)MySQL
BrowserAll
PHP Version
TestCaseID
QA Team - Task Workflow StatusTBD
Attached Files

- Relationships

-  Notes
(0028684)
fman (administrator)
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.
(0028687)
stuti.thakur (reporter)
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.

(0028690)
fman (administrator)
2019-04-09 18:22

This kind of guidance is not provided via mantis, because is not an issue.
please request a user for forum.testlink.org 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.
(0028697)
stuti.thakur (reporter)
2019-04-10 13:08

Ok. Thanks for the help.

- Issue History
Date Modified Username Field Change
2019-04-08 08:31 stuti.thakur New Issue
2019-04-08 15:06 fman Note Added: 0028684
2019-04-08 15:06 fman QA Team - Task Workflow Status => TBD
2019-04-08 15:06 fman Priority urgent => normal
2019-04-08 15:06 fman Severity feature request => trivial
2019-04-09 09:27 stuti.thakur Note Added: 0028687
2019-04-09 09:27 stuti.thakur Note View State: 0028687: private
2019-04-09 09:27 stuti.thakur Note View State: 0028687: public
2019-04-09 09:29 stuti.thakur Note Edited: 0028687 View Revisions
2019-04-09 18:22 fman Note Added: 0028690
2019-04-10 13:08 stuti.thakur Note Added: 0028697



Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker