/build/static/layout/Breadcrumb_cap_w.png

Application deployment

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?

Regards,

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 15 years ago
Red Belt
0
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ