Lars Nielsen has published another entry in his ongoing testing series, this time focusing on the RouterTestingHarness. Meanwhile, Signal Inputs are drawing closer, and Jecelyn Yeen has walked through what's new in Chrome DevTools 119 and 120.
Testing Routed Components with the Harness
When a component depends on the active route, writing tests for it can get fiddly. The available documentation for RouterTestingModule or provideLocationMocks often leaves out important details.
Fortunately, Angular 15.2 introduced a much more developer-friendly approach: the RouterTestingHarness. In the latest post from his Routing Testing Series, Lars Nielsen demonstrates how this harness works and why it simplifies the testing experience.
A First Look at Signal Inputs
Angular's next major shift is the introduction of Signal-based component inputs, where input() will return a Signal. It seems very likely that this feature ships as part of a minor Angular 17 update.
Matthieu Riegler already offered a glimpse of the proposed syntax on X last week.
At the time of this recording, the first pull request for the feature had already been opened. Expect more coverage in the upcoming episode.
What's New in Chrome DevTools 119 & 120
Jecelyn Yeen has provided an overview of the latest updates across Chrome DevTools 119 and 120. It's worth watching in case there's a feature you've been waiting for.
A significant topic is the gradual deprecation of Third-Party Cookies in Chrome, which gets underway next month. New DevTools capabilities have been added to assist developers with that transition.
https://www.youtube.com/watch?v=SpQ_7yZLaIc
Minor Version Updates
PrimeNG, one of the most widely used UI component libraries, has rolled out version 17 with full support for Angular 17.
https://github.com/primefaces/primeng/releases
Ionic, the cross-platform framework, has likewise moved forward with a release of version 7.6.