Subscribe Join 180,000+ subscribers and receive articles from our blog about software quality, testing, QA and security. Subscribe

TestRail 6.7.2 Released

I’m getting

RuntimeException: You need to enable the PDO_Mysql extension for Phinx to run properly. in /var/www/testrail/vendors/phinx/Db/Adapter/MysqlAdapter.php:95

I already updated my .ini file and enabled the prior to the first memory error

It’s working! Thank you!

As @sergiochoo has noted above, we have released new Server and Docker versions ( which should resolve the upgrade memory size issues.

Thanks for the fix, I’m currently seeing that my background tasks are now inactive.
The docs listed: Activating the Background Task - TestRail

Do not state how to do this with Docker, I’m assuming this should be configured within the Docker image itself though?

After upgrading from v6.7.1.1020 to v6.7.2.1043 and restoring the database from a backup, I’m not able to consult Milestones. When I click on a milestone it shows this error:
Undefined property: stdClass::$refs

File: C:\inetpub\wwwroot\testrail\app\views\milestones\sidebar_info.php
Line: 26
Status Code: 500
Uri: /testrail/index.php?/milestones/view/1 (GET)

Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36
PHP: 7.2.26
Server: Windows NT 10.0 build 17763 (Windows Server 2016) AMD64

at errors::show (errors.php:62)
at ErrorHandler::error (sidebar_info.php:26)
at unknown (loader.php:240)
at Loader_core->view_abs (loader.php:213)
at Loader_core->view (view.php:252)
at unknown (loader.php:240)
at Loader_core->view_abs (loader.php:213)
at Loader_core->view (loader.php:261)
at Loader_core->page (milestones.php:717)
at Milestones_controller->view (controller.php:257)
at Controller->_invoke_web_call (controller.php:168)
at Controller->_invoke_web (controller.php:120)
at Controller->_invoke (gizmo.php:129)
at require_once (index.php:114)


This seems to have resolved itself

Just upgraded from 6.6.0 to 6.7.2, it seems that the Bugfix no 11 still occurs on this version.
When moving testcases within the same section or other one with drag&drop the webpage gets stuck and the console error output is:
“Uncaught DOMException: Node.appendChild: The new child is an ancestor of the parent”.
Is there any other fix for this?


Thanks for your report and apologies for the inconvenience it has caused.

I would recommend you to reach out to our Support Team at


see lots and lots of extra TestRun and Results pages when there is actualy only 1


Hey Caroline,

Thanks for your report. Let me get back to you on this.