MantisBT - TestLink
View Issue Details
0008509TestLinkReportspublic2018-12-18 12:432018-12-24 08:54
multicode 
fman 
normalminoralways
resolvedfixed 
Red Hat Enterprise Linux Server6.7
1.9.18 (2018 Q3) 
1.9.19 (2019 Q1) 
MySQL
Chrome 62.0.3202.89
7.0.31
TBD
0008509: No keywords in Test Plan Report under some conditions
No keywords in Test Plan Report for test case if:
1. Both checkboxes Test Case Keywords AND Step Execution Results are checked.
2. Test case is executed (doesn't matter passed, blocked or failed).
1. Create project "Test Project".
2. Create keyword "Word_1".
3. Create Test Suite "Suite 1" for "Test Project".
4. Add test case "Test 1" into "Suite 1".
5. Add keyword "Word_1" into "Test 1"
6. Create test plan "Plan 1".
7. Add "Test 1" into "Plan 1".
8. Create build "Build 1".
9. Go to Test Reports -> Test Plan Report. Check Test Case Keywords AND Step Execution Results checkboxes, run report for "Suite 1".
10. We will see "Keywords: Word_1" - it's correct.
11. Execute "Test 1".
12. Run Test Plan Report again the same way.
13. We will see "Keywords: None" - it's incorrect.
A similar problem is also in reports Test Report and Test Report on build.
No tags attached.
child of 0008397closed fman Availables hot-fixes for 1.9.18 & How To get full fixed package from GitHub 
jpg No_keywords.jpg (91,705) 2018-12-18 12:50
http://mantis.testlink.org/file_download.php?file_id=5060&type=bug
jpg
Issue History
2018-12-18 12:43multicodeNew Issue
2018-12-18 12:50multicodeFile Added: No_keywords.jpg
2018-12-18 16:39fmanNote Added: 0028340
2018-12-18 19:38fmanAssigned To => fman
2018-12-18 19:38fmanStatusnew => feedback
2018-12-19 06:30multicodeNote Added: 0028345
2018-12-19 06:30multicodeStatusfeedback => assigned
2018-12-19 10:59multicodeNote Edited: 0028345bug_revision_view_page.php?bugnote_id=28345#r5673
2018-12-19 11:04multicodeNote Edited: 0028345bug_revision_view_page.php?bugnote_id=28345#r5674
2018-12-23 08:30fmanNote Added: 0028373
2018-12-23 08:30fmanNote Added: 0028374
2018-12-23 08:30fmanNote Edited: 0028374bug_revision_view_page.php?bugnote_id=28374#r5699
2018-12-23 08:30fmanQA Team - Task Workflow Status => TBD
2018-12-23 08:30fmanFixed in Version => 1.9.19 (2019 Q1)
2018-12-23 08:31fmanRelationship addedchild of 0008397
2018-12-23 08:31fmanStatusassigned => resolved
2018-12-23 08:31fmanResolutionopen => fixed
2018-12-24 08:41multicodeNote Added: 0028383
2018-12-24 08:43multicodeNote Edited: 0028383bug_revision_view_page.php?bugnote_id=28383#r5701
2018-12-24 08:54fmanNote Added: 0028384

Notes
(0028340)
fman   
2018-12-18 16:39   
1. reporter does not need to add himself/herself to issue monitoring

2. get latest code from github, do fresh install, retest & provide feedback
(0028345)
multicode   
2018-12-19 06:30   
(edited on: 2018-12-19 11:04)
I'm so sorry! It is necessary to check not checkbox "Step Execution Results", but "Test Case Custom Fields" along with "Test Case Keywords". Or you can just press "check/uncheck all".

We have new installation of the stable version 1.9.18 (2018-10-06) with following updates:
http://mantis.testlink.org/view.php?id=8423 [^] - Cannot assign requirement to test case
http://mantis.testlink.org/view.php?id=8450 [^] - Search Requirements Displays SQL Statements
http://mantis.testlink.org/view.php?id=8486 [^] - Testcase attachments not visible in Test Execution
http://mantis.testlink.org/view.php?id=8493 [^] - "Test Cases created per User" button does not respond to mouse clicks
http://mantis.testlink.org/view.php?id=8508 [^] - Incorrect date components separator for Russian localization

(0028373)
fman   
2018-12-23 08:30   
Please when request is to have latest code, get complete latest code from github
(0028374)
fman   
2018-12-23 08:30   
here the fix
https://github.com/TestLinkOpenSourceTRMS/testlink-code/commit/4382b344a7867fb181d80c8ca673892ad8f9fc85 [^]

thanks for your help

(0028383)
multicode   
2018-12-24 08:41   
(edited on: 2018-12-24 08:43)
We installd modules print.inc.php and printDocument.php from github. As a result, after starting the report, we get an empty report (blank frame).
 
Then we returned file printDocument.php (10/06/2018 version) and the report is working now, keywords appeared in it.

(0028384)
fman   
2018-12-24 08:54   
Please proceed as requested => Get Full code from github, do fresh install.
You can configure to point to your test db, then retest.

this can be an issue with your PHP version, I'm testing on 7.2.8.

Change done on printDocument.php, regards avoiding error message on TestLink Evento Viewer.