In my mind, a framework is a collection of functions, both applicaction-specific and generic, that makes large-scale automated testing possible.
There is no "one" framework for automated testing with QTP. Furthermore, since each AUT is unique, no single framework can be ported to another organization and be expected to work as well as it did for its creator (if at all). However, you can review the general concepts behind a framework, take what works for your AUT, and fill in the pieces by looking at other frameworks or by getting ideas from other people. That's how I cooked up mine.
There is no "one" framework for automated testing with QTP.
[/ QUOTE ]
That thought is based on old thinking.
Axe from Odin Software is one commercial solution that is a good example of a portable framework.
I am currently part of a project team working on another solution that is about to go to a customer as beta site. The solution is mature and works well. It also does away with the dependency of Excel and all its limitations.