I’d agree and say that your context and how your organisation / team works should shape how you test. It’s important that we as testers know WHAT IS POSSIBLE and why we’d use certain techniques in order to select the best approach for the context we’re in.
When’s it the best time to get involved early?
- When there’s team buy in for finding risks early
- When the team will change user stories and ACs based on feedback
- When it’s about quality (not testing)
- When there’s the psychological safety to have conversations out in the open
- When the team’s defined quality (how good what they’re working on needs to be)
- When you feel you have the skills to be involved in that way!
It’s worth noting that shifting left is a technique to provide clarity of what to build and shake out potential assumptions / risks early. We’re not looking to necessarily just do the testing we’d do but earlier… it’s a different thing with different outcomes 