Application support/Production release minimum requirement
Hi all. Just want to bounce some ideas of the collective head....
In the past, my company has been very relaxed (if not careless) about what are the requirements for new applications that are being released to production and being supported by both Production and NonProd support teams.
As the result of some major production outtages and the inability of support teams to cope with those appropriately, the management asked PM, DEV, Support and QA teams to come up with a list of minimum items that application should do before its both released to Production and supported by different teams.
As part of that, QA was asked to come up with things that should be happening from QA perspective.
The current questions are (subective Yes/NO):
1. End to end business functionality (e.g. workflow and key business process) has been tested by QA (and the users when is necessary) and is functioning as expected?
2. Formal adherence to independent testing within controlled QA environment?
3. Confirm adequate Functional Testing?
4. Confirm adequate Non-Functional Testing (performance/capacity, soak, unit, integration, system, monitoring and destructive testing)?
5. Test Automation Employed?
1. Post Mortem for all bugs to identify deficiencies in tests?
2. Test plan expansion for all bug fixes?
3. Collection of statistics on defects to identify defect hotspots and proactively target troublesome components?
4. All High Priority problems as defined by project are resolved or workarounds have been developed and accepted by users?
Immediate additions I had were these---------:
1. Is there independent QA employed to test application?
2. Testing and artefacts are traceable and reviewed?
Anyone else can think about something else that I am missing or I dont need.....
Last edited by tottallyoff; 05-16-2013 at 07:15 AM.