Known issues - basic
Relevant for: GUI tests and components and API testing
This topic describes general troubleshooting and limitations when working with OpenText Functional Testing.
WSE support
Microsoft no longer officially supports WSE, which OpenText Functional Testing uses to run web service testing using WSE security settings.
Windows update effects
Some Windows updates (for example from 101803 to 101903) affect the installed OpenText Functional Testing program and prevent it from working properly.
Root cause: The Windows update deletes some registry keys required by OpenText Functional Testing.
Solution: The first time you open OpenText Functional Testing after the Windows update, a registry repair program runs and fixes registry errors caused by the update.
User Account Control
You cannot use some of the OpenText Functional Testing tools when the UAC (User Account Control) option in is set to ON.
Workaround: Temporarily turn off the UAC option while using these tools, by doing the following:
To turn off the UAC option:
-
Open the registry editor. (Run a regedit command)
- Navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
- Modify the EnableLUA DWORD value and set it to 0.
-
Restart the computer for your changes to take effect.
To turn the UAC option back on:
-
Open the registry editor and set the value of the following key back to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA
- Restart the computer for your changes to take effect.
Using multiple user accounts
You can run tests from multiple instances of OpenText Functional Testing simultaneously on the same machine in different Windows sessions. When OpenText Functional Testing is launched by a different user account than the application you are testing, the following functions may behave unexpectedly:
- Recording
- Running tests
- Spy
Workaround: Launch the application through OpenText Functional Testing, for example, using the Record and Run settings.