Schematics for ngMocks

[JsantosDK]

Schematics for ngMocks

Author: @JsantosDK

Goal

The primary goal is to avoid the current need to remake the initial setup that is created via the @angular/cli.

Current Status:

Discussing a proposal for the schematic for Services.

Conclusion

The MVP for this PR to be considered complete is:

• A schematic for services;
• A schematic for pipes;
• A schematic for directives;
• A schematic for components;
• Updating the scripts to allow for the building of the schematics project;
• Updating the build to expose the schematics;
• Meeting quality code standards;

Linked tickets

• PR feat: adds schematics for service #9945;
• Starts the development of Feature Request: Replace Angular Testbed based spec schematics #6293;

[JsantosDK]

Proposal

Consider a service to be created with the name FooBar, then the schematics should create the following spec file:

import { MockBuilder,MockedComponentFixture, MockInstance, MockRender, } from 'ng-mocks';

import { FooBarService } from './foo-bar.service';

describe('FooBarService', () => {
  let service: FooBarService;
  let fixture: MockedComponentFixture<FooBarService>;

  MockInstance.scope();
  
  beforeEach(() => MockBuilder(FooBarService));

  beforeEach(() => {
    fixture = MockRender(FooBarService);
    service = fixture.point.componentInstance;
  })

  it('should be created', () => {
    expect(service).toBeTruthy();
  });
});

Issues

1. It does not follow the current documentation on how to write tests or provider of a component;
2. It assumes that MockInstance.scope() is always wanted;
3. It assumes ngMocks.faster() and ngMocks.guts() are never wanted;
4. It uses the beforeEach testing pattern, which is not the best with ngMocks, especially when there is a need to override the MockInstance of a service in a particular it or describe. The setup pattern or a ngMocks native pattern might be more appropriate;

[JsantosDK]

@satanTime any news on this?