Core answer
Start here. This is the direct spoken answer to practice first.
Overview
A good test strategy is organized by failure risk and feedback cost, not by a fixed percentage assigned to each test type.
I keep pure rules and transformations in fast unit tests, render components when template behavior matters, and use routed tests for navigation, guards, and resolver integration. End-to-end tests cover a small set of critical journeys through the real browser and deployed boundaries. The same assertion should not be repeated at every layer unless the risk justifies it.