MantisBT - TestLink
View Issue Details
0008647TestLinkKeywordspublic2019-04-24 12:472019-05-03 17:06
mshishodia 
fman 
normalmajoralways
closedreopened 
1.9.19 (2019 Q1) 
 
MYSQL 8.0
Chrome, ff
7.2
TBD
0008647: Keyword dispalyed as none in test cases after upgrading 1.9.19
Upgrade testlink 1.9.17 > testlink 1.9.18
Upgrade testlink 1.9.18 > testlink 1.9.19

Now when seeing existing test cases, then keyword displayed as none.
Now when I'm looking in testlink DB.
In Keyword Table tcversion_id = 0 instead of value's


No tags attached.
related to 0008639closed fman Keyword missing in Testlink 1.9.18 and 1.9.19 
jpg Testlink_Keywor_Issue .jpg (188,529) 2019-04-24 12:47
http://mantis.testlink.org/file_download.php?file_id=5146&type=bug
jpg
Issue History
2019-04-24 12:47mshishodiaNew Issue
2019-04-24 12:47mshishodiaFile Added: Testlink_Keywor_Issue .jpg
2019-04-24 12:51mshishodiaNote Added: 0028765
2019-04-24 15:22fmanNote Added: 0028766
2019-04-25 05:35mshishodiaNote Added: 0028768
2019-04-25 08:20fmanNote Added: 0028769
2019-04-25 08:21fmanQA Team - Task Workflow Status => TBD
2019-04-25 08:21fmanStatusnew => closed
2019-04-25 08:21fmanAssigned To => fman
2019-04-25 08:21fmanResolutionopen => unable to reproduce
2019-04-25 09:07mshishodiaNote Added: 0028774
2019-04-25 09:07mshishodiaStatusclosed => assigned
2019-04-25 09:07mshishodiaResolutionunable to reproduce => reopened
2019-04-25 10:29fmanNote Added: 0028777
2019-04-25 10:30fmanNote Edited: 0028777bug_revision_view_page.php?bugnote_id=28777#r5820
2019-04-25 10:30fmanNote View State: 0028777: public
2019-04-25 10:31fmanRelationship addedrelated to 0008639
2019-04-25 10:32fmanNote Added: 0028778
2019-04-26 17:25fmanStatusassigned => feedback
2019-04-29 10:27fmanNote Added: 0028799
2019-04-29 10:30mshishodiaNote Added: 0028800
2019-04-29 10:30mshishodiaStatusfeedback => assigned
2019-04-29 10:35fmanNote Added: 0028801
2019-05-03 17:06fmanStatusassigned => closed

Notes
(0028765)
mshishodia   
2019-04-24 12:51   
In the Keyword table, tcversion_id belong to Testcase_id or testcase version ?

tcversion_id store in which table
(0028766)
fman   
2019-04-24 15:22   
tcversion_id means tcversion ID

tcversion_id store in which table? tcversions table, id field

IMHO your upgrade has not be done completely
(0028768)
mshishodia   
2019-04-25 05:35   
tell me now what I do
(0028769)
fman   
2019-04-25 08:20   
Hi
dear user, it will be great if you can understood that a minimul of politeness is needed whe asking for help:

Then => tell me now what I do => NO good
Would you mind to provide me some intructions? => a bit better

I can not provide step by steps instructions, because IMHO all the instructions are present in the README present with each distribution.

In addition your way to provide details is such that you never provide detailed steps you have done.

IMHO you need to proceed first to 1.9.18, checking the result of the different sql script you have runned.

For my point of view till now I saw no evidence of issue => ticket will be closed
(0028774)
mshishodia   
2019-04-25 09:07   
I upgrade Testlink 1.9.17 > 1.9.18
and

Execute `install/sql/alter_tables/1.9.18/<your_db>/DB.1.9.17/step1/db_schema_update.sql`
  b. Execute (IF EXISTS) `install/sql/alter_tables/1.9.18/<your_db>/DB.1.9.17/stepZ/z_final_step.sql`
Then I upgrade Testlink-1.9.18 > 1.9.19
and
Execute `install/sql/alter_tables/1.9.19/<your_db>/DB.1.9.18/step1/db_schema_update.sql`
  b. Execute (IF EXISTS) `install/sql/alter_tables/1.9.19/<your_db>/DB.1.9.18/stepZ/z_final_step.sql`

After upgrading I view test cases under test specification
Keyword displayed as NONE

Then I looking to DB and found that tcversion_id = 0 for all test cases in testcase_keyword table.

Can you please suggest how can I get my tcversion_id in testcase_keyword
(0028777)
fman   
2019-04-25 10:29   
(edited on: 2019-04-25 10:30)
There was a mistake on the README.MD, finally a mistake but not so difficult to solve if you read with attention the file
I was able to find it now after all this ping pong because finally, you have provided the details requested.

In addition if you have proceed as requested i.e. FIRST go to 1.9.18 and see if things worked we have saved lot of time.

Next time you ask for help it will be better that you follow the instructions provided.

The right way to upgrade to 1.9.18 from 1.9.17 is


13. Upgrade from 1.9.17 to 1.9.18

WARNING: if you are using a table prefix replace `prefix` with your prefix

  a. Execute `install/sql/alter_tables/1.9.18/<your_db>/DB.1.9.18/step1/db_schema_update.sql`
  b. Execute (IF EXISTS) `install/sql/alter_tables/1.9.18/<your_db>/DB.1.9.18/stepZ/z_final_step.sql`


if you open the sql files (a thing that is not going to hurt) you will find the sql that update the new fields

ONly after you have moved th 1.9.18 and you see that keywords are OK, then you can move to 1.9.19

Same minor error on 1.19.18 to 1.19.19


 a. Execute `install/sql/alter_tables/1.9.19/<your_db>/DB.1.9.19/step1/db_schema_update.sql`
  b. Execute (IF EXISTS) `install/sql/alter_tables/1.9.19/<your_db>/DB.1.9.19/stepZ/z_final_step.sql`

(0028778)
fman   
2019-04-25 10:32   
why you have opened a new ticket leaving 0008639 opened?
(0028799)
fman   
2019-04-29 10:27   
would you mind to provide feedback?
(0028800)
mshishodia   
2019-04-29 10:30   
It's not work, reason I made changes in DB, so table already there in DB .
(0028801)
fman   
2019-04-29 10:35   
then you will need to restart from a backup