refactor(@angular-devkit/schematics-cli): use latest version of jasmine for schematics

[santoshyadavdev]

Schematics project install jasmine, but its of very old version.

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Currently jasmine version installed is very old

Issue Number: N/A

What is the new behavior?

Install the latest version of jasmine

Does this PR introduce a breaking change?

• Yes
• No

Other information

[JeanMeche]

Hi Santosh, check out our commit message guidelines for the linting rule to pass 😉

[santoshyadavdev]

Hi Santosh, check out our commit message guidelines for the linting rule to pass 😉

Sorry raised a PR after years, let me fix this

[santoshyadavdev]

@JeanMeche should be ok now. But I was wondering if we should keep jasmine, my first thought was to remove it, but we can discuss and decide.

[santoshyadavdev]

The error looks not related to this PR

[rainerhahnekamp]

In May, the Angular Robot tried to upgrade and got rejected because Jasmine 5 doesn't run on Node 16 anymore: angular/angular#50284

@santoshyadavdev I am all ears regarding dropping Jasmine. What are your reasons?

[santoshyadavdev]

Ahh makes sense for build failure. For jasmine,I mean it's a starter project, I think devs should chose the tool they like. And most of the project I have seen use jest, does that make sense?.

…

On Sat, 19 Aug 2023, 13:49 Rainer Hahnekamp, ***@***.***> wrote: In May, the Angular Robot tried to upgrade and got rejected because Jasmine 5 doesn't run on Node 16 anymore: angular/angular#50284 <angular/angular#50284> @santoshyadavdev <https://github.com/santoshyadavdev> I am all ears regarding dropping Jasmine. What are your reasons? — Reply to this email directly, view it on GitHub <#25694 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC27EBYI7IYZENGFO3YQYJLXWCR5VANCNFSM6AAAAAA3VRTKQM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rainerhahnekamp]

Understood.

I'd like to add that there are also reasons to use Jasmine instead of Jest:

• Sound testing framework: The Angular team uses Jasmine as well. I guess the same is true for the rest of the Google Angular applications. In general, though, I also confirm that the majority outside of Google uses Jest.
• Legacy Code: Especially Angular CLI-based applications that started out with Jasmine and already have a good testing code base might not have the need to switch to Jest.
• Full browser environment: Certain types of tests need a full browser environment. Jest runs on JSDOM, which is not a browser and doesn't give you that kind of support.
• Better support for asynchrony: There are some edge cases where Jest fails on asynchrony management. Jasmine doesn't have those obstacles.
• Better Integration: Maybe the main argument for Jasmine. Jasmine is integrated into the build system of Angular. Because of that, Jest had many performance issues with ESM.

Either way, official support for Jest will finally come to Angular as well. There is already experimental support since version 16. So devs will be able to choose.

If you are interested in more, I've written a whole article about it: https://dev.to/this-is-angular/angular-testing-in-2023-past-present-and-future-j5m

[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.}