Installation Testing

•Installation testing is often the most under tested area in testing. This type of testing is performed to ensure that all Installed features and options function properly. It is also performed to verify that all necessary components of the application are, indeed, installed.

Installation testing should take care of the following points: -

1. To check if while installing product checks for the dependent software / patches say Service pack3.
2. The product should check for the version of the same product on the target machine, say the previous version should not be over installed on the newer version.
3. Installer should give a default installation path say “C:\programs\.”
4. Installer should allow user to install at location other then the default installation path.
5. Check if the product can be installed “Over the Network”
6. Installation should start automatically when the CD is inserted.
7. Installer should give the remove / Repair options.
8. When uninstalling, check that all the registry keys, files, Dll, shortcuts, active X components are removed from the system.
9. Try to install the software without administrative privileges (login as guest).
10. Try installing on different operating system.
11. Try installing on system having non-compliant configuration such as less memory / RAM / HDD.

Prasad Reddy's blog
Login or register to post comments
3229 reads

Installation testing focuses

Installation testing focuses on the way the new application or system is placed into its production environment. The installation process itself can vary from a simple startup. exe that copies all application files to their proper place to a complex set of files and an instruction manual for an experienced system installer. Regardless of the simplicity or complexity of the installation process, it needs to be tested to ensure that the recipients of the new application or system can be successful at making it ready for use. The recommended approach is to have a test environment with the hardware platform(s) and software platform set up to look exactly like the intended production environment. Then the test is to execute the installation procedure as written with the files provided to validate successful installation. During the last 10 years, installation processes were weak in helping the end-user installer determine if the installation was successful. There has been a resurgence of vendors that include installation verification aids, both manual and automatic, with the installation packages. Do not forget to test the verification aids too!

Submitted by vemaniraghuraja on April 11, 2008 - 6:20am.