Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to setup PHPUnit 3.5.15 and Zend framework 1.11.10?
    text
    copied!<p>After spending 1 good day I still unable to resolve the following error:</p> <blockquote> <p>Testing Note: PHPUnit was not found in your include_path, therefore no testing actions will be created.</p> </blockquote> <p>This error appears when I create a new Zend-project.</p> <p>What i have tried so far:</p> <ol> <li>Updated Pear to the latest version. </li> <li>changed config to autodiscover as described on the readme of phpunit.</li> <li>Also I changed the include path of my php.ini file to the following: </li> </ol> <blockquote> <p>include_path=".;S:\PHP\PEAR;S:\PHP\PEAR\PHPUnit;S:\Framework\ZendFramework-1.11.10\library;S:\PHP\PEAR\PEAR"</p> </blockquote> <p>However I am still receiving the error.</p> <p>What does work is the commandline phpunit , the correct php.ini is loaded (checked by phpinfo()) so what am I missing?</p> <p><strong>Additional information</strong></p> <pre><code>C:\Users\Dev\Desktop&gt;php --ini Configuration File (php.ini) Path: C:\Windows Loaded Configuration File: S:\PHP\php.ini Scan for additional .ini files in: (none) Additional .ini files parsed: (none) </code></pre> <p>Instalation information:</p> <ul> <li>Apache 2.2.19</li> <li>php 5.3.6 </li> <li>mysql 5.5.15</li> </ul> <p>I did not install xammp or wammp just manual install to learn.</p> <p>php.ini that load :=> <a href="http://pastebin.com/bpqKhF7U" rel="nofollow">http://pastebin.com/bpqKhF7U</a></p> <h2><em>Update!</em></h2> <p>Php include_path is ambiguous the error you receive is because your .zf.ini is wrongly configured (mine was)</p> <p>.zf.ini can be found @ users home folder</p> <p>It looks like this:</p> <blockquote> <p>php.include_path=".;S:\xampp\php\;S:\xampp\php\PEAR;S:\xampp\php\PEAR\PHPUnit"</p> </blockquote> <p>After changing this parameter to the right locations the error did not occur anymore!.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload