You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove the Fake{Service}Request::class to simplify testing.
Find a way to make TEST_MODE mock the response without the Fake{Service}Request::class.
What problem will this solve? 🔥
Removes redundancy to the process because the request shall always remain the same, what is meant to be mocked is the response. This led developers to simply return a new instance of the Fake{Service}Response::class by passing it the data it had received. (Others would put the response mocking logic in the request contrapart, but that should also be considered "wrong", that logic should live within the Fake{Service}Response::class.
Which version(s) should this be pointed at?
1.x
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like.✈️
Fake{Service}Request::class
to simplify testing.TEST_MODE
mock the response without theFake{Service}Request::class
.What problem will this solve? 🔥
Removes redundancy to the process because the request shall always remain the same, what is meant to be mocked is the response. This led developers to simply return a new instance of the
Fake{Service}Response::class
by passing it the data it had received. (Others would put the response mocking logic in the request contrapart, but that should also be considered "wrong", that logic should live within theFake{Service}Response::class
.Which version(s) should this be pointed at?
1.x
The text was updated successfully, but these errors were encountered: