Basic FAQ

This topic answers some basic questions that are asked frequently by users.

How do I include snapshots in the report?

By default, snapshot images are not added to the HTML run results report, but you can modify the settings for your test so that it captures snapshots on errors or even for every step. You can also change this setting programmatically at any point in your test.

Additionally, you can use the TestObject.GetSnapshot method to capture an image of a test object at any point in your test and then pass the captured image to a Reporter.ReportEvent step to include it in the report.

For details, see Analyze run results and the .NET SDK Reference, Java SDK Reference, or JavaScript SDK Reference.

Note: In many cases, the generated HTML file is a standalone file.

If you selected to capture snapshots of all or failed steps, or your test includes steps that return images or other files, you may want to move the report to another location or share the report with others. In this case, make sure to keep the generated Resources folder together with the HTML file.

Can I use the same application model for different testing projects and technologies?

Yes. You can create a central application model and reference it from all relevant testing projects.

When you create an instance of your application model class, you can pass any defined Browser, Device, or GuiSession test object as the constructor.

For details, see Application models and Test-object hierarchy in the object application model.

How do I specify which technology support (add-ins) to load?

Support for testing standard windows applications is always loaded.

For all other technologies, you can modify which add-ins (technology support) to load on the computer where the runtime engine is installed.

You should load only the add-in technologies you need.

The changes you make affect the technologies supported in the Object Identification Center (OIC) as well as for tests that you run on that computer.

For more details on modifying runtime settings, see: Customize the runtime engine settings.

Can I create a test on one browser and run it on another browser or version?

Yes. You can run your Web tests on any supported browser or version.

For details on supported versions, see the Support Matrix.

As long as your application behaves the same in different browsers, you can run the test in different browsers.

To do this, use the BrowserFactory.Attach method to run on a browser that is already open, or change the browser type specified in a BrowserFactory.Launch step to specify the browser type you want for your run. All other test objects in your test, whether created using programmatic descriptions or using the application model, are independent of the browser type.

For more details, see the .NET SDK Reference, Java SDK Reference, or JavaScript SDK Reference.
See also: Test-object hierarchy in the object application model

Where are product files stored when installing from OpenText Functional Testing?

Throughout this Help Center, many instructions tell you to open files from the <Installdir> folder. For example, many important files are found in <Installdir>\bin or <Installdir>\Tools.

When you install OpenText Functional Testing for Developers on its own, you can specify the folder where you want to it. By default, C:\Program Files (x86)\OpenText\Functional Testing for Developers.

When you install OpenText Functional Testing for Developers as part of the OpenText Functional Testing setup program, the folder you choose for installing OpenText Functional Testing is also used for OpenText Functional Testing for Developers files. Therefore, the OpenText Functional Testing for Developers files mentioned above are located in <OpenText Functional Testing_installdir>\bin or <OpenText Functional Testing_installdir>\Tools.