In terms of cost, what is the ratio (percentage) of testing to overall Project?
This was selected as Best Answer Absolutely agree with all the other comments here. The thing about testing is this – the ratio is determined by how much testing you need to prove to yourself, your team and your client that your application meets the client requirements. I could easily argue that oh – 30% sounds good. But that number doesn’t mean anything. You need to understand why you are testing and the complexity of the system. The development methodology used can play a big part in this as well. If you go with the “traditional” waterfall methodology, then you don’t test until components are finished – and you have to revisit and/or rewrite test cases each time changes are made to components so these are hidden costs that can blow out your schedule. If you use Test Driven Development, then you write the test cases before (not true it’s more in conjunction with) the code. And you don’t change code until you have changed (if required) the test cases too. This should lead to much fast
Related Questions
- What are the funding plans for the difference between funds raised philanthropically and the overall cost of the project?
- How much of the overall cost of my small wind project goes toward the tower and foundation?
- Is Operations and Maintenance (O&M) included in the overall development cost of a project?
