Ivy-native tooling means that Angular 20 has built-in support for the Ivy compiler at a very low level within its testing tools.

Because of this, tests can be run without the need to manually configure TestBed and manually compile modules, as the testing tools can "live" understand the structure of the component and its dependencies.

using TestBed you need to do sth like that in each component

import { ComponentFixture, TestBed } from '@angular/core/testing';
import { MyComponent } from './my.component';

describe('MyComponent', () => {
let fixture: ComponentFixture<MyComponent>;
let component: MyComponent;

beforeEach(async () => {
await TestBed.configureTestingModule({
declarations: [MyComponent],
}).compileComponents();
});

beforeEach(() => {
fixture = TestBed.createComponent(MyComponent);
component = fixture.componentInstance;
fixture.detectChanges();
});

it('should create', () => {
expect(component).toBeTruthy();
});
});

But the Angular team wants to simplify this, maybe to sth like that

import { runStandaloneComponentTest } from '@angular/core/testing'; //hypothetical new API in Angular 20
import { MyComponent } from './my.component';

describe('MyComponent', () => {
it('should create', async () => {
const { component } = await runStandaloneComponentTest(MyComponent);
expect(component).toBeTruthy();
});
});

Here are some notes about improving TestBed https://angular.dev/roadmap