Is there a way to name mocks?

[parisBrentas]

Sometimes it happens that a test is failing and the error I'm getting is something along the lines of

Error: Didn't expect mock.someProperty to be accessed.

If you expect this property to be accessed then please
set an expectation for it.

There are no remaining unmet expectations.

However, it could be that the access of that property is happening in an array, so it's hard to tell which mock has the problem. I usually get around that by adding some debug logging and rerunning the test, however it could be much quicker if I could somehow name the mocks, so that I'd get something like this instead:

Error: Didn't expect myMockName.someProperty to be accessed.

Is there a way to do that? I tried when(() => myMock.toString()).thenReturn("myMockName").anyTimes() but that didn't work.

Thanks for your help.

[NiGhTTraX]

Hey, @parisBrentas. There's currently no way to name mocks, but the feature is planned! I'm thinking something along the lines of mock<T>("name"). I can't promise an ETA right now, but it's at the top of my backlog.

[NiGhTTraX]

@parisBrentas I released 9.2.0 with support for naming mocks with mock<T>({ name: 'CustomName' })!

[parisBrentas]

Thank you so much, this will make debugging much easier!