It seems [email protected] requires jasmine-core@">=3.5" but you have [email protected].

In package.json, change jasmine-core to 3.5.0 or greater and run an npm install again. Maybe you should also try deleting node_modules and doing a fresh install.

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)

The problem is that in Angular 13 they introduced a new optimization feature for tests:

From https://blog.angular.io/angular-v13-is-now-available-cce66f7bc296

We’ve made some important improvements to TestBed that now does a better job of tearing down test modules and environments after each test. The DOM is now cleaned after every test and developers can expect faster, less memory-intensive, less interdependent, and more optimized tests.

To opt out, I needed to insert this code to every TestBed:

beforeEach(() => {
    TestBed.resetTestEnvironment();
    ...
    TestBed.configureTestingModule({
        declarations: [TestComp],
        teardown: { destroyAfterEach: false } // true by default after Angular 13
    });
});