QTP Keyword View vs. Expert View
As a recent automation project I've worked on (Windows/ActiveX technology) draws to a close, we are looking at beginning another one on a Web-based application. For this app, we have some resources in NY, but much of the QA team for this product is offshore.
In terms of assigning resources, the question of how to create and manage reusable actions comes up. In the first project, we took the approach of having Excel Input sheets where the actions were defined, dedicated QTP automation people would code the actions, and the QA Staff worked solely with the Excel interface to specify test inputs and outputs, and used QTP solely to kick off the scripts. There were several pluses and minuses with this approach:
- the QA Team didn't really receive formal QTP training and feel they were intimately involved in the automation effort, nor were they getting QTP experience - a very marketable thing these days
- the scripts given to the Automation Team were incomplete in terms of environment settings, and since the Automation Team was not deeply trained in the product, much time was spent filling in missing test environment setup and data dependency information in the scripts
+ the reusable actions were quite versatile
+ much more sophisticated tests (and probably more maintainable) were possible based on the reusable actions created by the dedicated Automation group
On this new endeavor, I'm considering having more QA Team involvement with the QTP Scripting through the Keyword view - which has come a long way in terms of methodology, discipline and usability as compared with the initial record/playback script views in earlier products. The advantage in having the QA Team more versed in QTP is that the QA group will be able to more actively participate in creating reusable QTP script code, will proabably feel more part of the project and happier to be getting QTP experience, and understand the product and environment settings much better than the Automation resources (who are not versed in this product at all).
Now, finally my question - has anyone tried organizing a project where the Keyword View is the central focus of an effort, with various QA resources being trained in QTP and driving more of the effort by independently Automating their own areas and creating reusable actions - primarily through the keyword view. If so - how did this compare with the alternative approach of partitioning the effort as our orginal project, where QA group are the domain experts creating test data input sheets solely in an excel interface, and not having major interaction with QTP tool other than to run the input sheets.
By how did this compare - I mean in terms of were there issues with standards, sharing the reusable actions (e.g. was it hard to avoid duplicating effort across the same actions ?), maintenance, teamwork, etc...
Thanks in advance,
Re: QTP Keyword View vs. Expert View
yes, look into BPT from Mercury