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.
Created attachment 108642 [details] Screenshots in archive Hello, developers. I am using Zend Framework for my projects and found out this oddness: In my project I want to test "/library" folder. Unit tests placed separately in "/test_library" folder (image 0). When I using PHPUnit from command line all going ok (55 tests, image 1). When I using NetBeans it ignores my "phpunit.xml" and runs tests in both "/test_library" and "/test_application" folders (56 tests, image 6). I don't know why this happening.
Hi, we are now working on the test groups. See more here http://wiki.netbeans.org/PHPUnitTestGroups. It will solved the problem. Now you can define your test suite through use custome test suite field.
I'm not sure Test Groups solve the problem as this looks like an additional feature. The expected behavior (or at least what I expect) would be that, given the XML configuration, the Test folders would load dynamically and not ask for a specific one. In other words: - The test action (alt + F6) would run the command "phpunit -c path/to/config.xml" - If the config.xml is configured, don't ask for a single test folder - Load test folders & files according to the rules and patterns described in the config.xml I'm currently using Symfony 2, where there is a test folder for each bundle (like a plugin/module in Symfony 1. There is a default php unit configuration file in Symfony 2, yo can see it here: https://github.com/symfony/symfony-standard/blob/master/app/phpunit.xml.dist Regards, David
Well, hard to say what to do now. NetBeans uses its own TestSuite [1] which runs the "right" tests (reasons for having own suite can be found in issue #167519). It means that all tests are added if one invokes Test action on project node and also runs just a single file if one runs just one test file. This is the expected behavior, I would say, for most of the users. If a project has PHPUnit XML configuration set, it is definitely not ignored, it is passed to the PHPUnit script. Apparently, the tests in the test suite has precedence over tests in the XML configuration. Not sure how/whether this problem can be fixed. Any ideas? Possible work arounds: - provide your own test suite (in Project Properties, category PHPUnit) - use PHPUnit test groups - any other ideas? Thanks for reporting and any ideas. [1] <nb-install-dir>/php/phpunit/NetBeansSuite.php
Thank you for your answers. I am glad to now that somebody thought about this trouble. But I solved this oddness by totally separating /library from /application So Library and Application are two different projects with the different unit tests. /library/tests /application/tests
(In reply to comment #4) > Thank you for your answers. > I am glad to now that somebody thought about this trouble. Nothing to thank for. > But I solved this oddness Great to hear! Closing as WONTFIX (it is more appropriate) but feel free to reopen and provide your ideas how this issue could be solved. Keeping the current behavior makes more sense to me. Thanks.