Exploration - Dynamic Application Discovery

Problem:

With today's complicated and complex service applications it has become difficult (and somewhat impractical) to exercise an entire application. As a result there are often sacrifices made to the amount of time and resources that are applied to the application testing process. Due to these limitations, it is common that only a small portion of the predictable go right call paths are tested.

  • Only 25% of the average call flow is tested after a code freeze.
  • Less than 10% of the error paths are tested.
  • Bugs found in production are typically not on the common paths.

Solution:

Voiyager makes it easy to fully explore your entire application; every call path, every state, every time.

Additional Value:

No other solution available comes close! Although, if Voiyager did nothing other than exercise your application, quality would be improved immensely by providing more information than was previously possible.

Issues

Problem:

Finding issues, even when you are able to exercise an application, can be difficult. Developers often have to pour through logs to find the problem and recreate it.

The effort required to find and fix a problem grows as an application matures. Developers are often guided to focus on new tasks.

Solution:

Voiyager presents you with errors and suspicious behavior. Through a process of user-defined training, Voiyager learns which behaviors are valid and which are not.

Voiyager provides the full set of events required to recreate a problem.

Additional Value:

By running Voiyager early in your development lifecycle, and often, problems can be found quickly and cheaply fixed.

Issues - Problem Recreation

Problem:

Communication issues between quality and assurance testers and developers often involve an iterative process of problem recreation and data gathering. A simple problem can consume hours of discussion that is often plagued with miscommunication which cause delays.

When issues are found, developers still need to recreate the problem to find the source and to insure that their fix worked.

Solution:

Voiyager gives you the ability to export a problem and attach it to an email or an Issue Management system. This removes the "back in forth" interaction of the system tester who attempts to explain what they did and how the system responded.

Additionally, the developer can rapidly rerun the problem as often as needed to isolate and verify the fix.

Browser Phone / Bookmarks

Problem:

Developers spend hours every day calling and testing their solutions, often needing to manually drill down through a call flow tree to reach the specific issue they are investigating or working.

Solution:

Using a Voiyager bookmark a user can rapidly rerun any saved call to accelerate the call testing process.

Additional Value:

You can easily save 45 minutes a day, every day. The ease of testing will encourage developers to perform deeper, more regular, and thorough testing.

Interactive Callflow (multi-page display)

Problem:

With an adequate QA team and enough time, most "fall over and die" failures (like missing grammars and VoiceXML documents) can be found. However, it is difficult to insure all the business rules have been properly implemented. There is just not enough time to run all the possible test account variations. Worse, often the quality assurance and\or user acceptance testers are just using the same requirements documentation for validations that the developers used to write the software.

Solution:

Voiyager, from the multi-page display, you can explore all of the calls placed during a dynamic application discovery. For example, you can drill down into an Account Balance dialog and see the output for each test case provided. An analyst that understands how the application should respond should be able to validate the output of over a 100 test accounts in less than an hour.

Additional Value:

Incorrect business logic is the most common post production problem. This costs can be even more expensive than an outage as it causes users to mistrust the automated portions of the system.

Other items:

This portion of the interface is used as a launch pad to gain various types of insight regarding your application. From simple tasks, like renaming states to match your documentation, to higher value tasks like selecting a state and getting the browser phone to place a call that gets the user to the state.

Application Comparison

Problem:

Solution changes are time consuming and risky. Solutions are rarely given a full regression test prior to being put into production. Solutions are often built using common logical components. A change intended for one portion of an application may affect other portions of an application.

Solution:

Voiyager will fully test your application to insure there are no errors in your application. But, more importantly, Voiyager will rerun all the calls performed during the discovery and generate an issue list of all changes.

Additional Value:

Whether a developer accidentally changes a sound clip that happens to be used in two portions of the call flow or alters common business logic, Voiyager will expose the same changes your callers are currently finding.

Back to the top