MantisBT - TestLink
View Issue Details
0008818TestLinkTest Execute - 'Save and move to next'public2019-12-08 11:222020-03-08 10:44
heju 
 
normalminoralways
newopen 
 
 
mysql
0008818: TL 1.9.20(dev) DB error on "Move to next" in pop up window display
Dear TestLink Team,

a db error occurs in case the "Move to next" button is clicked in the "Test execution" display pop up window accessible from the "Test result matrix" (see steps to reproduce)

In the "Execute Tests" view moving to next TC works as expected.


1. Go to "Test result matrix"
2. For one of the test cases in the matrix, click the "Test Execution" sprocket symbol just before the test case name.
3. In the pop up window click the button "Move to next Test Case"

--> now you should see a db access error
 ==============================================================================

 DB Access Error - debug_print_backtrace() OUTPUT START

 ATTENTION: Enabling more debug info will produce path disclosure weakness (CWE-200)

            Having this additional Information could be useful for reporting

            issue to development TEAM.

 ==============================================================================

#0 database->exec_query() called at [/var/www/html/testlink_1.9.20_191101/lib/functions/database.class.php:763]
#1 database->get_recordset() called at [/var/www/html/testlink_1.9.20_191101/lib/functions/testplan.class.php:7715]
0000002 testplan->getVersionLinked() called at [/var/www/html/testlink_1.9.20_191101/lib/execute/execSetResults.php:2040]
0000003 getLinkedItems() called at [/var/www/html/testlink_1.9.20_191101/lib/execute/execSetResults.php:321]






ERROR ON exec_query() - database.class.php
1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 7 - /* Class:testplan - Method: getVersionLinked */ SELECT tcversion_id FROM testplan_tcversions TPTCV JOIN nodes_hierarchy NH_TCV ON NH_TCV.id = TPTCV.tcversion_id WHERE TPTCV.testplan_id = 642 AND NH_TCV.parent_id =
THE MESSAGE : /* Class:testplan - Method: getVersionLinked */ SELECT tcversion_id FROM testplan_tcversions TPTCV JOIN nodes_hierarchy NH_TCV ON NH_TCV.id = TPTCV.tcversion_id WHERE TPTCV.testplan_id = 642 AND NH_TCV.parent_id = Query failed: errorcode[1064] errormsg:You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 7
No tags attached.
Issue History
2019-12-08 11:22hejuNew Issue
2020-03-04 20:21farrukhnajmiNote Added: 0029521
2020-03-04 20:22farrukhnajmiNote Edited: 0029521bug_revision_view_page.php?bugnote_id=29521#r6019
2020-03-04 20:47farrukhnajmiNote Edited: 0029521bug_revision_view_page.php?bugnote_id=29521#r6020
2020-03-04 21:17farrukhnajmiNote Edited: 0029521bug_revision_view_page.php?bugnote_id=29521#r6021
2020-03-08 10:44fmanNote Added: 0029524

Notes
(0029521)
farrukhnajmi   
2020-03-04 20:21   
(edited on: 2020-03-04 21:17)
I am experiencing the same exact issue with release TestLink 1.9.20 [DEV] with same sequence of steps though the stack trace is slightly different.

OS: Ubuntu Linux 19.02

Until a fix is available, any suggested workaround would be great. Thanks.

 ==============================================================================
 DB Access Error - debug_print_backtrace() OUTPUT START
 ATTENTION: Enabling more debug info will produce path disclosure weakness (CWE-200)
            Having this additional Information could be useful for reporting
            issue to development TEAM.
 ==============================================================================
#0 database->exec_query() called at [/opt/bitnami/testlink/lib/functions/database.class.php:763]
#1 database->get_recordset() called at [/opt/bitnami/testlink/lib/functions/testplan.class.php:7752]
0000002 testplan->getVersionLinked() called at [/opt/bitnami/testlink/lib/execute/execSetResults.php:2051]
0000003 getLinkedItems() called at [/opt/bitnami/testlink/lib/execute/execSetResults.php:322]

(0029524)
fman   
2020-03-08 10:44   
Only workaround is to use the execution feature that is NOT ACCESSED form Test Result Matrix