Title: All testing cases failed Last modified: August 31, 2016 --- # All testing cases failed * Resolved [Mulen](https://wordpress.org/support/users/mulen/) * (@mulen) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/) * Hello, * I would really appreciate your help, because I’m not able to make EWWW work on my new VMS (where I moved my website [http://www.cena-vykon.cz](http://www.cena-vykon.cz)). * Plugin status: [http://pastebin.com/6CHtEAGC](http://pastebin.com/6CHtEAGC) Debugging information: [http://pastebin.com/4Eq0En9i](http://pastebin.com/4Eq0En9i) * It looks like everything is on it’s place, but test cases are failing – tool not found. * My VMS provider told me, that they allowed exec and installed all tools on the server, so it should be working, but it’s not! :-X Even when “Use System Paths” is on. * Can you please help me fix it? * Thank you very much, Mulen * [https://wordpress.org/plugins/ewww-image-optimizer/](https://wordpress.org/plugins/ewww-image-optimizer/) Viewing 8 replies - 1 through 8 (of 8 total) * Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951026) * Hmm, it seems running exec() on both the bundled binaries and the ones your VMS provider installed is producing no output. * The one exception I’m seeing is when it tests for ImageMagick and it does this: * ``` testing case: i at convert convert: Exception raised, terminating tool not found ``` * So I would see if your provider can check your syslog or any other error logs for clues. Also, can you find out what operating system your VPS/VMS is running? And if it is using Apache, Litespeed, or Nginx (or something else)? I see it’s PHP 5.6, so that shouldn’t be a problem (it’s what I use every day for testing). * Thread Starter [Mulen](https://wordpress.org/support/users/mulen/) * (@mulen) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951052) * Hello, thank you very much for your super-fast reply. * This is what I can see in phpinfo: * PHP Version 5.6.14-0+deb8u1 System: Linux replikant1348 3.16.7-ckt20-vch1-amd64# 1 SMP Wed Jan 6 18:21:38 CET 2016 x86_64 _SERVER[“SERVER_SOFTWARE”]: Apache/2.4.10( Debian) * Or I can send you full phpinfo on your e-mail…? * Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951055) * Go ahead and send it via [https://ewww.io/contact-us/](https://ewww.io/contact-us/) * Thread Starter [Mulen](https://wordpress.org/support/users/mulen/) * (@mulen) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951066) * Done * Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951333) * for anyone else with a similar issue, what we know so far is that Mulen’s webhost is suppressing output redirection which EWWW uses to check that the compression tools are functioning properly. I think I’ve just come up with a way to work around this. * Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951371) * [@mulen](https://wordpress.org/support/users/mulen/), the 2.5.8 release was for your particular problem, although it appears I have a small bug (which is already fixed in the dev branch). * Thread Starter [Mulen](https://wordpress.org/support/users/mulen/) * (@mulen) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951376) * Thank you for you reply, but I cannot test if this fix solves my problem because my VMS provider already created some script to overwrite the plugin code to make it work. They told me that the problem was in “incorrect paths” for creating new files when option “Use system paths” was on. So this is probably what you fixed? * Plugin Author [Shane Bishop](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951377) * Yeah, I modified the path checking so that it would test based on the optimization results for a sample file, instead of using output redirection which your provider had blocked. Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘All testing cases failed’ is closed to new replies. * ![](https://ps.w.org/ewww-image-optimizer/assets/icon-256x256.png?rev=1582276) * [EWWW Image Optimizer](https://wordpress.org/plugins/ewww-image-optimizer/) * [Frequently Asked Questions](https://wordpress.org/plugins/ewww-image-optimizer/#faq) * [Support Threads](https://wordpress.org/support/plugin/ewww-image-optimizer/) * [Active Topics](https://wordpress.org/support/plugin/ewww-image-optimizer/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/ewww-image-optimizer/unresolved/) * [Reviews](https://wordpress.org/support/plugin/ewww-image-optimizer/reviews/) * 8 replies * 2 participants * Last reply from: [Shane Bishop](https://wordpress.org/support/users/nosilver4u/) * Last activity: [10 years, 4 months ago](https://wordpress.org/support/topic/all-testing-cases-failed/#post-6951377) * Status: resolved