SQ and Testing Life Cycle specified by IEEE and ISO standards:

Review of the software requirement specifications

Objectives is set for the Major releases

Target Date planned for the Releases

Detailed Project Plan is build. This includes the decision on Design Specifications

Develop Test Plan based on Design Specifications

Test Plan : This includes Objectives, Methodology adopted while testing, Features to
be tested and not to be tested, risk criteria, testing schedule, multi-
platform support and the resource allocation for testing.

Test Specifications
This document includes technical details ( Software requirements )
required prior to the testing.

Writing of Test Cases
Smoke(BVT) test cases
Sanity Test cases
Regression Test Cases
Negative Test Cases
Extended Test Cases

Development – Modules developed one by one

Installers Binding: Installers are build around the individual product.

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

Testing
Smoke Test (BVT) Basic application test to take decision on further testing

Testing of new features
Cross-platform testing
Stress testing and memory leakage testing.

Bug Reporting
Bug report is created

Development – Code freezing
No more new features are added at this point.

Testing
Builds and regression testing.

Decision to release the product
Post-release Scenario for further objectives.

Software Testing Life Cycle

Software Testing Life Cycle:

Software testing life cycle or STLC refers to a comprehensive group of testing related actions specifying details of every action along with the specification of the best time to perform such actions. There cannot be a standardized testing process across various organizations, however every organization involved in software development business, defines & follows some sort of testing life cycle.
 
1. Test Planning
Prepare the test plan document, and test cases.

2. Test Development
Preparing requirements documents, Use Case documents, Traceability documents.

3. Test Execution
Executing all Test cases and filling actual results using testing tools and utilities.

4.Result Analysis
Comparing expected results with actual results.

5. Bug Tracking
Filed bugs are identified, isolated and managed.

6. Reporting
Bug Reporting process is the reporting of bugs in a database to track further.