Using UFT Developer for Web Apps (Visual Studio and Csharp)

UFT Developer helps you develop automated tests for a wide range of technologies, using standard IDEs with modern programming languages. UFT Developer requires familiarity with the basics of programming in the language you use to develop your tests.

This UFT Developer help center covers UFT Developer versions 15.0 through 15.0.2. Any version-specific changes are indicated where relevant.

Download the Trial for UFT Developer from resources.

An application model is comprised of a hierarchy of test objects that correspond to the structure of the actual objects in your AUT or a specific area of the AUT.

When you create a new UFT Developer application model, two files are created:

• .tsrx . An XML representation of the application model and its objects.

  This file is created when you create the application model item or project, and is updated regularly when you add test objects to your application model (using the Object Identification Center, in the Application Model editor, or directly in the file itself).

• .tsrx.cs or .java. A file containing the code for the application model class.

  Each application model is compiled into a class that can be instantiated in your test, enabling you to access the complete test object model of your application.

  This file is generated from the .tsrx file. There are several ways to generate this file, as described in Generate application model code.

Using the application model enables you to maintain your test objects in a single location for use across your entire testing suite, and helps you write your code more quickly, without the need to write manual programmatic descriptions for each object.

About the test object hierarchy in the application model

UFT Developer identifies test objects within context of their parent objects. The top-level parent represents the host application, such as a browser or window.

When creating test objects manually, you define the top-level parent object and then define the other objects as child objects.

When working with the Application Model, you can define an application model without the parent test object inside.

More specifically:

• For Web, Mobile, and SAP GUI for Windows applications, the parent object is never defined within the Application model.
  

• For other Windows-based applications, you can decide whether the parent window is defined inside the model or external to it, in your test.

When you create an instance of your application model class in a testing project, you can call it with or, for Windows-based applications, without a constructor.

• If you call it without a constructor: appmodel MyApp = new appmodel(); then the top-level parent defined in your application model is used. (Relevant only for Windows-based applications.)

• Alternatively, you can define your parent object (such as a Window, GuiSession, or Browser) within the scope of your test and then pass that parent object as the context for the application model class.

  For example:

  IBrowser MyBrowser;MyBrowser = BrowserFactory.Launch(BrowserType.Chrome);appmodel MyApp = new appmodel(MyBrowser);

Using this model, you can test objects from the same application model using different browsers or hosting applications.

If the test object methods and properties available for a particular test object do not provide the functionality you need, you can access the native methods and properties of the run-time object in your application using the relevant property/method/function for your programming language.

For example, suppose you have a Web edit test object defined in your test called searchBox. You could access the native (run-time) search box object, and then use the native isDisabled property to make sure your search box has the expected state.

When you run UFT Developer tests created from a UFT Developer project template, an HTML report is automatically generated. The report includes summary information about the run, as well as detailed information about the captured steps.