Channels ▼
RSS

Tools

The Fight Against Brittle Scripts and Software Defects


Parasoft has continued its current focus on its automated testing tool with yet another new release of Parasoft SOAtest. This latest iteration of the product is offered to programmers testing and validating complex, composite applications and aims to eliminate costs associated with testing delays, brittle scripts, and software defects.

Visual analysis features in the latest release of Parasoft SOAtest are described as suitable for pinpointing the root cause of failures within complex component-based architectures. The new Event Details capability aggregates event details from tests running in SOAtest as well as from remote systems under test. This provides access to all relevant information in a single location — with controls for zeroing in on the critical information needed to debug the behavior of a test scenario that is not producing the expected results.

Another new analysis feature allows Parasoft SOAtest to connect to a JMS or MQ broker (e.g., Progress Sonic MQ/ESB, IBM WebSphere MQ, JBoss JMS) to retrieve the list of queues provided by that broker and display the messages currently sitting on each queue. A user views queues, messages, and message contents — as well as delete messages. This visibility into (and control over) the messages present on queues is helpful when analyzing the interaction between the test scenarios and the system under test.

"SOAtest has been on the market since 2002. It has matured with the growing complexity that large enterprises face while evolving SOA or composite applications," said Wayne Ariola, VP of strategy for Parasoft. "The latest release of Parasoft SOAtest addresses the distributed nature of both applications and development teams. The ability to visualize and pinpoint failures allows for the rapid identification and remediation of software defects. In highly iterative or agile software development shops, these new capabilities will save teams a significant amount of time."


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video