Is it possible to mock an interface or abstract class inside a service?

[cesalberca]

I'm trying this with no results:

import { WhoAmIQry } from './who-am-i.qry'
import { createServiceFactory, SpectatorService } from '@ngneat/spectator/jest'
import { ProfileMother } from '../../../../../apps/webapp/src/tests/mothers/profile-mother'
import { UserRepository } from '../domain/user-repository'

describe('WhoAmIQry', () => {
  let spectator: SpectatorService<WhoAmIQry>
  const createService = createServiceFactory({
    service: WhoAmIQry,
    providers: [
      {
        provide: UserRepository,
        useValue: {},
      },
    ],
    mocks: [],
  })

  beforeEach(() => (spectator = createService()))

  it('should get the profile', async () => {
    const userRepository = spectator.inject(UserRepository)
    userRepository.profile.mockReturnValue(Promise.resolve(ProfileMother.jane()))

    const profile = await spectator.service.internalExecute()

    expect(profile).toEqual(ProfileMother.jane())
  })
})

This is the code I want to test:

import { Injectable } from '@angular/core'
import { Query } from '../../../../../apps/webapp/src/app/core/use-case/query'
import { Profile } from '../domain/profile'
import { UserRepository } from '../domain/user-repository'

@Injectable({
  providedIn: 'root',
})
export class WhoAmIQry extends Query<Profile> {
  constructor(private readonly userRepository: UserRepository) {
    super()
  }

  internalExecute(): Promise<Profile> {
    return this.userRepository.profile()
  }
}

[grosch]

I think what you want is to put UserRepository into mocks and get rid of the providers altogether.

[cesalberca]

The thing is that UserRepository is an abstract class. If I do that I get the following error:

 Type 'typeof UserRepository' is not assignable to type 'Type<any>'.
      Cannot assign an abstract constructor type to a non-abstract constructor type.

[grosch]

Yah, you can't test abstract class directly. For that, just make a fake wrapper:

class TestUserRepository extends UserRepository {
    // Implement all abstract requirements
}

And then just use the TestUserRepository everywhere.

[cesalberca]

Aaah, too bad there is no direct support for this. Is this feature in the roadmap?