I've been reading lot of eulogies on the Keyword Driven framework but my experience has been that it really sucks. The project I am working on had a KWD framework that were created by some consultants and handed over to the client. With no expertise on-site and the scripts falling apart, I have been hired to see what I can do with the existing scripts.
All the coding is done outside QTP in functions. And this one .vbs file has several hundred functions for each functionality in the Application. The Driver script has to make a call to this external vbs file to execute any small functionality. So the performance is pathetically slow.
And also, functions have been written even for a CLICK and EXIST while these are provided within QTP itself. The DataSheet is over a thousand lines long and gong through it gives me a headache.
So for those with good experience with KWD framework, can you please let me know if this just a single case of a bad design of a good framework or this is how it works?
I have now split all the functions into smaller QTP scripts and running them in batch mode from QC. Makes the job so much easier!!
All the coding is done outside QTP in functions. And this one .vbs file has several hundred functions for each functionality in the Application. The Driver script has to make a call to this external vbs file to execute any small functionality. So the performance is pathetically slow.
And also, functions have been written even for a CLICK and EXIST while these are provided within QTP itself. The DataSheet is over a thousand lines long and gong through it gives me a headache.
So for those with good experience with KWD framework, can you please let me know if this just a single case of a bad design of a good framework or this is how it works?
I have now split all the functions into smaller QTP scripts and running them in batch mode from QC. Makes the job so much easier!!