Advanced FAQ
This topic answers some of the advanced questions that are asked frequently by users.
What if I upgrade my environment after I've installed the IDE plugin?
For some upgrades, no action is required. For others you need to re-run the installation in Change mode, as shown below:
| If I upgrade: | Change: |
|---|---|
| NUnit framework version | No change required. |
| JUnit framework version | No change required. |
| Java JDK version | No change required |
| Visual Studio version | Run OpenText Functional Testing for Developers installation in Change mode, and select the new Visual Studio version. |
| IDE version | Run OpenText Functional Testing for Developers installation in Change mode. |
For details, see Change or uninstall.
Can I run tests remotely?
Yes. You can set up your environment to run tests in a configuration where your test is located on a different computer than the AUT. For details see Run tests remotely.
Note: In addition to these instructions, before you set up remote run configurations, make sure to review your network topology and read the Security Reference section.
Can tests continue to run if the RDP connection is locked or disconnected?
Yes. You enter the user name and encrypted password credentials in the runtime engine settings on the computer where the test is running so that the test can continue to run when the connection is locked or disconnected. For details, see Customize the runtime engine settings.
Can I configure the port number?
Yes. If you have another application that listens to the same port as OpenText Functional Testing for Developers, you can configure the port number. For details, see Modify the communication port number.
How do I create a data-driven test?
Use Excel data as input and take advantage of standard looping functionality available in the NUnit or JUnit frameworks or implement on your own.
How do I identify and handle errors that occur during a run?
When an error occurs in a step that the runtime engine tries to perform on your application, it throws an exception. You can catch the exception in your code and handle it as needed.
All such errors are also included in the report.
For details, see Analyze run results.
Can I use my own testing frameworks?
Yes. The IDE plugin includes templates that are based on leading frameworks like NUnit and MSTest (Visual Studio), and TestNG and JUnit (Eclipse, Spring Tool Suite, JBoss Developer Studio, IntelliJ IDEA, and Android Studio). Using these templates helps you get started working quickly and enable you to take advantage of their built-in functionality.
You can also build on top of the provided templates or create tests from scratch with your own framework. Doing this requires some extra configuration.
For details, see Use your own frameworks.
Example: Testing with Cucumber
Can I run multiple tests in parallel on the same host?
Yes.
What can I do if an interface in the SDK doesn't have the operation I need?
- FireEvent. For Web, Java, and Windows Forms technologies, you can use a FireEvent method to perform events supported for that technology and object type.
- SendKeys. Many of the SDK technologies offer the SendKeys method for all interfaces. You can use this method to type text or activate special keyboard modifiers on an object in your application.
-
Mouse and Keyboard classes. (Windows only.) These classes provide methods that enable you to send a variety of mouse and keyboard events to your application. For example, you can use these methods to move the mouse to a particular coordinate and then perform a DoubleClick. Or you can use a normal test object method to bring a particular object into focus on your application, and then use a Keyboard.PressKey method to send the keyboard scan code for the
Enterkey.Keep in mind that unlike the FireEvent and SendKeys methods, the Mouse and Keyboard classes work at the device level and not within the context of a test object. You can use them for any technology, but they rely on coordinates relative to the screen, which can be tricky to maintain over time.
- NativeObject. You can use NativeObject to access and run the native methods and properties of the run-time object in your application. For guidelines and usage details, see Access native objects, methods, and properties.
For more information on all of these methods, see the see the .NET SDK Reference, Java SDK Reference, or JavaScript SDK Reference.
How do I create toggle button test objects in WPF?
WPF toggle buttons are a special type of Button test object.
Create a WPF Button test object, and then use the ToggleButton property (C#) or getToggleButton method (Java) to return a ToggleButton instance.
For example:
C#:
var window = Desktop.Describe<HP.LFT.SDK.WPF.IWindow>(new HP.LFT.SDK.WPF.WindowDescription { Text = "MyWindow" });
var toggle = window.Describe<HP.LFT.SDK.WPF.IButton>(new HP.LFT.SDK.WPF.ButtonDescription { ObjectName = "Button4" });
toggle.ToggleButton.Set(CheckedState.Checked);
Java:
Window appMainWindow = Desktop.describe(Window.class, new WindowDescription.Builder().objectName("MainWindow").fullType("window").windowTitleRegExp("MainWindow").build());
Button buttonWithToggleButtonSupport = appMainWindow.describe(Button.class, new ButtonDescription.Builder().text("Toggle Button").objectName("Button4").build());
ToggleButton toggleButton = buttonWithToggleButtonSupport.getToggleButton();
See also:

