There's someone who oversees QA - let's call him Joe. During 2 years of development we haven't had real load tests. Now release is getting close and QA is responsible for preparing and executing load tests. We (dev team) have suggested, that the load tests should be prepared and executed ASAP, before UAT starts and re-executed at least once before release.
Our proposal has been refused by Joe. The reason was that code is still changing and every code change could possibly break test scripts and require them to be updated. Joe explained that load tests should happen after code freeze, preferably after everything is already approved by the business. It was also refused by head of QA for the same reasons.
I'm not really into testing, so - is this really the way to go? Is it common practice to load test just before the release? Or are they all insane?