hi simple question......after our package is ready how we test it. we will test on clean VM right? and do we check that if the package is installing and uninstalling properly? and check the shortcuts and in add/remove programms right? amii going in right directions?
hi simple question......after our package is ready how we test it. we will test on clean VM right? and do we check that if the package is installing and uninstalling properly? and check the shortcuts and in add/remove programms right? amii going in right directions?
Answers (7)
You are in right direction, but it is not just this. By ready to test, I hope you have validated the MSI for ICE errors.
You also need to test it in the production VM with basic application installed like Office, Adobe. Basically the VM of a production build. This will test the compatibility of the application with already installed applications.
You can also do Conflict management against standard SOE and added applications which will tell you if there is a conflict between your application and any other application.
Comments:
-
so after i ready the application for sccm i have to check in registries for validation? - shilesh1982 11 years ago
-
That's right. I think most of the companies would provide you the VM's with all the basic software installed. Which is basically a clean install. - Sidhugadu 11 years ago
another important point to make is all tests should be done with a regular user, not an admin user.
Comments:
-
so we should not do like when we open a command line "run as administrator"? - shilesh1982 11 years ago
Apart from the above mentioned , u can also check for clean uninstallation & functionality of core apps when ur app is installed & uninstalled. Another impt check is for the files & registries match.
Comments:
-
thanks for replying..how we can do check for files and registries match? - shilesh1982 11 years ago
All of the above are what we use for testing an application. We also test for:
Event log for install clean, and re-install over existing.
Deploy to physical lab machines.
Software Requester lab testing for product functions prior to approval.
thanks all. one more question. why we create install logs and uninstall logs? and how we can create it?
Comments:
-
Logs are created to check if there is any error while installation/uninstallation of the application. You can create logs by /l*v <logfile.log> switch - piyushnasa 11 years ago
-
So should it be like that Msiexec.exe /i "<msi path\.msi>" \l*v"<path of log file>/qb-? and how we can decide that it should be qb- or q or other parameter? - shilesh1982 11 years ago
-
it should be /l*v
depends on what level of progress message you require, you can give the /q, /qb, /qb- - piyushnasa 11 years ago
what is physical machine ? difference bet physical machine and virtual machine?
Comments:
-
Physical machine is OS on your Physical hardware like Desktop or Laptop.
Virtual Machine is an image residing on your Machine like in C or D drive and you using it with VMWare Virtual desktop or Oracle VMBox. - piyushnasa 11 years ago
This is what we perform before submitting the app to SME (person that knows how the app is used, because we don't know how to use all 2k apps:).
We test on VMs that are the same as a fresh computer seutp. UAT (sometimes a VM) and then Pilots are done on production machines.
We confirm out test items in 2 basic scenerios for each OS we support:
1. Fresh/New Install
2. Upgrade
TEST items
1. Does it install as expected
2. Does it launch and run as expected for both Admin nad limited rights users
3. Are custoizations applied as expected for both Admin and limited rights users
4. Are customizations applied to each user that logs on to machine (Just for reference, this is usually tested with #3 when testing both types of accounts)
5. Uninstall, confirm files are removed and also customizations. I usually do not worry too much about per user data, cause that is a pain to remove for all users, and generally is low risk.
Checking the event log is a good idea... I will have to start doing that.