Mock static methods

[nagrock]

Mock static methods

[MatejSkrbis]

@leegee This library is no longer maintained. I like it but there are no updates from the author and he didn't give access to anyone else to update the documentation or the code. I don't know what is the correct way, but you could use spy instead of mock.

class Foo {
    static sayHello(): string {
        return 'Nop';
    }
}

const spyFoo = spy(Foo);

when(spyFoo.sayHello()).thenReturn('Yes');

console.log(Foo.sayHello()); // Will print out Yes

[MatejSkrbis]

You can try something like this:

class Foo {
    static sayHello(): void {
        console.log('hello')
    }
}

const mockFoo = mock<typeof Foo>(Foo);
mockFoo.sayHello(); // no more error

This is how I get around this problem.

[SatoshiKawabata]

@MatejSkrbis
I tried your code and use when.

const mockFoo = mock<typeof Foo>(Foo);
mockFoo.sayHello(); // no more error
when(mockFoo.sayHello());

But I got this error. Could you run the test without error?

TypeError: mockFoo.sayHello is not a function

[MatejSkrbis]

@SatoshiKawabata

@MatejSkrbis
I tried your code and use when.

const mockFoo = mock<typeof Foo>(Foo);
mockFoo.sayHello(); // no more error
when(mockFoo.sayHello());

But I got this error. Could you run the test without error?

TypeError: mockFoo.sayHello is not a function

I've tried it and there is no error on my side.
I'm using latest packages of mocha and ts-mockito ("mocha": "8.2.1", "ts-mockito": "2.6.1", "typescript": "4.0.5")

[kmannislands]

Mocking of static methods would be even nicer but the current state is that if the class has any static methods, they cannot be called on the mock version (rendering this package unusable in my case)

ie:

class Foo {
  static sayHello() {
    console.log('hello')
  }
}

const mockFoo = mock(Foo);
mockFoo.sayHello() // error TS2339: Property 'sayHello' does not exist on type 'Foo'.

[IonelLupu]

Any updates on this?

[leegee]

The above example works for me, but I can't get it working IRL, where the static method to be mocked is in a dependency of the object being tested: could the documentation be updated to include the correct way to handle such a scenario?

[leegee]

That was kind of you, thank you.