Best Of
Re: SOATest Not Working Properly on Wndows 11
Support for Windows 11 was added in SOAtest 2022.1. See the release notes at https://docs.parasoft.com/display/SOA20242/SOAtest+Virtualize+and+CTP+20221
Are you able to upgrade to a newer version of SOAtest?
Re: SOATest Not Working Properly on Wndows 11
Build info: version: '2.53.1'
This is the version of the Selenium library which is quite old and obsolete. Upgrading to a current supported release of SOAtest will likely fix things for you.
Re: SOATest Not Working Properly on Wndows 11
Driver info: msedgedriver=134.0.3124.83
I also noticed MS just released Edge 135 (stable channel).
Re: Parasoft DTP fails to connect to Postgres by hem chart
In your value.yaml, instead of:
username: "psqladmin"
password: XXXXXXXXXX # User psqladmin password
Set using:
user: "psqladmin"
For password - don't use clear text string. You need to use "passwordSecret" and "passwordSecretKey".
See, reference documentations under DTP configuration https://hub.docker.com/r/parasoft/dtp-helm. This provides example of using MySQL, but for the user + password it would similar to whatever DB you used.
Vinay
Re: Rest API to Get All Message Responders in a Given Virtual Asset
Hi,
The information about responders would be in the pva file. If you looking for all responders in pva file you then this API endpoint will get that. It includes the Responder Suites and all Responders.
http://[host and port]/soavirt/api/v6/descendants/assets?id=%2FVirtualAssets%2Fecho.pva
Hope this helps!
Re: Sample Escaped HTML Body for Message Responders API Payload
Glad to hear that you were able to make it work!
Re: Sample Escaped HTML Body for Message Responders API Payload
Hi,
What I often do in these cases is to test the actions in reverse. I would create a responder with html as the response payload and then I would call the GET operation on the REST API to see what the payload looks like.
When I did that with a simple html payload this is what was in the GET response
"text": "<html>\n\t<div>\n\t\t<p>This is \"html\" for a response</p>\n\t</div>\n</html>",
Since the payload is JSON it really only is the double quotes that need to be escaped.
Hope this helps!
Re: /v6/testExecutions - Location of Test Configuration Files
Using custom test configurations in the workspace has been working for me the same way we document. It isn't obvious to me why this might not be working for you.
Re: /v6/testExecutions - Location of Test Configuration Files
I checked with a colleague and we see custom test configurations working as expected. We confirmed it doesn't matter if the test configuration is added before or after starting the server. If you continue to run into issues with custom test configurations then you can enable debug logging then check the logs for detail.
Re: /v6/testExecutions - Location of Test Configuration Files
I do want a custom config so that I can add the accessibility scans.
Are you using the new Web Accessibility Scan tool? There is nothing special to enable in the test configuration.