How do you test your packages?
Hey all
What kind of procedures, tasks and documents do you use for your software (packages) testings?
Who is responsible?
What are the main steps to take into consideration?
Thanks for any input or sample docs.
Roland
What kind of procedures, tasks and documents do you use for your software (packages) testings?
Who is responsible?
What are the main steps to take into consideration?
Thanks for any input or sample docs.
Roland
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
AngelD
18 years ago
1. After a repackage or modification there is another packager doing a QA on the package verifying that the package is okey.
2. Test distribution (install & remove) in a Lab environment similar to the production env.
3. A responsible person for each application that will perform the functionality test and aprove that the application is working correct.
These steps are also made for patches.
2. Test distribution (install & remove) in a Lab environment similar to the production env.
3. A responsible person for each application that will perform the functionality test and aprove that the application is working correct.
These steps are also made for patches.
Posted by:
turbokitty
18 years ago
Testing Procedures
1. Silent and UI Installation (always)
2. Product Functionality (as per handover document - always)
3. Uninstall (always)
4. Differencing (if issues)
5. Application Cleanup (always)
6. Different locked down user (always)
Explanations:
1. run misexec /i "msi" /qn and run the UI msi install as an admin to be sure it doesn't bomb out.
2. test the application to be sure it's working properly. This info should come from the business analyst if possible
3. run misexec /x "msi" /qn and run the UI msi uninstall as an admin to be sure it doesn't bomb out. (clean O/S with patches that match production)
4. If there are issues, install your msi, run a repackaging scan, install the vendor MSI overtop, run the final repackaging scan. see what's missing.
5. do a repackaging scan, install repackaged msi, run program, ununstall, run post-scan. see what's left behind after an uninstall
6. install, login as different user, test functions.
1. Silent and UI Installation (always)
2. Product Functionality (as per handover document - always)
3. Uninstall (always)
4. Differencing (if issues)
5. Application Cleanup (always)
6. Different locked down user (always)
Explanations:
1. run misexec /i "msi" /qn and run the UI msi install as an admin to be sure it doesn't bomb out.
2. test the application to be sure it's working properly. This info should come from the business analyst if possible
3. run misexec /x "msi" /qn and run the UI msi uninstall as an admin to be sure it doesn't bomb out. (clean O/S with patches that match production)
4. If there are issues, install your msi, run a repackaging scan, install the vendor MSI overtop, run the final repackaging scan. see what's missing.
5. do a repackaging scan, install repackaged msi, run program, ununstall, run post-scan. see what's left behind after an uninstall
6. install, login as different user, test functions.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
