Best Of
DTP 2025.1 Product Release Announcement
Parasoft is pleased to announce the release of DTP 2025.1. This update is available at no cost to customers on an active subscription or maintenance contract.
Enhancements:
License Server Enhancements
Support for Jtest Unit Test Bulk Creation Tiers
- Jtest Unit Test Bulk Creation Tiers license feature enables users to create unit test cases for more than one file at a time. When hosted on a License Server, this license allows centralized tracking of token availability and usage across your team.
Support for Contributing Developers Usage Data
- License Server collects statistics on analyzed files and their associated Git repositories, as reported by the C/C++test CT tool. Users can download a ZIP archive containing the full dataset or view a summarized version of the usage data directly in the UI.
Improved Widget Search when Adding New Widgets
- Users can now search for widgets by category, name, or keywords in their descriptions when adding a new widget. See Adding Widgets for more information.
External System Integration Enhancements
Integration with Azure Key Vault
- DTP can now retrieve and use its database password stored in Azure Key Vault, enabling secure and centralized credential management. See Configuring the Database Connection for more information.
Integration with DOORS Next
- Users can create a task or defect in DOORS Next from the Violations and Test Explorers. See Manually Creating Tasks or Defects in DOORS Next for more information.
Integrating with External Systems via CSV File
- You can now track requirements from nearly any external system using simple CSV files. This feature allows you to monitor traceability between Parasoft DTP tests and requirements stored in any external system not natively supported by DTP by associating projects with a CSV output from your external system that is published to an HTTP server. With it, you can track how your system's requirements are tested and view test execution statuses in DTP through DTP reports. In addition, associations can be seamlessly imported into Parasoft testing products like SOAtest and C++test. See Integrating with Other External Systems for more information.
Other Notes
- Support for PostgreSQL 17 has been added.
- Support for Windows Server 2025 has been added.
- Support for codeBeamer 2.1 has been added.
- Support for Polarion 2410 has been added.
- Polarion Requirement Traceability widget now supports filtering data by specific requirement types.
- Added REST endpoints to review and delete users in the User Administration database who were originally imported from LDAP but are no longer present in the directory.
- Improved logging of errors to provide clearer diagnostics when issues occur with OpenID Connect (OIDC) configuration.
- When creating a new Filter, the "Do not show" priority is now selected by default in the Included Priorities section of Filter Settings.
- Added instructions for deploying DTP in Kubernetes environments that enforce volume mount security policies.
- Redesigned the Deviations Report in Compliance Packs to support displaying more than 1000 deviations.
- Introduced a more flexible versioning scheme for Extension Packs, allowing older versions of Extension Packs to be compatible with newer versions of DTP.
Deprecated or No Longer Supported
- Support for Oracle 18c has ended.
- Support for MySQL 5.7 has ended.
- Support for Windows 10 has been deprecated.
- Java 11 is no longer supported for OWASP Dependency-Check Pack. Java 17 is required.
- "Do not show" priority in Violations and Test Explorers and Filter Settings will be removed in the next release.
Software Shipped with DTP
The following software is shipped with DTP 2025.1:
- Apache Tomcat 10.1.40
- Java Azul OpenJDK 17.0.14 (17.56.15)
Re: SOATest Not Working Properly on Wndows 11
Doing a lot of searching on the web, all of what I found pertains to Selenium
Yes. SOAtest happens to use Selenium WebDriver APIs. The "Response code 500" would be the HTTP error response returned by the msedgedriver. The test failure detail shows the error message as returned by Selenium's API.
These posts are talking about that either the webdriver and browser versions don't match
In your case, they do match. SOAtest gets the browser version independently, showing "Edge 135.0.3179.85". The error detail from Selenium shows "Used msedgedriver version 135.0.3179.85".
I should mention that the newer version of Selenium used by SOAtest 2024.2 will download webdrivers automatically. Unlike earlier versions of SOAtest, you no longer need to manually download and copy webdrivers into the SOAtest installation. If you already copied a "msedgedriver.exe" into the SOAtest installation then you can delete it to make Selenium download the correct one automatically. Selenium will store webdrivers in your user profile (home directory) under a ".cache/selenium" folder.
Could this be an issue of not having the authorization to run the tests?
Edge playback works without running as administrator. We have many users on Windows 11.
Any suggestions would be helpful
Since the error and behavior is not specific to SOAtest, you can often find help by searching for such errors on the web.
I found a couple things describing how different security policies can block access and what to do about that:
https://github.com/MicrosoftEdge/EdgeWebDriver/issues/109
https://learn.microsoft.com/en-us/microsoft-edge/webdriver-chromium/?tabs=c-sharp#developer-tools-availability-policy
I found a couple other suggestions recommending to first try killing any running or background instances of Edge with taskkill /f /im msedge.exe.
Re: We changed from 2021.1 to 2024.1 version of Soatest, there is a difference in compare
Please allow me to copy my explanation and response from Traffic Viewer/Diff tool issue:
You show these extra attributes:
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"
This is the typical way to say that the element represents a null pointer as opposed to an empty string, for example.
This is an intentional change made a few years ago for the SOAtest 2021.2 release.
From the SOAtest 2021.2 release notes:
SOA-8013 Database Tool Returns zero or empty string for null values
Previously, the result set XML did not distinguish whether a value was a null as opposed to empty string or zero but now it does. The Traffic Viewer's Table view will also now render null values a special way, those that have xsi:nil="true" in the XML representation.
and this can't be turned off?
No. Please update your Diff controls, for example.
Re: Soatest 2021.1 issue: SSL Error: Received fatal alert: protocol_version
TLSv1.3 was enabled in Java 8u341 in July 2022. https://www.oracle.com/java/technologies/javase/8u341-relnotes.html
I see that you have SOAtest 2021.1 which predates that.
Two possible solutions are:
1) Download the latest Java 8 (u341 or newer) and launch SOAtest with -Zjava_home C:/Program Files/Java/jdk1.8.0_341/
https://docs.parasoft.com/display/SOA20211/Configuring+Java+Runtime
2) Upgrade to SOAtest 2022.1 which includes Java 11.
https://docs.parasoft.com/display/SOA20232/SOAtest,+Virtualize,+and+CTP+2022.1