8/13/2019 Introduction - Practical Software Testing

1/2

Test Process:-> Project familiarity meeting

- understanding the client,- Project duration and delivery dates- People involved in the project like PM, tech leads, QA leads, devs, te

sters....-> Developing the project plan

- Understand the SRS (Software Requirement Specification)- Create the test plan and project plan- Develop the test scenarios while the developers are writing code for i

ndividual modules and write code to test each of the modules under development- Cover as much functional test cases from SRS as possible.- Data maintained in Excel or bug tracking tools

-> Testing- Once a module development is finished, start the testing with Smoke te

sting. The module should pass smoke testing inorder to proceed for further testing

- Modules passing smoke testing are tested manually against the test cases written for the first time.

- Bugs found while testing must be logged in bug tracking tool.- On bug fix, do verification testing and regression testing for all the

related modules- If fix passes verification, then the bug is marked as fixed and verifi

ed. Bug closure happens at this stage.

- If the fix fails, then the above steps are repeated until the bug fixhappens correctly and is resolved.

Different tests are performed on individual modules and integration testing on module integration. These tests include:

- Compatibility testing- Load and Stress testing- System testing

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 tobe 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 CasesSmoke(BVT) test casesSanity Test casesRegression Test CasesNegative Test CasesExtended Test Cases

8/13/2019 Introduction - Practical Software Testing

2/2

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.

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

Testing of new featuresCross-platform testingStress testing and memory leakage testing.

Bug ReportingBug report is created

Development Code freezingNo more new features are added at this point.

TestingBuilds and regression testing.

Decision to release the product

Post-release Scenario for further objectives.