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

#235 First draft of v3.1 #237

Open
wants to merge 1 commit into
base: next
Choose a base branch
from
Open

#235 First draft of v3.1 #237

wants to merge 1 commit into from

Conversation

pabloelcolombiano
Copy link
Collaborator

No description provided.

@LordSimal
Copy link
Contributor

I do like the new resultset methods 👍

but I am not really sure what the benefit of the select query mocking is...

Maybe its just my usecase but I dont use seeders or any of the old fixture system to create a initial DB state for my tests anymore thanks to this awesome plugin.

Therefore what is the difference between just persiting entities via the factory so a normal e.g. ->get() call inside an integration test fetches it from the DB instead of (basically) mocking the model? just so that the DB layer is extracted and not called? is this so much faster?

@dereuromark dereuromark mentioned this pull request Nov 29, 2023
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.

2 participants