`ng new` does not allow creation without any testing

[LoganDark]

Maybe I don't want or need tons and tons of unnecessary testing frameworks like Protractor, Karma, Jasmine, etc.

What do you think of an option to skip these? There's only an option to omit spec files at the moment, but a flag to skip all testing would be great for, for example, developers who want to use different testing frameworks, or (like me) no testing frameworks. (I prefer to do the testing by hand)

Right now, my solution is:

rm -rf e2e/ src/karma.conf.js src/*.spec.* tslint.json src/tslint.json .editorconfig src/test.ts
npm un --save-dev protractor karma karma-chrome-launcher karma-coverage-istanbul-reporter karma-jasmine karma-jasmine-html-reporter jasmine-core jasmine-spec-reporter @types/jasmine @types/jasminewd2 tslint codelyzer

It would be nice not to have these files generated in the first place and added to package.json.

[alexeagle]

Automated testing of some sort is pretty integral to the Angular ecosystem. You're free to do as you like of course, but I suspect we wouldn't add this option since we want to keep most users on the recommended path.
After you delete the files, are you done? Or does the CLI keep re-adding them?

[LoganDark]

Yeah, I'm done. I would be pretty pissed if the CLI kept adding them.

In my opinion, manual testing allows me to get more of a feel for how the user might experience it, but that's just my personal opinion.

[hansl]

We used to have a --minimal option but it's been disabled until we figure out what it means to have a minimal project. Once that option is re-enabled, that's probably what you're looking for.

[hansl]

I opened #11904 to track re-enabling the flag.

[LoganDark]

This command removes 14 vulnerabilities and almost 200 packages:

npm un -D codelyzer jasmine-core jasmine-spec-reporter karma karma-chrome-launcher karma-coverage-istanbul-reporter karma-jasmine karma-jasmine-html-reporter protractor @types/jasmine @types/jasminewd2 tslint

Useless bloat.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}