|Anonymous | Login | Signup for a new account||2019-06-20 06:13 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005930||TestLink||Database MySQL||public||2013-09-18 15:43||2014-11-29 16:20|
|Product Version||1.9.8 (2013 Q3 - bug fixing)|
|Fixed in Version|
|Summary||0005930: After upgrading from 1.9.7 to 1.9.8 some Test Cases execution history report Test Case has not been executed|
|Description||After upgrading from 1.9.7 to 1.9.8 some Test Cases execution history report "This Test Case has not been executed" and does not allow to see the execution history.|
These same tests are blocked from edition because they were in fact already ran and somehow Testlink knows it and reports "You can not edit this version because it has been executed"
These same tests also appear has executed on Test Reports.
Only the Execution history reports the Test Case was not run.
I rolled-back to 1.9.7 and restored the previous DB and it is working fine.
The only thing I can not understand is the pattern that makes this happen to only some of the Test Cases.
|Steps To Reproduce||1- Have a Testlink 1.9.7 installation, with some data regarding executed tests;|
2- upgrade to Testlink 1.9.8;
3- run the sql file step1/db_schema_update.sql
4- run the sql file stepZ/z_final_step.sql
5- go to Testlink webGUI and explore you executed Test Cases.
6- Open the Execution History of those executed tests.
6- some of those tests will report "This Test Case has not been executed" on the execution history page.
|Tags||No tags attached.|
|QA Team - Task Workflow Status||TBD|
|Attached Files|| run_norun.jpg [^] (164,138 bytes) 2013-09-18 15:43
run_norun_2.jpg [^] (148,028 bytes) 2013-09-18 15:43
edited on: 2013-09-18 19:40
please provide your 1.9.7 in order to allow me to test.
send me a link to download it privately to firstname.lastname@example.org
issue changed to private => only reporter and dev team can access it, this way if reporter wants to provide here link or db can be done safely
what is happening is very strange because if you give a look to sql to update you will find that only fields regarding exec time are added.
Then seems very strange that can generate this effect.
It is very important that you can do a simple test in a 1.9.8 FRESH INSTALL, I will try to do the same, but we need to use same test cases,
that's why I request you to try to reproduce on FRESH 1.9.8
Francisco, thanks for your fast reply.
I believe I really have a problem on my DB and it must be an old problem that I only have realize now.
While investigating the issue 0005931 I created a new fresh DB and this way I could access some Testlink features I couldn't before and I could edit user permissions just fine. I believe the problem cause is the same.
I compared my problematic DB schema with the schema of the new one and I just found these differences:
PRIMARY KEY (`version`) -> is missing on the problematic one
`bug_id` varchar(64) NOT NULL DEFAULT '0' -> the problematic DB has varchar(16)
PRIMARY KEY (`testproject_id`) -> the problematic DB has UNIQUE KEY `testproject_issuetracker_uidx1`(`testproject_id`)
I don't find these directly related to my problem but I did the changes to the DB schema anyway.
Unfortunately the same problems persists. I suspect there is something in the DB content also affecting this strange behavior.
edited on: 2013-09-19 20:25
Francisco, I found the BUG and is not related to my DB although I need to make some corrections to it but it's another problem.
The execution history disappears when the Test Plan where it was executed is not active.
Follow these steps:
1- create a Test Case XXX;
2- Create a Test Plan A;
3- Associate Test Case XXX to Test Plan A;
4- create a build B1 on Test Plan A;
5- Execute the Test Case XXX (result is irrelevant)
6- Go to Test Specification and select Test Case XXX
7- you will see "Warning! This Test Case version has been executed."
8- click on "Execution History"
9- you will the the history just fine
10- Deactivate Test Plan A
11- Go to Test Specification and select Test Case XXX
12- you will see "Warning! This Test Case version has been executed."
13- click on "Execution History"
14- you will the message "This Test Case has not been executed"
On 1.9.7 Execution History used to show all records ignoring whether the Test Plans are active or not. I believe this should continue to be the correct behavior.
Thanks for the good report you have done on note 19677.
I suppose the issue is a side effect of other change.
I suppose you are right when you said:
>> On 1.9.7 Execution History used to show all records ignoring
>> whether the Test Plans are active or not.
>> I believe this should continue to be the correct behavior.
I'm going to check, please be patient
I think we can have a similar issues in this situation (but need to check)
1. Test Plan A - Public + Active -> TC1
2. Test Plan B - PRIVATE + Active -> TC1
3. execute on Test Plan B
4. Use an USER THAT CAN not access test plan B
how are you going to provide info ?
|I believe that use case requires Execution History to look for user permissions before presentation.|
|2013-09-18 15:43||mat||New Issue|
|2013-09-18 15:43||mat||File Added: run_norun.jpg|
|2013-09-18 15:43||mat||File Added: run_norun_2.jpg|
|2013-09-18 19:39||fman||Note Added: 0019667|
|2013-09-18 19:39||fman||View Status||public => private|
|2013-09-18 19:40||fman||Note Edited: 0019667||View Revisions|
|2013-09-18 19:45||fman||Note Added: 0019668|
|2013-09-19 14:06||mat||Note Added: 0019676|
|2013-09-19 15:35||mat||Note Added: 0019677|
|2013-09-19 20:25||fman||Note Edited: 0019677||View Revisions|
|2013-09-19 20:27||fman||Note Added: 0019679|
|2013-09-19 20:27||fman||View Status||private => public|
|2013-09-20 08:14||fman||Assigned To||=> fman|
|2013-09-20 08:14||fman||Status||new => assigned|
|2013-10-13 16:04||fman||Note Added: 0019831|
|2013-10-13 16:13||fman||Relationship added||related to 0005971|
|2013-10-14 10:47||mat||Note Added: 0019833|
|Copyright © 2000 - 2019 MantisBT Team|