-
-
Notifications
You must be signed in to change notification settings - Fork 641
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
Rewrite Mockery calls to Prophecy #2217
Comments
@mvriel As prophecy integration in PHPUnit is deprecated from version 9 and will be removed in version 10, do you still want to migrate to Prophecy or would it make sense to migrate to PHPUnit's built-in mocking library? |
However prophecy is removed from the phpunit core I think it is still superior to the phpunit mocks. I tried recently to improve the phpunit mocks and I was a bit disappointed about the internals. There are much edge cases which are not nicely covered. So yes I do still prefer to migrate to prophecy. |
As I see in the issue description the point of this task was as well to simplify dependencies of phpDocumentator. If we got with |
Since phpdocumentor libraries are used by phpunit, mockery and prophecy it is always a pain to install more dependencies via composer. We will need to find a way to install prophecy via phar like we do with phpunit right now. Removing mockery is a step forward. Phars can be scoped which prevents issues. |
I've opened two more PRs and if those get merged what will be left to do is:
|
Many phpDocumentor tests use Mockery as a mocking/stubbing library but with the advent of prophecy, we are now working to adopt that as our library or method of choice.
To reduce the number of dependencies that we have and simplify our tests, we need all mockery uses to be rewritten to use prophecy.
Any help here is much appreciated. Please issue a PR per test as that will help in reviewing and merging.
The text was updated successfully, but these errors were encountered: