You can also try installing from network location and remove network during installation, install with insufficient disk space, start installation multiple times on the same machine, corrupt installation and try installing from corrupted file, install on a non supported platform, non supported environment.. and many more.. some more information can be found at http://testinggeek.com/installation.asp hope it helps.
[ QUOTE ]
yes we need more information regarding this
here i'll explain how we use test the Installer
first while installing the installer creating all the folders and subfolders in required locations?
++++++<<<<<<<<<<< << this is actually not negative testing but rather the criteria one uses to determine if a successful install occurred.
is it missing out any files(ex:-exe files)?
++++++<<<<<<<<<<< << same comment as above
how much memory it has to occupy now how much memory is it is taking?
++++++<<<<<<<<<<< << I guess I've never thought of such a test case but I don't really feel it's important to monitor memory usage during installation. What you should be interested in is disk space required to install the app as well as the time to install.
1. Install on unsupported OS's. Take into account Service Packs for Win environments
2. Install on a drive that doesn't have enough disk space to install
3. Technically this is "recovery" testing but for this discussion I think it's beneficial to mention....pull the plug on the machine halfway through the install. What happens when you re-boot and attempt to install the app?
4. Corrupt data in the registry files such as install loc and then attempt to uninstall the app
5. Select a location other than the default and input an invalid drive and/or folder
6. If you have a serialized app then input an invalid validation code and see if you can install
7. If you must have certain OS privs to install your app attempt to install as a user who doesn't have those privs
8. Install into a read-only directory
9. Name a folder on your hard-drive using...oh, let's see here...how about Japanese text. Select this as the install loc and see if the installer can write to this location
10. Max out RAM so you'll start paging data and see how installer behaves
11. Change OS lang to a lang the app doesn't support....some apps will read OS lang and if isn't recognized will default to English
And now I'm going to get totally rediculous.....
Talk to R&D and understand the installation flow and in particular if there is something the installer expects in order to perform an operation. Create a batch file that deletes those files and execute it during the install process and see what happens. The installer will be expecting a particular file to be in a location yet it doesn't exist because it was deleted.
Reserve a few months every so often and preview retirement throughout your career. You won't regret that a 35 year career was reduced to 34 years to take vacations measured in months in order to remember what a stress and care-free life is all about.
Books and hard work will get you anywhere you want to go.
Seeing as this thread was brought up in another thread...and the topic was touched upon in the current issue of Better Software ("Navigating the Installation"), I will add one item mentioned in the article that wasn't mentioned above.
Uninstall the software and then try to reinstall.
Looks like thekid spelled out the majority of the other scenarios that were identified in the Better Software article.
"The single biggest problem in communication is the illusion that it has taken place."
-George Bernard Shaw, Irish playwright and Nobel Prize winner, 1856-1950