As promised earlier, I'm writing few more requirements that would help you folks in preparing for testing. As always, I would request you all to post your comments so that all the testers could make their job easier. If you have missed to read the other checklists, please Click here.
Procedures to add/delete or update hardware components are existing and followed
The test environment components are sized in relation to the production environment
Log files are available for the different applications deployed on the test environment
Disaster recovery plan is known, documented, implemented and trained to everyone in the team
Procedure exists to request and add test users for any application in the test environment
Unexpected downtime of the test environment is communicated to all the stakeholders (preferably using a central communication channel - for instance an intranet website to avoid miscommunication and other issues)
Physical locations of different infrastructural components are identical to the production environment and documented. Any deviation is clearly identified and approved by the project team
We are agile enough to patch and refresh data properly which improved the test experience drastically.
Deployment or Release management requirements
- Version control is applied to all development products and system documentation, it is highly recommended to use a SVN or rational Clear-case or Git something would be good instead of manual.
- Deployments are always done from 1 agreed central data store
- Roll-back scenario's are in place for every deployment cycle
- Users (both the dev team and the testing team) are trained and informed about deployment agreements
- A patch procedure is known, documented and implemented
- Deployment tasks follow formalized checklists (should be verified by the test team)
- Builds or data refreshes in a test environment take only place after approval of the impacted test teams
- A deployment/release management role is assigned
- Every defect fixed for a new deployment in the test environment is at least communicated within an agreed defect management tool
- Every deployment should come along with the build release note
- Builds are subject to formal and/or informal entry criteria
Maintainability requirements
Procedures to add/delete or update hardware components are existing and followed
The test environment components are sized in relation to the production environment
Log files are available for the different applications deployed on the test environment
Disaster recovery plan is known, documented, implemented and trained to everyone in the team
Procedure exists to request and add test users for any application in the test environment
Unexpected downtime of the test environment is communicated to all the stakeholders (preferably using a central communication channel - for instance an intranet website to avoid miscommunication and other issues)
Physical locations of different infrastructural components are identical to the production environment and documented. Any deviation is clearly identified and approved by the project team
We are agile enough to patch and refresh data properly which improved the test experience drastically.
Join our community in Facebook and Google+ at the below URL's to stay up to date:
Facebook Page: http://www.facebook.com/SoftwareQaHelp
Google+ : https://plus.google.com/101680718973348361876
Facebook Page: http://www.facebook.com/SoftwareQaHelp
Google+ : https://plus.google.com/101680718973348361876
No comments:
Post a Comment