Subscribe by Email

Friday, February 10, 2012

What are installation/ uninstallation testing? What are some tips for installation testing?

Installation testing comes under the category of quality assurance aspects. It is concerned with the procedure that the user has to follow in order to install that software. Installation may be of any type like partial, full or it might be an installation of an upgrade of the software.

- Installation testing is carried out by the lead tester and configuration manager.
- Before carrying out installation testing, implementation testing is performed outside the testing environment.
- This is done to minimize the corruption of the software code.
- Usually for installing software, its package software or set up is run.
- The set up is actually a multi-configuration program.
- It plays a great role in the installation of software on a computer system.
- Every phase in the installation of software must be tested before it released to the public.
- In rare cases of distributed systems, it is some times required to change the database schemas and installation process of that particular software.
- For such situations a back up deployment plan is also prepared which can be implemented in case the release is unsuccessful.
- The deployment plan should also be tested as if it is a live plan.
- This kind of procedure for installation testing is called a “dry run”.
Installation testing and implementation testing are very closely related and in fact sometimes they are considered to be the same.
- The installation should be done as such that the installed program is able to cooperate with the other programs that are already installed on the computer system.
- If the program is installed successfully, it’s ok.
But, what if it doesn’t?
- It can cause considerable damage to the system.
- The user may need to format the whole system and reinstall everything again.
- The installation process should be tested both manually and automatically with all the possible configurations.
- Installation testing is a very time consuming process.
- Tests cases require much time to execute.

Un-installation testing also follows the same procedure.


1. List all the configurations that you want to test.

2. Format one of the drives on the system and use it as the base for your testing.

3. Every time you have to execute a configuration, you can create a ghost of the basic images that will be required. This will save your time. This is the only automation that can be done in an installation or uninstallation testing.

4. You can attempt to install software on one operating system many times. Every time you uninstall the software, you can prepare the base for installation of the next configuration.

5. Always keep the flow chart of the whole testing process handy with you. With a flow chart you can how much you have progressed in the testing.

6. If previously you have installed the compact version of the software, then for the next test case install the full version.

7. If you are going according to the flow chart for installation process, then follow the same flow chart bottom up for the un-installation testing.

8. You can even use the flow chart to design automated test cases.

9. Check the amount of space that the software requires. Make sure that only that much is utilized and not more than that or less than that.

10. Always carry out installation and un-installation testing in a distributed testing environment. This helps you in managing many test cases simultaneously. You no need to manage different systems.

11. Try crashing the installation and un-installation process in between.

No comments:

Facebook activity