Qualifying

Ever rising cost, and the need for a more flexible workplace (any time, any place, any device) put large demands on the IT departments of companies today. The solution lays in the Cloud: Infrastructure as a Service (IaaS) promises all the flexibility you need while at the same time lowering costs significantly.

However, moving a companies IT into the cloud is not an easy task: Many applications still have problems running in the cloud. Incompatibilities with current server operating systems, issues in multi user access scenarios and interoperability problems, make moving a companies IT into the cloud a precarious endavour.

Thus, before taking on a cloud transitioning project for a customer, it is important to not only check the customers application portfolio for performance parameters (as is typically done in cloud readiness checks), but also verify the compatibility and interoperability of each application the customer is wanting to use.

However, it is impossible to perform extensive tests with each application before even having started with a transition project. This is where our QtestBASE Qualifying module will make your life a whole lot easier!

QtestBASE provides a knowledge base capable of collecting data of large quantities of applications in multiple projects. This data comes from testing done during the application management process in other projects. The Qualifying module identifies all applications already known to the database, and provides you with detailed information on their compatibility and interoperability. This enables you an in-depth analysis of large parts of a future customers application portfolio without even having done a single test!


Customer Application Pretest (CAP)

The Customer Application Pretest approach of QtestBASE enables a new level of Application Readiness Test for the cloud. Not only will you be able to check the installability of an application in much finer detail than ever before, but also monitor an application start to make sure the application actually runs. While it is, in the rich client world, sensible to assume an application will run as expected after having performed a successful installation, this cannot be taken for granted in a multi user scenario. It is thus absolutely imperative to perform and monitor an application start and make sure the application not merely installs, but rather runs as expected.

Also keep in mind, that every company uses a large number of standard applications like Microsoft Office, Adobe Reader, Oracle Java and others (as opposed to custom applications that may be specialised on the companies market or self-developed in-house). These standard applications typically make up the largest part of a companies application portfolio. However, since they are widely used and developed by third party companies, they mostly are unproblematic in regards to platform compatibility and application interoperability. The flexible rulebased approach of QtestBASE enables you to perform the necessary analysis as fast as possible but as thorough as necessary.


Risk Analysis (RA)

The application management process typically consists of three main steps:

  1. Engineering
  2. The engineer installs and analyses the original vendor package. He then configures the application in such a way that it meets the requirements of the target environment and company guidelines. This includes for example compatibility to the rollout mechanism, correct usage of user data directories, etc.
  3. The resulting scripting instructions describe the steps necessary to have an application run correctly in the target environment.
  4. Packaging/Scripting
  5. In Packaging (aka Scripting) the instructions given by the engineer are put into installation scripts that automatically perform the steps, the engineer executed manually. Also, in Packaging the application is put into a form, that the target deployment system can use for automatic installation.
  6. Rollout
  7. The deployment package is finally rolled out to the enduser.

However, large scale rollout of a faulty deployment package can lead to interuptions in day-to-day bussines, which, in the end, may cause serious losses. It is thus most important to make sure the deployment package is actually fit for a rollout "in the wild".

With Rulebased Risk Analysis (RA) QtestBASE provides in-depth testing of a deployment package while at the same time reducing costs significantly.

In the RA process the package is deployed in a test environment. Using our world-wide unique Fingerprint technology, an Application Fingerprint is generated. This Fingerprint includes all changes the deployment package makes to the system. The aquired data is then used by our rule system to analyse the deployment package and detected installation errors, interoperability problems, styleguide violations and more. The resulting data is structured and prepared to be reviewed by a QA expert. Reporting capabilities from management overviews to customer reports to highly detailed technical spreadsheets, finalise the process.

But RA is more than just installation testing. In a large scale system management process application lifecycle management is a very important factor to stress free deployment. For this reason QtestBASE also enables uninstallation testing to make sure uninstallation and/or upgrade of an application is possible at any point in time.