This topic explains several ways to contact technical support, as well as how to prepare and send "support archives" that help the technical support team diagnose any problems you are experiencing.
In this section:
| Table of Contents | ||
|---|---|---|
|
Obtaining Live Online Support (Windows only)
The Parasoft support team is available online to answer your questions. This live support allows you to chat in real-time with the support team and perform desktop sharing if needed. To receive live online support, go to https://www.parasoft.com/support/. This live tech support feature currently supports only the Microsoft Windows operating system.
Creating a Support Case
You can file a support case directly at http://www.parasoft.com/ticket.
Contacting us via Phone or E-mail
USA Headquarters
Tel: (888) 305-0041 or (626) 256-3680
Email: [email protected]
Other Locations
See http://www.parasoft.com/contacts.
Preventing SOAtest from Running Out of Memory
To prevent SOAtest from running out of memory, add memory parameters to the script or shortcut being used to start SOAtest. The two parameters are the initial size of the JVM (Xms) and the maximum size of the JVM (Xmx). Typically, both are set to the same size (for instance, 256MB). However, if you have occasional problems but don't want to always allocate a large amount of memory, you can set the parameters to different sizes (for example, 256MB as the initial size and 512MB for the maximum size).
...
Note that the maximum size you can set depends on your OS and JVM.
Increasing Memory for Report Generation
SOAtest uses a separate JVM to generate reports after code is tested. You can increase the amount of memory allocated for generating SOAtest reports by configuring the parasoft.report.separate_vm.xmx system property. Additionally, you can configure the JVM that generates reports to use Java with a larger maximum memory size by setting the parasoft.report.separate_vm.java_home system property.
...
parasoft.report.separate_vm.xmx=1280mparasoft.report.separate_vm.java_home=C:/Program Files/Java/jdk-12.0.1
| Anchor | ||||
|---|---|---|---|---|
|
If you are experiencing testing problems such as build failures, the best way to remedy the problem is to create a zip archive containing the source file(s) that caused that failure (if applicable), as well as related test information, then send that zip file to Parasoft's support team.
...