-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Cannot run test suite #5402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think you need to install the composer stuff with |
you need to ask composer to install the dev dependencies too (used in the testsuite but not mandatory deps) by adding the |
Information like this should not be hidden in JSON and YAML files. Now I have a different issue:
|
This is weird. I don't find any duplicated class declaration for this test. Could it be possible that phpunit includes the file twice ? |
this is not hidden h 8000 ttp://symfony.com/doc/master/contributing/code/tests.html |
Commits ------- 7ef6295 Removed the unnecessary file include Discussion ---------- Removed the unnecessary file include As of Doctrine 2.2, the ORM annotations can be found by the autoloader directly. This will also avoid breaking the testsuite in case the dev deps have not been installed as the ORM would not be available in this case (the tests relying on the ORM should already be skipped when it is not available). See #5402
True, I did not know about http://symfony.com/doc/master/contributing/code/tests.html. Why? Because I expect this information in a |
@sebastianbergmann Could you send a PR updating the README file with your expected information? |
Less snark, more pull requests maybe, @sebastianbergmann? FWIW, I'd put this into a |
I do not like your attitude, @dzuelke. What you "demand" already happened. |
I do not like your tone, @sebastianbergmann. |
I do not like yours, either. I asked for feedback on PHPUnit 3.7RC. @fabpot replied mentioning an issue with Symfony. To research this issue I need to run the Symfony test suite. I ran into problems, I opened this ticket asking for help. And while others are helping ... you are attacking me for not contributing. |
Right, I'm not helping, I was just the first person who told you how to install the required dependencies (here and on Twitter). All of your comments this PR are unnecessarily passive-aggressive. If you don't see that, then figure out a way to get out of your bubble until you do please. |
Indeed, you helped in the beginning. Sorry that I forgot about that. I overreacted because of your "Less snark, more pull requests maybe" remark. At least to me, such a remark is offensive. I do not use Composer, Symfony, Travis, etc. This is why I ran into the original issue. For me it was clear from the beginning that I would send a pull request once I gathered all the information I needed, that's just what I do. If my comments came across as passive-aggressive or offended in any way: my apologies. |
And finally, did you find a solution for your |
Yes, it was PHPUnit's fault: sebastianbergmann/dbunit@4ca6667 |
@sebastianbergmann, I see that you require a few more Symfony files there, how does that work when we want to test the Yaml component with PHPUnit, wouldn't we test the classes that are in PEAR then? |
The text was updated successfully, but these errors were encountered: