Testing Repackaged Applications
After repackaging an application, who will test that application and is there any document to mention the report of testing and what are all the things they will test
Answers (5)
Really?
It will be specific to your needs. Everyone will more than likely be different.
First you should test your apps on a VM or a test rack. Then test it on a small group of production machines, such as your IT dept machines, willing testers, your bosses workstations, etc and await feedback. Staff that is skilled in usage of the program the app installs should give you the feedback.
Comments:
-
This is a good starting point. Make sure that the application installs first - use a VM or test box, unless you have some magical power to make things work on the first try.
Once you know that the install works and can launch the main executable, it's time to get the application expert involved. There's nothing worse than doing a large deployment of an application and not having someone else say "it works the way it is supposed to" before doing the deployment.
Testing should be the responsibility of the application expert. You may know how to use it, but unless you manage it, make the owner determine whether it works or not. - Arminius 12 years ago
I Just wanna make few points here, I worked for 3 different clients everyone has their own environment set up for testing the apps after packaging before deployments but the common things i observed are
- after developing the package jus test in VM machines, install the application as an adminstrator and log into the same machine with some test user account which has equal privilages as a normal user in the enterprise envirement and test it
- If its okay with above test next level is UAT (User Acceptense Test) which should be done by Actual user who exactly uses that perticuler application.
- To perform UAT you need to take a machine which has your organisations's basic standard image (I think you ll get it from Desktop Admins) and Install your application in that. Now ask the user to log in and test the application (either remotly or Physically).
- If everything is okay with above step now make an appointment with SCCM admin (who ever the deployment specialist accng to your company) and perform the pilot push into some of the user machines and observe the behaviour of the application.
- Take the pilot push reports and if everything is okay with that you can go for LIVE PRODUCTION DEPLOYMENT.
This is jus according to my knowledge, hope this helps you
TY
Comments:
-
thanks for that ontari...can you elaborate it bit more..... - jay25oct 12 years ago
- Check whether you have applied the standards as per your customer's standard document
- Package Validation
- Conflict Check (If required)
- Check Installation and Create log file for the same
- Check your application atleast in 2 standard user account for the consistancy. Also you have to check your application in Admin account as well to check is there any difference in functionality in Admin and Standard users
- Check Self-Heal/Repair (Create log file)
- Ensure that the basic functionality of the application is working fine. In addition to this if your customer provides any test cases then you have to check it on
- Check other stuffs like odbc, environment variable, file associations, add/remove program icon, etc.. etc.. confirm that everything is as expected
- Check whether you have applied packaging best practices
- Check Uninstallation and create log files
- Check log files.. It should not have any error
- Check Event Viewer..
- Check core application's functionalities like Office, Adobe etc.. once you have uninstall your package
- Reboot your system after uninstallation of the package and ensure that your system restarts properly without giving any bluescreen :)
A User Acceptance Test or UAT is conducted by Clients on their end in which they install the application from deployment tool and then ask the end users to test the application based on their needs. There are lots of applications which require credentials and so we cannot test them at our end. There might be drive mappings/databases to connect to and a lot other things.
You should only worry to individual testing and a good response from all have summarized most of the points.
