Skip to content
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

Refactor PHPUnit mock assertions to use Mockery #1756

Open
phavekes opened this issue Nov 29, 2024 · 0 comments
Open

Refactor PHPUnit mock assertions to use Mockery #1756

phavekes opened this issue Nov 29, 2024 · 0 comments

Comments

@phavekes
Copy link
Member

This issue is imported from pivotal - Originaly created at Nov 25, 2019 by Michiel Kodde

EngineBlock is a project that spans several decades of PHP testing developments. And you can see that from the testing tools utilized. For example we use 3 different mock testing tools.

  1. PHPUnit Mock
  2. Mockery
  3. Prophecy

This is not a bad thing per se as each tool has its pro's and cons. This story should identify which tool is used for what reason. And when opportune, rewrite the test to use the mock testing tool of our choosing.

Left-over from:
#168924689

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

No branches or pull requests

1 participant