I am currently writting a general document/checklist for testing software packages, that have been packaged. I want to know what everyone else has on their checklist, if one is used?

Hope that makes sense!
0 Comments   [ + ] Show Comments

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.

Answers

0
People will no doubt have their own lengthy check list, and a lot of it will relate to the specific packaging standards that are implemented (assuming they have any) but the main points to check are as follows;

1) Packaging documentation is satisfactory (install routine, prerequisistes, MSI / MST customistations etc)
2) Package installs silently (from command line and/or deployment tool of choice)
3) Package upgrades any previous versions sucesfully
4) Software works under locked down user account (obviously this is key)
5) Package uninstalls cleanly (for me, the most important point)

I could go on and on but this should get you started... [:)]

Cheers,
Rob.
Answered 12/15/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Don't forget:

Test package as non privileged user
Answered 12/15/2009 by: pjgeutjens
Red Belt

Please log in to comment
0
My current client has begun clamping down on Production releases without UAT sign-off. Luckily, some wonk somewhere devised this list which the BU must complete and return for attachment to the release document. It's pretty basic but it's a start:

- All expected shortcuts present
- Excluded shortcuts absent
- (ditto for features)
- Application starts without error
- Application performs as expected (in terms of load-time, window drawing, etc)
- Application files can, if relevant, be:
- opened
- saved
- printed
- Application doesn't conflict with other BU's apps
- Application closes without error
Answered 12/16/2009 by: VBScab
Red Belt

Please log in to comment
0
We follow this procedure once the software has been discovered, packaged and conflict managed:

Install package on clean standard build machine.
Launch application and test basic funcitonality i.e help and menus.
Uninstall package on clean standard build machine.

Set up Package for deployment.
Install from deployment on a clean machine.
Launch application and test basic funcitonality i.e help and menus.
Uninstall package on clean standard build machine.

Launch all core applications on the standard build machine and test basic funcitonality i.e help and menus.

Deploy for UAT to a test account that will be used by a user in the business for full functionality testing. Then get that user to sign off the UAT when they are happy that the package is functioning correctly.
Answered 12/16/2009 by: t_claydon
Senior Yellow Belt

Please log in to comment
0
Found a few samples, like this, for example.
Answered 12/16/2009 by: VBScab
Red Belt

Please log in to comment
0
Thanks a lot guys! This helps me out a lot!
Answered 12/16/2009 by: cwilkins
Senior Yellow Belt

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