Looking at it from management's perspective, if you improve their framework, it will have the following costs: 1. Cost for you to make it. 2. Cost for QA to l

Looking at it from management's perspective, if you improve their framework, it will have the following costs: 1. Cost for you to make it. 2. Cost for QA to learn it. 3. Cost to convert previous tests to new framework, if necessary . 4. Cost for delays on fixing QA's tests. 5. Cost for developers and management to receive QA's results later than expected during development/training. Essentially, the question you have to ask is this: In the process of improving this, how many tests will be delayed and by how much time? Will doing this save or expend resources over the duration of the project? If you can answer that question, and the answer is that it will save resources - do it. Break down the costs and benefits to them from a program perspective. Understand them at their level and they will likely listen to you. Keep in mind though - their goals aren't always what you think they are.