I looked more at the angular.json file in the working new Angular 15 application. I had to do 2 things:

1. remove the "main"
2. change the "polyfills"

Changed from:

   "options": {
     "main": "src/test.ts",
     "polyfills": "src/polyfills.ts",
     "tsConfig": "tsconfig.spec.json",

Changed to:

   "options": {
     "polyfills": [
       "zone.js",
       "zone.js/testing"
     ],
     "tsConfig": "tsconfig.spec.json",

Short answer: no. Karma is deprecated and is not accepting new features or general bug fixes:

The web testing space has evolved significantly in the 10+ years since Karma's creation. The web landscape looks very different today and new patterns and tools have emerged in the ecosystem. New test runners offer more performant alternatives, and Karma no longer provides clear unique value.

Based on the current state of the web testing ecosystem, we have made the hard decision to deprecate Karma.

We know Karma is used particularly commonly in the Angular ecosystem, so Angular is adding Jest and Web Test Runner support to provide a migration path off of Karma. See the Angular blog for more details.

Critical security issues in Karma will still be triaged and fixed as necessary. This will continue until 12 months after Angular CLI's Web Test Runner support is marked stable.

For those outside Angular looking to migrate off Karma, both Web Test Runner and jasmine-browser-runner provide browser-based unit testing solutions which can be used as a direct alternative. Jest and Vitest also provide Node-based alternatives.

Recommending alternatives is strictly outside the scope of StackOverflow, but hopefully the above provides some pointers.

There has been some testing logic upgrades in 15, You can find the comprehensive steps on V15 below

Angular Upgrade Guide V14 -> V15

Have you done the below steps?

• Update instances of Injector.get() that use an InjectFlags parameter to use an InjectOptions parameter. The InjectFlags parameter of Injector.get() is deprecated in v15. Read further
• Update instances of TestBed.inject() that use an InjectFlags parameter to use an InjectOptions parameter. The InjectFlags parameter of TestBed.inject() is deprecated in v15. Read further

Also check if the correct versions are set for karma and jasmine below is a stackblitz of a new project using angular 15, the versions should match, if you have a different version of angular 15, then first do npm i -g @angular/cli@<<version>> then do ng new test, then check the versions of karma and jasmine and verify all versions are the same!

"@angular-devkit/build-angular": "^15.2.10",
"@angular/cli": "~15.2.10",
"@angular/compiler-cli": "^15.2.0",
"@types/jasmine": "~4.3.0",
"jasmine-core": "~4.5.0",
"karma": "~6.4.0",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage": "~2.2.0",
"karma-jasmine": "~5.1.0",
"karma-jasmine-html-reporter": "~2.0.0",
"typescript": "~4.9.4"

Stackblitz Demo

You can know the jasmine version you are using by running the following Spec:

describe('Test to print out jasmine version', function() {
  it('prints jasmine version', function() {
    console.log('jasmine-version:');
    console.log(jasmine.version || (jasmine.getEnv().versionString && jasmine.getEnv().versionString()));
  });
});

and then checking the karma output in your console or browser. It should be something like:

LOG: 'jasmine-version:'
LOG: '2.3.4'

The jasmine library is included in the jasmine-runner plugin as you've already found out. You can find the exact place where this file is loaded in the source code of the plugin: https://github.com/karma-runner/karma-jasmine/blob/master/lib/index.js (line 7)

You can try to modify the plugin so that an upgrade is possible and send a pull request to karma (see http://karma-runner.github.io/0.10/dev/contributing.html)