MockProvider does not call promise's callback about malibu HOT 4 CLOSED

I ended up making sure the Networking instance doesn't deallocate in the tests by retaining the object as follows:

func execute<T>(request: T,
                    mockProvider: MockProvider<T>? = nil) -> NetworkPromise where T: RequestConvertible {
        let networking = Networking<T>(mode: .async, mockProvider: mockProvider)
        return networking.request(request).validate().always({ _ in _ = networking })

Thanks for the help!

from malibu.

You could make networking an instance var in your test and then inject it to APIFetcher for example.

from malibu.

Sorry, due to oversimplifying the real case got lost :)

Here is a gist containing the actual case.

The execute<T>(request: T) -> NetworkPromise is required by the protocol, and relied upon by my services.

If I want to test a service, I thus mock the APIClient in them, and the Networking instance is configured in the APIMockClient, since in the real world, it is also responsible for configuring the Networking's headers and authentication token.

Now, in a real world example this approach works:

    func execute<T>(request: T,
                    mockProvider: MockProvider<T>? = nil) -> NetworkPromise where T: RequestConvertible {
        let networking = Networking<T>(mode: .async, mockProvider: mockProvider)
        networking.configureHeaders()
        networking.configure(token: userManager.accessToken)

        return networking.request(request).validate()

So I am a bit confused here, as the exact same approach is used.

from malibu.

When I use Malibu I usually keep a reference to Networking class somewhere. In your case it's not easy to find a workaround without changing the code. It would be easier if you had a generic APIMockClient with networking being an instance var, but it doesn't follow func execute<T>(request: T) method from APIClientMethods protocol.

from malibu.