What we really need is a giant flow chart that factors in every single thing that should go in to the calculus of how to structure your testing. Blanket strate

What we really need is a giant flow chart that factors in every single thing that should go in to the calculus of how to structure your testing. Blanket strategies and approaches are just never going to be right for all codebases and companies. There probably are aggregate rules which kind of generalize, but I think the actual system under test and the organization it sits inside is an incredibly important consideration that needs to be taken into account. I'd love to see how everyone's different advice pans out for all possible permutations of org and codebase they could be tried against.