Is there any standard procedure to test the application as a whole? Or How can I test complete application right from the requirement gathering?
Here are the broad steps to test the application :These are the standard SQA peocesses to be followed in any application testing.
- Marketing Requirements
Objectives remaining to be completed are carried forward for the next release.
- Branching for the development cycle
- Objectives settings for the Major and customized releases
- A Detailed Project Plan and the release of design Specifications
- QA – Develop Test Plan based on Design Specifications
This includes Objectives, Methodology adopted while testing, Features to be tested and not to be tested, risk criteria, testing schedule, cross-platform support and the resource allocation for testing.
Feature Test Plan : This document talks about how the testing is going to be carried out for each type of testing.
- QA – Functional Test Specifications
Application Development : Considering the product features, tester has to make ready his/her own test suit.
- QA – Writing of Test Cases (CM)
- Sanity Test cases
- Regression Test Cases
- Extended Test Cases
- Negative Test Cases
- Development – Goes on Module by Module.
- Installers Binding and Building
- Release Engg is responsible for releasing the Builds.
- Release Engg collects fresh/developed code from the developer’s initially/module wise.
- Installers have to take care of jar files updating, registry entries, and additional software installations.
- Build Procedure :
- For each build one or 2 CDs are made/build the same are pushed to Pune/Chennai based on the priority.
- Each product build are received in the form of zip files under http://pun-qaftp/ftproot/QA-Builds ( Pune-Specific). The procedure goes along for Chennai. San Jose QA picks up builds from Nexus ( Build Specific Server )
- The same zip files need to be unzipped to get the desired installer and the same is put at Pun_fps1/QA/Builds folder. ( Pune-Specific)
- QA – Testing :
- Smoke Test results has to be posted on http://Chaquita which is an official site for posting Smoke
- Test results and to share the basic testing information.
- Prepare Smoke Test procedure.
- QA – Extensive testing :
- Document review
- Cross-platform testing
- Stress testing and memory leakage testing.
- QA- Bug Reporting :
- Further FET (Fixed Effectiveness testing) of the filed bugs.
- Exception study and verification.
- Development – Code freeze :
- QA – Testing :
- QA- Media Verification :
- Decision to release the product :
- Post-release Scenario :
Post release review meeting to decide upon the objectives for the next release.
http://www.softwaretestinghelp.com/sqa-processes-how-to-test-complete-application/
No hay comentarios.:
Publicar un comentario