As most folks, I've picked up a bunch of intuitions and best practices on testing over the years, but I didn't have deeply structured thoughts on where the advice and intuitions came from.
Two things that nailed this for me:
1) @GeePawHill 's content on leading technical change (I just attended his live course, highly recommend!)
2) Re reading the testing chapters from the book "Software Engineering at Google". Content available for free at: https://abseil.io/resources/swe-book