Best Of

The leading dot is valid, and I doubt it is something that will change.

Earlier you stated "The cookie, technically, is not being set incorrectly."
I also referenced the RFC which confirms it is "not permitted".
So, it looks like a genuine defect in the application-under-test.

Even though the RFC states this is "not permitted" it also says in the same sentence that the client should ignore the dot if the application were to do such a thing. SOAtest could be enhanced to ignore the leading dot.

any chance this has been addressed in any patches?

There is indeed a request being tracked for this but if there are questions then you'll need raise them with your Parasoft account representative. I can't answer such things on the forum.

Or is there a way I can specify HTTP Client 5.x.x, which appears to be in the patched 2024 distribution?

The REST Client uses its own HTTP client implementation and not this library.

I'm not aware of any workaround other than what I suggested earlier, where you could use a reverse proxy server to re-write the Domain attribute in any Set-Cookie headers.

For reference, they are listed here:
Additional Options for SOAtest and Virtualize

I should also mention that you typically do not need to set the location explicitly. By default, SOAtest will look for browsers in common locations. On Linux, it will check the PATH using "which" command. On macOS, SOAtest will check under /Applications. On Windows, SOAtest will query registry keys to locate the browser.

What type of content are you diffing? Is it XML or JSON? For most cases, I do not recommend using Suppress Task... for violations from the Diff tool. Instead, you should use the Ignore Difference (JSON) or Ignore XPath (XML) option. This will automatically update the Diff tool's Ignored Differences tab with the ignored item.

The 2025.2 release of Parasoft SOAtest, Virtualize, and CTP introduces powerful new AI capabilities to make service virtualization and advanced test creation faster and more approachable for QA teams. Whether you’re testing traditional systems or the next generation of AI-driven applications, this release helps you reduce manual effort, accelerate test creation, and validate complex, non-deterministic behavior with confidence.

Here’s what’s new:

First-to-Market Agentic AI for Virtual Service Generation

The AI Assistant in Parasoft Virtualize is the first of its kind to offer agentic AI to generate virtual services from natural language instructions. Just describe the behavior you need, and the assistant handles the rest: from parsing service definitions or sample requests to parameterizing responses.

Now anyone on your team, not just domain experts, can create rich, reusable virtual services in minutes. It’s service virtualization, reimagined for speed, accessibility, and modern API-first workflows.

See Creating Virtual Assets with the AI Assistant for more information.

Natural Language Assertions & Data Extraction With Generative AI Tools

Testing AI-driven systems requires flexibility to test systems that return variable or non-deterministic outputs. The new AI Assertor in SOAtest and AI Data Bank tool in SOAtest and Virtualize makes this easier than ever.
These tools let you use natural language to define rich validation logic and data extraction—no XPath, scripting, or hardcoding needed. They’re ideal for:

• Handling non-deterministic outputs common in generative AI systems
• Describing expected behaviors in natural language, making it easier and faster to validate complex business logic in both traditional and AI-enhanced systems
• Accelerating test authoring and reducing errors in assertions

Validate smarter, not harder—with AI tools built for dynamic systems.

For more details, see AI Assertor and AI Data Bank.

Codeless Testing and Simulation of MCP-Based Applications

Parasoft now supports testing and simulation of Model Context Protocol (MCP) servers, a key framework for generative AI agents.

Using the intuitive SOAtest and Virtualize UI, teams can now:

• Test MCP Servers and the behavior of MCP tools that AI agents rely on
• Simulate unavailable MCP tools for stable, uninterrupted test automation
• Build test environments that control and observe AI interactions through MCP interfaces—without writing code

This gives teams a huge advantage in testing AI-infused applications, especially as MCP adoption grows.

Learn more in MCP Extensions.

Additional Updates in 2025.2

In addition to our new AI innovations, this release includes valuable updates across the platform:

• Virtualize adds support for GraphQL selection sets, improving GraphQL responder flexibility.
• Provisioning Assets project is now exposed in the Virtualize Server view for easier access and management.
• CTP now supports PostgreSQL, expanding database compatibility.

Review our release notes to learn more about the 2025.2 release of SOAtest, Virtualize, and CTP.

I updated to 2024.2.2 and it worked
Here is the connection string without anything in the user and password fields for DB Tool.

JDBC connection string
jdbc:sqlserver://.database.windows.net:;database=;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;Authentication=ActiveDirectoryIntegrated

A change template defines mappings that control how to update existing tests. A change template can highlight new operations for you but does not suggest how they should be placed within any of your existing scenarios or whether that even makes any sense. In many cases, new operations may not fit into any of your existing scenarios and you may need to create new scenarios to test them. You would need to define and create the new test scenarios for yourself. However, there is a very powerful new feature that can assist you in doing this. See Creating Tests with the AI Assistant