- 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