Bug #75215 Fabric unittests please report missing environment
Submitted: 15 Dec 2014 15:46 Modified: 4 Mar 2015 3:02
Reporter: Ingo Strüwing Email Updates:
Status: Closed Impact on me:
Category:MySQL Fabric Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[15 Dec 2014 15:46] Ingo Strüwing
The Fabric unittests (test.py) may please report, if the environment is not set up properly.

For example, if the environment variables MYSQLDUMP or MYSQLCLIENT are not set correctly, the test suite fails on tests, but doesn't tell why.

How to repeat:
Start test.py without the environment variables MYSQLDUMP or MYSQLCLIENT set.

Suggested fix:
Check as much of the environment as possible at test begin.
Or report, that the client program was not found, directly in the test case.
[4 Mar 2015 3:02] Philip Olson
Posted by developer:
Fixed as of the upcoming MySQL Fabric 1.5.4 / 1.6.1 releases, and here's the changelog entry:

With Fabric, the test suite now checks if the required environment
variables, such as MYSQLDUMP and MYSQLCLIENT, are set before proceeding.

Thank you for the bug report.