...
| Scroll Ignore | ||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This release includes the following enhancements.
Release date: October 714, 2025 Adding MIME Attachments to Outgoing MessagesThe new Attachments tool allows you to add MIME attachments to an outgoing message before it is sent. This tool is primarily used to add binary attachments to a SOAP message according to the "SOAP with Attachments" (SwA) specification. This replaces the SwA functionality that was removed in the 2024.1 release. See Attachments Tool for more information. GraphQL Query Validator ToolThe new GraphQL Query Validator tool validates GraphQL queries against a schema defined using Schema Definition Language (SDL). The typical use case for this tool is to connect it to a tool that sends or receives messages in GraphQL format to verify that the queries are valid, but it can be used as a standalone tool to manually validate GraphQL queries as well. See GraphQL Query Validator for more inforamationAutomatic Identification of Manual Tests Impacted by Application ChangesYou can now identify an optimized subset of manual tests that need to be run to sufficiently test recent application changes or perform manual regression testing for release. This allows your team to focus testing on only a specific set of tests while still having the confidence that sufficient testing was done. You can see a real-time view of the execution status of each manual test for a given application in a given environment - passed, failed, incomplete, impacted (needs retesting), or not executed. This view automatically updates as you execute tests or whenever the application changes. If the underlying code that is associated with a previously executed manual test changes, the view will automatically update the test status to show that it is impacted and needs retesting. With this summary, you can focus your efforts on manual tests that are impacted or haven't been run yet. If a test is shown as passing and is not impacted - you know that you don't need to run the test again, even if the build has been updated since you ran the test. Additional updates:
Easier Generation of Dynamic Lists in Response PayloadsNew JSON and XML list generators processors in Virtualize allow you to select items from a request payload request payload to be processed individually, enabling you to build a dynamic list for use in a response. They can be used by chaining it to another tool (for example, a message responder or REST client) or as a stand-alone tooltools. By iterating over each selected item in the a request payload, the tool enables the aggregation of dynamic, item-specific data, such as data source lookups or calculations, within a single operation, eliminating the need for multiple separate requests. Manual Testing in CTPYou can now determine which tests have been impacted by code changes and need to be retested in CTP. The process for collecting code coverage from a manual test session has been streamlined. Manual Testing in CTP now requires a separate license. AI Tools Updates
you can dynamically build a list of items for a response payload using data from the items in the request payload. Each selected item can be processed individually, allowing you to perform data source lookups or other processing steps to generate item-specific response content. The tools aggregate each response item into a list that can be inserted into a response payload.These tools replace the Multiple Response Generator, which is now deprecated, and adds support for JSON (whereas the Multiple Responses Generator only supported XML) while removing the need for multiple virtual assets "front-end asset" and "back-end asset" to be deployed to support the use case. Viewing Asset Utilization by Team or ProjectThe Asset Utilization Report in CTP supports multiple new features to make it easier for organizations to understand their usage of Parasoft Virtualize. Data can now be reported by team or by project when you organize assets on Virtualize servers using folders in the VirtualAssets project. The report now groups data by folders by default, so that it is easy to see usage broken down by folder when first viewing the report. When folders are used to separate assets by team or by project, you can gain insight into asset usage per team or per project. The report also supports new metrics: Peak Hits per Second and Average Hits per Second. This data allows you to get a better understanding of which teams and/or assets have the highest usage spikes. Data in the report can now be exported to a CSV file, easily enabling the data to be consumed and processed by external tools. AI Assistant and AI Tool EnhancementsTest scenarios created from the AI Assistant now contain assertions if the user includes instructions to perform validation of specific requirements. Assertions are created by adding LLM-enabled AI Assertor tools to appropriate REST Clients within the scenarios. See See Creating Tests with the AI Assistant for more information. The AI Assistant now supports creation of test scenarios that span multiple microservices by allowing you to specify multiple service definition files. You can now chain theThe AI Assertor and AI Data Bank tools can now be applied to web browser test scenarios by chaining them to the Browser Contents output of Brower Playback Tools. MCPTool UpdatesClient and Listener Enhancements
Utilization Report UpdatesThe Utilization Report in CTP can now be focused on folders in the VirtualAssets project in Virtualize and can now be exported to a CSV file. This is now the default focus for the Utilization Report.
Notification When Virtual GraphQL Services Need to be UpdatedYou can now identify incoming GraphQL queries to the Virtualize server that no longer adhere to an updated schema for a GraphQL service, so that callers know they need to update their GraphQL queries and their GraphQL responders to match the updated schema. This is done through the new GraphQL Query Validator tool, which validates GraphQL queries against a schema defined using Schema Definition Language (SDL). The new tool can be attached to any tool that sends or receives messages in GraphQL format to verify that the queries are valid. See GraphQL Query Validator for more information. Adding MIME Attachments to Outgoing MessagesThe new Attachments tool allows you to add MIME attachments to an outgoing message before it is sent. This tool is primarily used to add binary attachments to a SOAP message according to the "SOAP with Attachments" (SwA) specification. This replaces the SwA functionality that was removed in the 2024.1 release. See Attachments Tool for more informationThe Utilization Report can now also report new metrics: Peak Hits per Second and Average Hits per Second. When viewed alongside current metrics like asset count, proxy count, hit count, and response time, you can get a better understanding of which assets are demanding the most performance. Additional Updates
Resolved PRs and FRs
|
...