SQA Processes. How to Test complete application?

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 processes to be followed in any application testing.

 Review of the Objectives set for the Last Released Build

Objectives remaining to be completed are carried forward for the next release.

Target Date planned for the Releases and decision on the entire Project schedule that is required to achieve these target dates.

This includes the decision on Design Specifications (Products), review of the design specs and development schedule. This involves QA during the phase of review.

Test Plan: This is a top-level document that talks about how the product is going to be tested

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.

This document includes technical details (Software requirements) required prior to the testing. It is important from the tester’s point of view to understand and plan the technical resources prior to the testing.

Application Development: Considering the product features, the tester has to make ready his/her own test suit.

– Smoke (BVT) test cases

– Sanity Test cases

– Regression Test Cases

– Extended Test Cases

– Negative Test Cases



– Installers are built around the individual product.

– 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.

– A build includes Installers of the available products – multiple platforms.

– For each build, one or 2 CDs are made/build the same are pushed to Pune/Chennai based on the priority.

– Each product build is 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)

– Smoke Test (BVT) to check basic features of the product.

– Smoke Test results have 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.

– Testing of new features

– Document review

– Cross-platform testing

– Stress testing and memory leakage testing.

– Use of Trackweb’s “Soffront” as the Bug Tracking tool.

– Further FET (Fixed Effectiveness testing) of the filed bugs.

– Exception study and verification.

No more new features are added at this point.

Candidate Builds and regression testing.

CDs are cut for the released products and the product is installed using those CDs and it takes place in San Jose.

A review meeting to analyze the performance of the product, which is set and the same is compared with the objectives set.

One branch is kept for the post release modification and hence the product testing.

A post release review meeting to decide upon the objectives for the next release.