Is there any standard procedure to test the application as a whole? Or How can I test the complete application right from the Requirement gathering phase?
This tutorial includes the entire steps to test the application: These are the standard SQA processes to be followed in any application testing.
What You Will Learn:
SQA Processes: How to Test Complete Application?
The marketing requirements include:
- Review of the Objectives set for the Last Released Build.
- Objectives remaining to be completed are carried forward for the next release.
Branching for the Development Cycle
Objective Settings for the Major and Customized Releases.
Target Date planned for the Releases and decision on the entire project schedule that it is required to achieve these target dates.
A Detailed Project Plan and the Release of Design Specifications
This includes the decision on Design Specifications (Products), review of the design specs, and development schedule. This involves the QA during the phase of review.
QA – Develop Test Plan based on Design Specifications
Test Plan: This is a top-level document that talks about how the product is going to be tested. This includes objectives, the method 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 explains how the testing is going to be carried out for each type of testing.
QA – Functional Test Specifications
This document includes technical details (Software requirements) required prior to testing. It is important from the tester’s point of view to understand and plan the technical resources prior to testing.
Application Development: Considering the product features, the tester has to make his/her own test suit.
QA – Writing of Test Cases (CM)
- Smoke (BVT) Test Cases
- Sanity Test Cases
- Regression Test Cases
- Extended Test Cases
- Negative Test Cases
Installers Binding and Building
- 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 is 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 in Pun_fps1/QA/Builds folder. (Pune-Specific)
QA – Testing
- Smoke Test (BVT) to check the 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 a Smoke Test procedure.
QA – Extensive Testing
- Testing of new features
- Document review
- Cross-platform testing
- Stress testing and Memory Leakage testing.
QA- Bug Reporting
- Use of Trackweb’s “Soffront” as the Bug Tracking tool.
- Further FET (Fixed Effectiveness testing) of the filed bugs.
- Exception study and verification.
Development – Code freeze
- No more new features are added at this point.
QA – Testing
- Candidate Builds and regression testing.
QA- Media Verification
- CDs are cut for the released products and the product is installed using those CDs and it takes place in San Jose.
Decision to Release the Product
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.
Please share your thoughts in the comments section below!