Your manager sounds great. Once you're able to outline the delivery/business/product case consider getting your QA function to champion (author?) the technical

Your manager sounds great. Once you're able to outline the delivery/business/product case consider getting your QA function to champion (author?) the technical solution with you. It's good to separate the two initially (a well documented problem leads to more options than a quick fix) but at some point you'll want to engineer buy-in. What you've described will almost certainly be a pain point for testers - this makes them great advocates for change and grants QA much needed ownership. Feel free to dm me if you want to discuss this further.