Based on the rave reviews our clients have given us, we can confirm that we have now cleared these hurdles, thanks in large part to our clients’ support. After five years of work, we have achieved a real maturity of both our tools and the associated methodology. The next step is to take advantage of the markets for this technology, which could revolutionize the world of test automation.

The key factors for the success of our proven offering are:

• Our product line’s perfect adaptation to AS/400 applications, with all their related particularities. Batch process and spool file management are just two examples of many,
• The fact that our products can be placed in the hands of users who are not IT specialists by profession. This might seem surprising, but in most cases, the scenarios are developed by the developers themselves. This is not the case with ARCAD-Qualifier,
• Flexible use. Whether our tools are used in conjunction with ARCAD-Skipper (the version manager) or as a stand-alone, they can be adapted to any type of software development organization,
• The handling of the data used for each of the scenarios. This avoids manual processing, which is both a source of error and the major cause of a decline in productivity,
• Optimization of testing processes by automatic impact measurement based on a batch of modified programs.

We will continue to pursue our research and development efforts, and we are pleased to already be able to announce the availability of coverage for your applications’ web interfaces. Our users have been waiting for this function for quite a while, but the problem was not easily solved. It was imperative to maintain our competitive advantage in terms of ease of use. Now we have found the solution. I encourage you to register for our upcoming webinars to find out more.
The other goal of this newsletter is to let you know that it is not necessary to have a large crew of testers to get the most out of this tool. A limited set of scenarios covering the most critical functions of an application, such as for example a command entry, makes it possible to have a near-immediate return on investment.
We would also like to use this newsletter to sincerely thank our client Sogecap, which contributed significantly to this latest success. You will find their testimonial on their experience at the « Success story Sogecap » link.

Yours sincerely,
Philippe MAGNE
CEO

Below you will find a functional description of our test automation suite, the key element being its easy implementation.
ARCAD-Qualifier offers absolute simplicity in a number of areas: orientation, design, functioning, etc...

Read>>

The effort needed for application testing depends on one paramount factor – the critical nature of incidents in production. The ARCAD method is to focus on these vital application functions and apply a consistent non-regression test policy to even the smallest application change.

Read>>

Neller Pty Ltd has been designing, developing and supporting human resources and payroll software solutions for organisations in Australia and New Zealand for over 33 years. Their solution, Preceda On Demand, is delivered through the on-demand platform, commonly referred to as Software as a Service (SaaS) - via the internet.  Neller has kindly offered to share with us real-world examples of their success with the new Eclipse-based version of ARCAD-Verifier.

Read>>

This topic is dedicated to the users of ARCAD products, to give you little tips and tricks to make your life easier in your daily tasks. In this issue, we tell you everything you need to know about :

Modification of the content of a script via TFROBJ
Tests of web applications often handle the management of test scripts differently than production scripts (different servers, access paths, etc.) Since ARCAD offers the possibility of managing application variables in the script, it allows users to have a single script whose content will be dynamically modified during the transfer into the test or production environment. To illustrate this concept, here is a simple, authentic example taken from a .jnlp script.