This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This one occurs on: Product Version: NetBeans IDE 6.7 RC2 (Build 200906042131) Java: 1.6.0_13; Java HotSpot(TM) Client VM 11.3-b02 System: Windows Vista version 6.0 running on x86; Cp1254; tr_TR (nb) I'm trying to run tests by right clicking on project and selecting tests (Or right clicking on a test file under the "Test Files" folder and select "Run" command). Everything goes ok and test results are shown. After I add some dependencies on my classes and unit test files can't find the newly added file and output pane shows an error like this with a call stack: Warning: require_once(Company/A/B.php): failed to open stream: No such file or directory in C:\www\project\tests\lib\Company\A\BTest.php on line 4 File lib/Company/A/B.php is like: <?php //As lib folder is defined on the include_path on the bootstraps, there is no need to put lib folder. require 'Company/A.php'; class Company_A_B extends Company_A { //Some definitions are here. } Test file is like: require 'Company/A/B.php'; class Company_A_BTest extends PHPUnit_Framework_TestCase { //Testing here... } So when I encounter an error on the ouput window like failed to open stream, Test Results pane shows the results of the last successfully (I do not mean a test with 100% success but a test without any php errors.) executed tests. Instead It should show that an error occurred or something like that. By the way, is there a way to define the include_path for running tests? I mean, should it work well if I write an AllTests.php file and add some bootstraps, because when you select Tools -> Create PHPUnit Tests, it also adds some relative path includes. Instead It would be cool to define a general include path for the running tests. The PHP Include Path you define on the project properties, does not apply for the tests you run. Perhaps a new issue must be opened for this or this is a bug? I'm not sure if the sub component part is correct. You might move this to the ui or something. thanks
Fixed a while ago, thanks for reporting. *** This issue has been marked as a duplicate of 166529 ***