Skip to content

[PHPUnit] ignore E_USER_DEPRECATED notices #12756

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

Merged
merged 1 commit into from
Nov 29, 2014

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Nov 29, 2014

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR

This updates the PHPUnit configuration files that have not been
updated in #12705.

This updates the PHPUnit configuration files that have not been
updated in symfony#12705.
@fabpot
Copy link
Member

fabpot commented Nov 29, 2014

Thank you @xabbuh.

@fabpot fabpot merged commit dcc1103 into symfony:2.7 Nov 29, 2014
fabpot added a commit that referenced this pull request Nov 29, 2014
This PR was merged into the 2.7 branch.

Discussion
----------

[PHPUnit] ignore E_USER_DEPRECATED notices

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        |

This updates the PHPUnit configuration files that have not been
updated in #12705.

Commits
-------

dcc1103 [PHPUnit] ignore E_USER_DEPRECATED notices
@xabbuh xabbuh deleted the phpunit-ignore-deprecation-warnings branch November 29, 2014 15:28
@stof
Copy link
Member

stof commented Dec 4, 2014

The drawback of this is that we hide the fact that normal usage of Symfony 2.7 triggers deprecation notices. What we did in Symfony 2.2 was to explicitly ignore the deprecation notices in tests relying on BC layers, but not in others.

@weaverryan
Copy link
Member

@stof That makes more sense to me too, but that would be a bit of work to accomplish (since these will be tests in many places). But if we did that work, we would also exactly know which tests are testing deprecated behavior.

Do you have an example of where/how we did this in 2.2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants