Mock RepositoryService Test about crud HOT 7 CLOSED

Here is what I came up with:

import { Test, TestingModule } from '@nestjs/testing';
import { getRepositoryToken } from '@nestjs/typeorm';
import { AnnotationsService } from './annotations.service';
import { AnnotationEntity } from '../entities/annotation.entity';

describe('AnnotationsService', () => {
  let service: AnnotationsService;

  beforeEach(async () => {
    const module: TestingModule = await Test.createTestingModule({
      providers: [
        AnnotationsService,
        {
          provide: getRepositoryToken(AnnotationEntity),
          useValue: {
            metadata: {
              columns: [],
              relations: [],
            }
          }
        }
      ],
    }).compile();

    service = module.get<AnnotationsService>(AnnotationsService);
  });

  it('should be defined', () => {
    expect(service).toBeDefined();
  });
});

This is far from perfect and I can't imagine keeping this kind of mock if I want to perform more complex tests. I think it is worth the pain to also ask this question to the TypeORM guys.

from crud.

Same issue here.
This is where the exception is thrown: https://github.com/nestjsx/crud/blob/master/src/typeorm/repository-service.class.ts#L31

from crud.

@zMotivat0r could you provide any instructions on how to test a RepositoryService?
Also, I'm wondering if the RepositoryService.{entityColumnsHash,entityRelationsHash} abstraction layer is really needed?

from crud.

So basically it's the same as you would mock TypeORM Repository in your project without using crud lib. I don't think that mocking it should be a part of this lib.

from crud.

Yes, I also think this issue is more related to TypeORM than to this library.

from crud.

There are apparently two main ways of doing things. See https://stackoverflow.com/questions/52797727/process-of-testing-with-typeorm-and-nestjs-and-jest-using-mocks for a good introduction.

from crud.

thanks it's works now with metadata field :)

from crud.