angular-cli: Generate .spec files for already existing components / services

I created a pull request implementing the feature https://github.com/angular/devkit/pull/938 .

Allows to create specs for component, directive, module, service, pipe, guard (based on corresponding schematics) by running

ng g spec my-component.component

or as a file (more convenient because files normally already exist and it is easier to point to the file)

ng g spec /my/project/app/src/blah/my-component.component.ts

Please review.

Yes generating a spec file after we already generated our component and modified it. ng g component your-component --spec-only

A small addition: would be incredibly perfect if the just created .spec.ts files would have mocks for the every injected item according to the methods / properties that are used in the unit being tested 😃

I’d like to add my vote for this. Even if it was only able to create the “[object] works!” type test, it would still save on boilerplate.

I realize this thread is a bit dated, however I’ve just run into this myself (wishing for a ng g spec type of functionality). That said, if anyone else runs across this and is looking for a simple way to do this, I’ve found this project to fill the hole for now https://github.com/allenhwkim/ngentest

Something I do is… generate component COMPONENT-NAME --force then in GIT revert the items that got overwritten

As an outcome of the pull request: the custom schematic as a standalone library ngx-spec. Please check and share your feelings there.

@Brocco I leave the thread open as a reference for the future RFC / standard.

+my whole dev team

+1 I think this should be possible without installing a additional node package

For anyone still looking for a solution to this: https://www.npmjs.com/package/angular-spec-generator

This seemed to work fairly well for me.

What I do to generate the spec file for an already existing component:

ng generate component [name]

And then answer “no” to the “Overwrite …” questions regarding already existing, non-spec, files.

EDIT: this is not possible in the current version (1.6.0) of angular-cli, as it would prompt the component already exists and would not generate any file.

I found I wanted to do this. In the end I just generated a new component with a spec called something very similar to the real component, then renamed the spec, search & replaced the content and deleted the new component.

+1

So, it’s a misdocumented feature then? @Brocco can you confirm it’s the right way to do stuff?