We have a payment switch, so we handle many message protocols such as ISO 8583 and SOAP. Our focus isn't much on GUI testing. Mainly, we concentrate on the transactions going to the bank and back to the terminal, heavily utilizing the part of the system that requires a JBoss license.

We use Parasoft SOAtest for automotive compliance and sanity-checking scores.

We primarily use the solution for API testing for banking clients.

Our primary use case is for Driver and Firmware SQA. This is a pre-requirement for ASIL-certified SW component.

We are a large company based in India. The primary use case of this solution is for our REST architecture. Parasoft uses different languages like JSON, XML and SORBS. It's like an API testing tool and can be used for both automation and manual testing. We are customers of Parasoft and I'm a senior software engineer.

The solution is primarily used by clients for testing, such as load testing. 

We use a lot of tools from Parasoft toolset, but with SOAtest specifically, we use it for creating and running integration tests.

The primary use case for adopting Parasoft SOAtest is to test web services/middleware testing (SOAP/REST/MQ/SAP RFC/EDI/FTP). 

Inbuilt support:

• REST: WADL and JSON.
• SOAP: WSDL.
• SAP RFC
• Message queuing supported: JMS, MQ, and NET WCF.
• Protocols supported: TCP/IP, FTP, EDI, WSDL, WADL, WS-*, UDDI, RMI, EJB, webMethods, TIBCO, SMTP, and custom.
• Languages Supported: Java, JavaScript, Groovy, Jython
• Virtualization
• Third-party tool integration (plug and play)
• Stored procedure testing and DB validation
• UI recording through Selenium WebDriver.
• I've used this solution for more than 6.7 years.

Repeatable automated regression tests in a SOA architecture IT landscape, for several SOAP/REST webservices including Web Gui end-to-end testing, all scenario-based for 10+ applications. Also, scheduled for test runs at night, using Jenkins.