@elch : most likely you don't have the administrative rights to access test configurations. I suggest contacting your administrator. Once you have the right access, you should see this list of options:
It is not a "standard error" message from the tool. I guess there may be some issue in your local configuration files. Please contact our support team - short streaming session will be the most effective way to solve this problem.
Please open project properties, then Parasoft -> C/C++test -> Build Settings. In 'Compiler settings' select 'Family' drop box and change compiler to 64-bit variant (with x86_64 in name) or if 64-bit variant is used change it to 32-bit (without x86_64).
C++test sometimes incorrectly detects available compiler.
These are two different instances of Visual Studio, thus Parasoft plugin have to be installed separately for each one.
The WSDL field cannot be parameterized from data source or test suite variable. It can only be parameterized from an environment variable.
You can modify the method to accept two arguments:
def writeString(input, context)
From the 2nd parameter to the method (called "context" in my example), you can call
This will return a java.io.File object, whose path is created by resolving the path passed into getAbsolutePathFile with the path to the .tst file that the script lives inside. So if the .tst is at c:/myworkspace/myproject/mytest.tst, then the call above would return a File object for c:/myworkspace/myproject/File.txt.
You can view JavaDocs for this method by going to Help > Help Contents > Parasoft SOAtest Extensibility API and viewing the ScriptingContext interface.
Are you testing a mobile app or a desktop app? SOAtest supports web applications, and it can execute Appium scripts against a mobile app - but it does not support desktop applications. SOAtest's sweet spot is testing the APIs that all of those apps make to the backend.
Support would be the best pick.
I think we identified the issue. It most likely happend when both C/C++test and dotTEST looked for custom test configurations in the same custom folder.
In order to avoid the issue, until we have the issue resolved, please, use different custom folders for C/C++test and dotTEST test configurations.
I'm sorry, I don't know why it does not work. It should. Could you please contact our support for more detailed investigation?