Make ng test work #30
Comments
|
@mvollebregt why wont you create a PR for this seems like you already know what the solution is, amd see if they agree with it for a merge. |
|
I had a short look at it before, but I had some trouble finding out how the schematics worked. I'll see if I have some more time later to dive into that. In the meanwhile, I just wanted to explain the improvement, in case someone happened to be able to fix it easily. |
schuchard
added a commit
that referenced
this issue
Sep 2, 2020
Add support single application projects and workspaces with apps and libraries. ## Jest runner Replace the direct reliance on [`jest-preset-angular`](/~https://github.com/thymikee/jest-preset-angular) and package json scripts in favor of [`angular-builders/jest`](/~https://github.com/just-jeb/angular-builders/tree/master/packages/jest). This provides the ability to run tests with `ng test` This should address #30 #28 #22 #11 It better positions us to support #1 ## Jest types Update each projects `tsconfig.spec.json` to configure the `jest` types while removing `jasmine` This should address #24 #14 ## Other Non-user facing changes - refactor development scripts from `package.json` to TS file - create 2 sandboxes (single app and workspace with app and lib) - test both sandboxes during CI - add MIT license - add prettier
|
Please try |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
This is an awesome schematic. It would be even more awesome, if you could run the jest specs by entering
ng test. After adding the jest-schematic, ng test does not run the tests anymore.Describe the solution you'd like
Make the jest-schematic:
npm i -D jest @types/jest @angular-builders/jest)@angular-devkit/build-angular:karmawith@angular-builders/jest:runThe text was updated successfully, but these errors were encountered: