angular-testing

You can unit test Angular signal-based components with Vitest by using Angular TestBed to drive signals directly and assert derived outputs from computed and effect behaviors. This approach validates state transitions and DOM rendering deterministically.

Yes, Angular v20 supports native Vitest testing through the @angular/build:unit-test runner. This allows you to configure TestBed for standalone components without needing Karma or Jasmine as a dependency.

The best way to mock HTTP interactions in Angular Vitest tests is using HttpTestingController. It provides deterministic verification of HTTP requests and responses, ensuring your service mocking and HTTP flows are validated accurately.

You test OnPush change detection in Angular components by configuring TestBed to handle standalone patterns and signal updates. This ensures your tests properly trigger and verify the component's rendering behavior during async timing operations.

Yes, you can test computed signals and effects without Jasmine by using Vitest. The skill provides modern mocking patterns that let you replace services with Vitest mocks and verify signal updates and UI outcomes directly.

Cypress and Playwright are excluded because they are E2E tooling, whereas this approach targets unit and integration testing. Using Vitest with TestBed provides isolated, fast-running tests for signal-driven components rather than full browser automation.