https://www.softwaretestingmagazine.com/knowledge/qtp-best-practices/ Tue, 08 Oct 2013 12:52:42 +0000 hourly 1 https://www.softwaretestingmagazine.com/knowledge/qtp-best-practices/#comment-8615 Thu, 25 Apr 2013 12:35:04 +0000 http://www.softwaretestingmagazine.com/?p=2127#comment-8615 […] on a Project in Difficulties Article: Iteration Retrospective Activity: Turn the Tables Article: QTP Best Practices Article: Dot NET Assemblies and Strong Name […]

]]> https://www.softwaretestingmagazine.com/knowledge/qtp-best-practices/#comment-7257 Wed, 03 Apr 2013 18:59:57 +0000 http://www.softwaretestingmagazine.com/?p=2127#comment-7257 Additional best practice suggestion: using Function Overrides (registeruserfunc). It allows you to override the QTP functions like ‘input’, ‘select’, ‘click’ etc so you can wrap logging, sync and error handling lines of code around them. It saves you repeatedly having to write this sync, logging and error handling code everywhere else in your actions.

]]> https://www.softwaretestingmagazine.com/knowledge/qtp-best-practices/#comment-6912 Thu, 28 Mar 2013 06:41:49 +0000 http://www.softwaretestingmagazine.com/?p=2127#comment-6912 This will helps developer to indentify what to do and what don’t do in QTP. Very helpfull.

]]>