Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1903 views

QTP/UFT DP best practices

Hi

Do we have a certain set of baseline documents for our junior testers as a "QTP Best Practices".? Any thing related to Descriptive Programming and use of regular expressions ?

What are you experiences using one ? We are trying to implement best practices as an effort to have everyone in sync. 

 

Thanks

Rey 

0 Likes
4 Replies
Absent Member.
Absent Member.

Hi Rey,

We don't have a single compiled document on best practices, per se.

However, you can refer your users to a number of topics in the documentation included with their UFT installation:

  1. Use the UFT IDE > Creating and Enhancing UFT Tests with Code > Programming in GUI Testing Documents in the Editor > Programmatic Descriptions
  2. Use the UFT IDE > Creating and Enhancing UFT Tests with Code > Programming in GUI Testing Documents in the Editor > Programmatic Descriptions > StaticProgrammatic Descriptions > Guidelines for Using Static Programmatic Descriptions
  3. Use the UFT IDE > GUI Test Objects, Checkpoints and Output Values > Parameterizing Object Values > Regular Expressions Overview
  4. Use the UFT IDE > GUI Test Objects, Checkpoints and Output Values > Parameterizing Object Values > Regular Expressions Overview > Regular Expression Characters and Usage Options

 

There are also a number of topics related to using programmatic login in UFT tests in this chapter: Use the UFT IDE > Creating and Enhancing UFT Tests with Code > Programming in GUI Testing Documents in the Editor.

Hope that gives you a start. If you  have suggestions on content you want to see in the documentation for scenarios such as this, we always welcome feedback!.

Thanks,
Jeremy (UFT Docs)

Commodore Commodore
Commodore

I'd recommend sticking with the Object Repository and then using DP when you absolutely need it.  The OR will give you easier and more managable access to various UFT recognition (such as RegEx for various properties) along with easier VRI configuration, if needed.  Share out your repositories to your app area (is using BPT) or to your UFT gui tests and you have everything centrally managed.

DP has it's place but it can introduce unnecessary complexities, especially for newer (junior) automation engineers. 

Absent Member.. Absent Member..
Absent Member..

I would agree with @JohnQC use Shared OR (dont use local one) as your main respository and go for DP if you for example need to loop thru a dynamic list of elements. You could still use it in combination with standard OR

Browser("orOBject").Page("orObject").WebElement("innertext:=" & someVariable).click

Using DP for your entire solution generally means maintenance will be huge and also its alot harder for collaboration

Commander
Commander

Our help center is now online! See http://uft-help.saas.hpe.com/

We'd be glad to hear any feedback at docteam@hpe.com!

Regards,

Batami

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.