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
Sometimes, I might just want to create a version of my concrete type that is the real object, except that the invocations of functions and the get/set of properties can be verified.
From a quick overview of the architecture, this seems totally feasible. This is because mocks of concrete types are created by Mockingbird via subclassing that concrete type.
Currently, whenever there is no stub of the desired/function/property provided for the mock class, fatalError(self.stubbingContext.failTest(for: invocation)) is called.
But we could also just use the actual implementation with just super call.
The text was updated successfully, but these errors were encountered:
Sometimes, I might just want to create a version of my concrete type that is the real object, except that the invocations of functions and the get/set of properties can be verified.
From a quick overview of the architecture, this seems totally feasible. This is because mocks of concrete types are created by
Mockingbird
via subclassing that concrete type.Currently, whenever there is no stub of the desired/function/property provided for the mock class,
fatalError(self.stubbingContext.failTest(for: invocation))
is called.But we could also just use the actual implementation with just
super
call.The text was updated successfully, but these errors were encountered: