CodeVetter · Repo Unpack · Testing signals
angular/angular
Tests and CI were inspected, not executed; a test's existence is not a passing result. The framework uses Bazel targets with Jasmine and browser test suites, while DevTools also has Cypress and Zone.js has multiple runner integrations. Inspected assertions cover HTTP semantics, XSRF boundaries, history state, compiler behavior, route tables, and settings migration. Coverage observations are limited to the files read and do not establish whole-repository coverage or absence.
- Verification status is source inspection only: the declared test commands and CI jobs were read, but no test, build, benchmark, or workflow was executed and no passing result is asserted.
- The HTTP test BUILD declares zoneless_jasmine_test named test and zoneless_web_test_suite named test_web, sharing TypeScript tests and TestBed dependencies.
- FetchBackend tests use TestBed, an injected MockFetchFactory, and Jasmine spies to assert immediate Sent events, subscription laziness, and retry behavior.
- Fetch tests assert download event sequencing, response headers, partial text, and rejection of upload-progress requests.
- XSRF tests distinguish GET/HEAD from POST, absolute and protocol-relative cross-origin requests from same-origin requests, and preservation of existing headers.
- SearchHistory tests assert storage serialization, ordering, deletion, favorites, and the recent-history limit using MockLocalStorage; their timestamp ordering helper uses real short timeouts.
- Adev routing smoke tests reject external and malformed route paths and load representative lazy components; despite the 'prerender' name, those assertions do not render a complete page or exercise real content fetching.
- ngtsc behavioral tests run through runInEachFileSystem and NgtscTestEnvironment; an inspected case writes a component and external template, invokes driveMain, and checks generated JavaScript.
- DevTools has direct assertions for injector path and edge construction and for V1-to-V2 settings migration; PR CI also runs DevTools unit tests, a Chrome build, and Cypress against the devserver.
- Framework test:ci excludes integration, adev, VS Code, DevTools, and SSR benchmarks; PR CI provides separate integration, adev, VS Code, and Zone.js jobs, with Zone.js invoking Jest, Vitest, Electron, and typings checks.
- createCustomElement contains a specific TODO requesting end-to-end coverage for cases where the constructor is not called and says that scenario is tested internally at Google; the internal test implementation and results were not available in this inspection.