Skip to main content

Installation Testing

In this module, you will learn:

  • Installation/Un-Installation Testing.
  • Factors to look for in Installation Testing.
  • Types of Installation.
  • Types of Licensing.

Installation testing is any testing that takes place at a user's site with the actual hardware and software that will be part of the installed system configuration. The testing is accomplished through either actual or simulated use of the software being tested within the environment in which it is intended to function.

Installation testing is often an overlooked component of testing. This type of testing is performed to ensure that all Install features and options function properly. It is also performed to verify that all necessary components of the application are, indeed, installed.

Tests focused on ensuring the target-of-test installs as intended on different hardware or software configurations and under different conditions (such as insufficient disk space or power interrupt). This test is implemented and executed against applications and systems.

Installation testing should follow a pre-defined plan with a formal summary of testing and a record of formal acceptance. There should be retention of documented evidence of all testing procedures, test input data and test results.

There should be evidence that hardware and software are installed and configured as specified. Measures should ensure that all system components are exercised during the testing and that the versions of these components are those specified. The testing instructions should encourage use through the full range of operating conditions and should continue for a sufficient time to allow the system to encounter a wide spectrum of conditions and events in an effort to detect any latent faults, which are not apparent during more normal activities.

The objective of Installation Testing is to verify that the product installs without hanging, crashing or exhibiting other installation failures, and that there are no problems with kernel drivers, if installed.

We perform several installation tests, which include installing the application on:

  • Computers that have the minimum hard drive space required
  • Computers that have the minimum RAM required
  • Removable drives (Zip and Jazz)
  • Drives other than the default drive
  • CLEAN systems (configurations with no other software installed)
  • DIRTY systems (configurations with other programs installed, i.e. anti-virus software, office software, etc.)

We also test all of the user setup options (full, typical, and custom), navigational buttons (Next, Back, Cancel, etc.), and user input fields to ensure that they function properly and yield the expected result.

In the wider sense, installation is the very first thing the customer will do. Any faults found here will immediately give the wrong impression about the product.

TYPES OF INSTALLATION TESTING

  • Custom Install.
  • Shrink Wrap.
  • ASP Mode.
  • Custom Install: - The type of installation which can be customized according to the needs and requirements of the customer.
  • Shrink Wrap: - The type of installation which has to be installed as it is as a whole and cannot be modified.
  • Access via Internet: - Making the product available for purchase and download over the Internet, or as a packaged product.

TYPES OF LICENSING

The installation of the software requires the use of license keys. Therefore different kinds of licensing are:-

  • Node locked: - The type of license which will work for a particular node on which it is installed in a network, so it is locked for that particular node only.
  • Floating: - The license that can be used by the nodes other than the one on which it is installed over a network.
  • Named User: - The license that can be used by a particular user only.
  • Temp/evaluation Licenses: - The Evaluation license keys are the ones that are used for a limited period of time till the product is evaluated and the temp license keys are also for limited period of time but they can be used till the actual keys for the product has been received.

UN-INSTALLATION TESTING


The objective of Uninstallation Testing is to verify that uninstalling the product does no to cause chronic errors or otherwise render the Operating System useless. Uninstallation was accomplished without error. The Uninstallation of the product also needs to be tested to ensure that all data, executables, and DLL files are removed. The uninstallation of the application is tested using DOS command line, Add/Remove programs menu, and through the manual deletion of files.

Comments

Popular posts from this blog

PDF Automation in QTP

                                                                            The most challenging issue with PDFs is that it could be of any kind, not just a tabular data; it could have plain text, images or even forms to fill up. So this makes a tester’s life a bit difficult, never mind, we will definitely find an easy of do it… Although there are already some better approaches we have to deal with PDF documents but I found many of us are facing so many difficulties using this. There are lots of queries coming at QTP forums asking for an easy way of doing it with PDFs. keeping those in my mind I started c...

Convert JSON to XML using QTP/UFT/VBScript

Sample Code : Dim strPage,strJSON,objIE strPage = "C:\Jay\JLoader.html" Set objIE = CreateObject("InternetExplorer.Application") objIE.Visible = True objIE.Navigate2 strPage While objIE.Busy : Wend strJSON = "{""FirstName"":""Jay"", ""LastName"":""Krishna""}" Set objWin = objIE.document.parentWindow objWin.execScript "var jsonStr2XML = function(strJSON) { return json2xml(JSON.parse(strJSON));};" Msgbox  oWin.jsonStr2XML(strJSON) objIE.Quit In Detail: Converting The most popular data interchange format JSON(JavaScript Object Notation) to XML using QTP/UFT. Parsing JSON in UFT could be a challenge so we will use JavaScript in UFT to make it perfect. SO We need :              Java Script API  - To Convert JSON to XML                         JavaScript Files :  ...

Download Test Resource From QC Using QTP

'########################################################################### '* Function Name: QCGetResource '* Designer: Jay '* Date 09-May-2012 '* This script will Download QC Test Resource to a local dir '########################################################################### Function QCGetResource(resourceName,saveTo)     Set qcConn = QCUtil.QCConnection     Set oResource = qcConn.QCResourceFactory     Set oFilter = oResource.Filter     oFilter.Filter("RSC_FILE_NAME") = resourceName     Set oResourceList = oFilter.NewList     If oResourceList.Count = 1 Then         Set oFile = oResourceList.Item(1)         oFile.FileName = resourceName         oFile.DownloadResource saveTo, True     End If         Set qcConn = Nothing     Set oResource = Nothi...

compare Two Text files using Vb Script

Public Function CompareFiles (FilePath1, FilePath2) Dim FS, File1, File2 Set FS = CreateObject(“Scripting.FileSystemObject”) If FS.GetFile(FilePath1).Size <> FS.GetFile(FilePath2).Size Then CompareFiles = True Exit Function End If Set File1 = FS.GetFile(FilePath1).OpenAsTextStream(1, 0) Set File2 = FS.GetFile(FilePath2).OpenAsTextStream(1, 0) CompareFiles = False Do While File1.AtEndOfStream = False Str1 = File1.Read(1000) Str2 = File2.Read(1000) CompareFiles = StrComp(Str1, Str2, 0) If CompareFiles <> 0 Then CompareFiles = True Exit Do End If Loop File1.Close() File2.Close() End Function Return value: The function returns 0 or False if the two files are identical, otherwise True. Example: File1 = “C:\countries\apple1.jpg” File2 = “C:\countries\apple3.jpg” If CompareFiles(File1, File2) = False Then MsgBox “Files are identical.” Else MsgBox “Files are different.” End If    Source: Mercury Forum’s KB articles

CreateImageFromClipBoard using QTP

'-------------------------------------------------------------------------' Method : CreateImageFromClipBoard' Author : Jai Purpose : It gets the clipboard image and convert as a image file.' Parameters: FileName - String, contains the BMP file name' iIndex - Integer, contains the Worksheet index' Returns : String. The replaced file name it gives.' Caller : - Nil' Calls : - Nil' ------------------------------------------------------------------------- Sub CreateImageFromClipBoard(sFileName) Dim wshShell,ShellReturnCode, sCmdExec Set WshShell = WScript.CreateObject("WScript.Shell") sCmdExec = "D:\autostuff\i_view32.exe /silent /clippaste /convert="& sFileName ShellReturnCode = WshShell.Run(sCmdExec, 1, True) End Sub