-
Notifications
You must be signed in to change notification settings - Fork 368
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
Stubbing / mocking search with minitest #654
Labels
Comments
Well, it is a good idea but not implemented yet, unfortunately. You may try to hack into |
Vitalina-Vakulchyk
added a commit
that referenced
this issue
May 6, 2021
Vitalina-Vakulchyk
added a commit
that referenced
this issue
May 6, 2021
Vitalina-Vakulchyk
added a commit
that referenced
this issue
May 6, 2021
Vitalina-Vakulchyk
added a commit
that referenced
this issue
May 7, 2021
Vitalina-Vakulchyk
added a commit
that referenced
this issue
May 7, 2021
Vitalina-Vakulchyk
added a commit
that referenced
this issue
May 7, 2021
Vitalina-Vakulchyk
added a commit
that referenced
this issue
May 7, 2021
Vitalina-Vakulchyk
added a commit
that referenced
this issue
May 14, 2021
cyucelen
pushed a commit
to cyucelen/chewy
that referenced
this issue
Jan 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to find an existing thread on this or a Google Group for the current gem, but couldn't find one.
I'd like to be able to stub / mock searches without having to use webmock.
The current minitest test helper is only for testing index changes, but not mocking searches.
I'd ideally also like the ability to test that a search was not done.
Any recommendations on how to handle this? Thank you in advance.
The text was updated successfully, but these errors were encountered: