I'm wondering how you check and test new applications, when you install it in your environment. For example you repackage some app and you have to check conflict with other apps, libraries, dlls. What do you check exactly, What kind of test you do? Do you use any special software for it?

0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


The first step is Windows Installer validation, then conflict-detection/fixing (not performed by everyone, note), then deployment to a clean-build test workstation (probably a VM or VPC on the packager's machine), then UAT (again, not done everywhere). For many shops, if the app installs and runs to an opening dialog or log-in screen (e.g. host connectivity apps) on a clean-build workstation, then it's good to go. Much depends on your desktop people (if you're in a corporate environment), whether or not you have a QA dept/process and so on.

Validation and conflict-handling are built-in to the main vendor's authoring tools.
Answered 06/19/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity