Micro Focus QTP (UFT) Forums
Why scripting instead of using inbuilt features of QTP - Printable Version

+- Micro Focus QTP (UFT) Forums (https://www.learnqtp.com/forums)
+-- Forum: Micro Focus UFT (earlier known as QTP) (https://www.learnqtp.com/forums/Forum-Micro-Focus-UFT-earlier-known-as-QTP)
+--- Forum: UFT / QTP Beginners (https://www.learnqtp.com/forums/Forum-UFT-QTP-Beginners)
+--- Thread: Why scripting instead of using inbuilt features of QTP (/Thread-Why-scripting-instead-of-using-inbuilt-features-of-QTP)



Why scripting instead of using inbuilt features of QTP - azar80 - 01-09-2010

Hi Saket\Ankur\or any senior resource --No one can answer my doubt except experienced resources like you.

"instead of touching the nose directly with finger, why do lot of resources like to take the hand around the head and try to touch the nose"

Basically - instead of using the features provided within QTP or any tool, why do lots and lots of resources try to write more than 2 lines of code. This is just one instance, i see a lot of wastage like this or other.

As a resource who has to justify Return On Investment, how can I or anyone justify even wasting of 2 minutes in a hour writing code instead of using inbuilt features. Companies buy tools for their inbuilt features. If the resource\s dont want to use the inbuilt features of tools and want to write code to test then its better to use opensource tools which are free instead of investing in a tool especially expensive tool like QTP.

Sorry if it hurts anyone's feeling but I truly cannot justify ROI on it. Any reason why the resources do that?


RE: Why scripting instead of using inbuilt features of QTP - Saket - 01-11-2010

Thats definitely a good idea to look into such kind of cases (if it happens). I completely agree with you that we should first try to use the inbuilt features only whenever applicable. But at the same time it may depend on your requirement, objective, AUT etc.

as you said "wasting of 2 minutes in a hour writing code instead of using inbuilt features", would you like to elaborate the query specifying any particual instance when this happened at your side?