Product Documentation
Abstract
This document contains a complete listing of releases, refreshes, fix packs and interim fixes sorted by version for IBM DevOps Test UI.
Content
Table of Contents:
List of fixes
ID | APAR | Description |
TP-95224 | PH63559 | Previously, when you imported a functional test from a shared folder and ran the test in IBM Engineering Test Management, and if the test had an image verification point, then any updates to the verification point were not reflected and the test failed. This problem is fixed. |
TP-95162 | Previously, when you ran a runner file to play back a functional test with Cucumber integration, the Cucumber HTML log was overwritten even if you specified a different name for the log. This problem is fixed. | |
TP-95535 | Previously, when you ran a Web UI test on the computer whose hostname contained an underscore, and if the test also had a dataset associated, then the test run failed. This problem is fixed. |
List of fixes
ID | APAR | Description |
TP-93047 | Previously, when you ran a runner file to play back the functional test with Cucumber integration, the test failed with the java.lang.ExceptionInInitializerError error. This is problem is fixed. | |
TP-93891 | Previously, if the Chrome or Edge browser version did not match the driver version, the correct driver was not downloaded even after selecting the Click here to download the compatible driver option in the recording or play back dialog. This problem is fixed. | |
TP-94000 | PH62760 | Previously, when you ran a test for a Java application, the actions on UI controls were not completed, but the unified report did not show any failures for the test steps. This problem is fixed. |
TP-94001 | PH62762 | Previously, when you recorded tests for a Java application, the dropdown list was captured as frame().click(atPoint()) instead of jComboBox().click. This problem is fixed. |
TP-94248 | PH62763 | Previously, when you installed DevOps Test UI 11.0.2 after uninstalling 11.0.1, and then if you enabled the environment by using the Configure > Enable Environments > Java Environments option to select the default JDK, an error message was displayed after you clicked the Test button or restarted DevOps Test UI. This problem is fixed. |
TP-94564 | Previously, when you ran a mobile test on BitBar Cloud, the test failed to run on the selected device even though the device was listed in Test UI. This problem is fixed. |
List of fixes
ID | APAR | Description |
TP-91484 | Previously, when you selected the Load option from My Repository workspace for a component to load all the test assets available in the stream to be pushed to IBM Engineering Workflow Management, the assets created by the other users failed to load and displayed an error message. This problem is fixed. |
|
TP-92011 | PH59989 | Previously, when you ran a functional test from IBM Engineering Test Management, and if the test run could not be completed because of any errors, the execution status stopped and remained at 70%. This problem is fixed. Now, even in the event of errors, the test runs till it is 100% complete and the log file updates correctly. |
TP-92285 | Previously, when you ran a Web UI test that had user actions on multiple windows, the switchover to the parent window, after closure of the child window, for the user action did not work correctly and the test run failed with the NoSuchWindow exception. This problem is fixed. |
List of fixes
ID | APAR | Description |
TP-85450 | PH50908 | Previously, when you recorded tests for an HTML application, the recording window of the functional test script either did not capture test steps or slowed down if you selected Enable Simplified Scripting in the Preferences window for functional testing. To fix this problem, you can clear the Enable Simplified Scripting option in the Preferences window, and then select the Simplified Scripting option from the Select Mode list in the Record a DevOps Test UI window. |
TP-87273 | PH54177 | Previously, when you ran a functional test by using the Web UI engine and if a test step had an image verification point on a div control in the second window of the application, then the verification point failed. This problem is fixed. |
TP-87880 | PH54475 | Previously, when you recorded additional steps by using the Insert Recording into Active Functional Test Script option in the running browser instance for a functional HTML test, the recording failed with an error. This problem is fixed. |
TP-89305 | Previously, when you ran a test for Windows 64-bit applications with the tree-view control, the playback failed with SubitemNotFoundException. This problem is fixed. | |
TP-91129 | Previously, when you recorded tests for a Windows application, after the log-on action, the login window closed and with that the test recording stopped abruptly. As a result, the recording could not continue on the new window that appeared. This problem is fixed. | |
TP-91202 | PH59019 | Previously, when you configured the RQM adapter of Test UI to enable logging by using the configureadapter.bat file, the adapter failed to generate debug traces. To fix this problem, you must perform the following steps:
|
TP-91238 | When you record or play back functional tests for Java applications that use Java 9 or later on Linux, the UI controls might not be recognized correctly. To work around this problem, you must perform the following steps:
|
|
TP-91569 | PH57165 | Previously, when you ran a functional test that had steps associated with a logger and feign client dataset APIs, Test UI displayed java.lang.UnsupportedClassVersionError. This problem is fixed. |
TP-91596 | Previously, when you ran a Web UI test with a custom code to use JDBC libraries, Test UI displayed java.lang.UnsupportedClassVersionError. This problem is fixed. | |
TP-91735 | Previously, when you ran a Web UI test that had a verification point to verify the tagName property, the test step failed. This problem is fixed. |
List of fixes
ID | APAR | Description |
TP-88262 | Previously, when you ran Web UI tests that had a large number of test steps, the unified report failed to be exported as a PDF. This problem is fixed. | |
TP-89286 | Previously, when you ran a schedule that had a UI test, and if the RTW_WebUI_Browser_Selection variable was not defined for the test, the test failed without an indicative message for the failure. This problem is fixed. | |
TP-89319 | PH56255 | Previously, when you ran a Web UI test from a schedule, and if the test had Verification Points (VPs) with the Retry verification point until attribute is verified or time out expires option selected, the test failed randomly. This problem is fixed. |
TP-89519 | Previously, when you ran a security scan before installing DevOps Test UI as part of DevOps Test Workbench, the scan reported certain common security vulnerabilities (CVEs). These known vulnerabilities are fixed. | |
TP-89803 | PH56973 | Previously, when you ran a functional test by using the Web UI engine and if the test contained an ITestDataTable API, then the test either failed to retrieve the row count in the table or the playback slowed down. This problem is fixed. |
TP-89916 | PH57165 | Previously, when you recorded a Web UI test that had a test step to select an option from a list box, the test step was not captured. This problem is fixed. |
TP-90253 | Previously, when you ran a Web UI test that had an alphanumeric value with 8 characters for a UI control, the test failed. This problem is fixed. |
Original Publication Date
12 December 2024
Related Information
Was this topic helpful?
Document Information
More support for:
IBM DevOps Test UI
Component:
Documentation, Documentation->Functional Tester
Software version:
All Versions
Document number:
713025
Modified date:
12 December 2024
UID
swg27036170