chore: upgrade to Karma 3.x and Jasmine 3.2.x

Open Splaktar opened this issue 7 years ago • 2 comments

Bug, enhancement request, or proposal:

Proposal

Steps to reproduce the issue:

https://github.com/angular/material/blob/v1.1.10/package.json#L62-L71

What is the expected behavior?

We depend upon recent versions of Karma and Jasmine.

What is the current behavior?

Currently we depend on very old versions of Karma and Jasmine.

What is the use-case or motivation for changing an existing behavior?

This Karma version has some high security vulnerabilities. It also makes it harder to track down test failures or issues like https://github.com/angular/material/issues/11487 when we're based on old versions of these testing libraries.

Which versions of AngularJS, Material, OS, and browsers are affected?

AngularJS: 1.7.x
AngularJS Material: 1.1.10
OS: all
Browsers: all

Is there anything else we should know? Stack Traces, Screenshots, etc.

[x] Karma updated
[ ] Jasmine updated

Oct 17 '18 00:10 Splaktar

PR https://github.com/angular/material/pull/11494 updates Karma to the latest.

Updating Jasmine won't be so easy as there are a lot more breaking changes.

Oct 26 '18 01:10 Splaktar

Related PR https://github.com/angular/material/pull/12103 updates to Karma v6.

Jun 03 '21 21:06 Splaktar