Saturday, April 28, 2012

Testing during production deployment:

Last week we had a major production deployment for our existing website.Project team came up with an eight hour estimate whereas testing covered with 2 hours time period. So we are in a position to plan our self to complete the entire testing activities within the scheduled time period.

For this initially, we have prepared some smoke and sanity test cases for existing application and the new enhancements. Also we have included some test cases from regression test suite to this. We executed this smoke and sanity suite as part of our daily testing activities five days prior to deployment, with the intention of getting some hands on experience in execution to reduce the time period during production deployment.

After completing the successful deployment we came up with some checklists for testing the application during production deployment. They are listed below,

1) Get the test login id’s for production server
2) Ask the data team to insert some test data to the test user login or account
3) Check for the “Website Maintenance / Offline messages displayed while accessing the website at the time of        deployment
4) Execute the sanity and smoke test cases which you have prepared to ensure all the major functionalities are working fine
5) Check for any broken links
6) Check for any images missing throughout the application
7) If the website has different group of users, test by using the default user in every group
8) Ensure with the browser you are testing with the project team
9) If there are any configuration or environmental issues during deployment , convey them to the project team immediately
10) Sign off email from QA team to ensure the website is working fine after the deployment

If you want to add some more points to this post please add them in the comments section.

Also please correct me if anything wrong.