Free Training
C Language   |   CSS   |   MainFrame   |   VBScript   |   PHP   |   XML   |   C++ Tutorials   |   Ajax   |   JavaScript   |   CSS3   |   UML   |   jQuery   |   Microsoft AJAX

Sponsored Links

Testing Tutorials

 
Home Tutorials Testing
 

Life Cycle of Testing Process

 

Life Cycle of Testing Process

Page 1 of 2
This article explains about Differant steps in Life Cycle of Testing Process. in Each phase of the development process will have a specific input and a specific output. Once the project is confirmed to start, the phases of the development of project can be divided into the following phases:
  • Software requirements phase.
  • Software Design
  • Implementation
  • Testing
  • Maintenance


In the whole development process, testing consumes highest amount of time. But most of the developers oversee that and testing phase is generally neglected. As a consequence, erroneous software is released. The testing team should be involved right from the requirements stage itself.


The various phases involved in testing, with regard to the software development life cycle are:


 


 


 


1. Requirements stage
2. Test Plan
3. Test Design.
4. Design Reviews
5. Code Reviews
6. Test Cases preparation.
7. Test Execution
8. Test Reports.
9. Bugs Reporting
10. Reworking on patches.
11. Release to production.


Requirements Stage

Normally in many companies, developers itself take part in the requirements stage. Especially for product-based companies, a tester should also be involved in this stage. Since a tester thinks from the user side whereas a developer can’t. A separate panel should be formed for each module comprising a developer, a tester and a user. Panel meetings should be scheduled in order to gather everyone’s view. All the requirements should be documented properly for further use and this document is called “Software Requirements Specifications”.


Test Plan

Without a good plan, no work is a success. A successful work always contains a good plan. The testing process of software should also require good plan. Test plan document is the most important document that brings in a process – oriented approach. A test plan document should be prepared after the requirements of the project are confirmed. The test plan document must consist of the following information:

• Total number of features to be tested.
• Testing approaches to be followed.
• The testing methodologies
• Number of man-hours required.
• Resources required for the whole testing process.
• The testing tools that are to be used.
• The test cases, etc


Test Design


Test Design is done based on the requirements of the project. Test has to be designed based on whether manual or automated testing is done. For automation testing, the different paths for testing are to be identified first. An end to end checklist has to be prepared covering all the features of the project.

The test design is represented pictographically. The test design involves various stages. These stages can be summarized as follows:

• The different modules of the software are identified first.
• Next, the paths connecting all the modules are identified.

Then the design is drawn. The test design is the most critical one, which decides the test case preparation. So the test design assesses the quality of testing process.


Test Cases Preparation

Test cases should be prepared based on the following scenarios:

• Positive scenarios
• Negative scenarios
• Boundary conditions and
• Real World scenarios


Next Page: Life Cycle of Testing Process - Page 2


Read Next: WinRunner - TSL Functions



 

 

Comments


Kots said:

  Hi
The article is very informative,
Thanks & Regards
Kots.
September 8, 2006, 11:04 am

ugan said:

  this is good
November 7, 2008, 8:09 pm

Rahul said:

  Nice One

Regards
Rahul bagati
November 18, 2008, 1:50 am

0 said:

  This topic is very informative and helpful
November 27, 2008, 7:06 am

vikram said:

  good one
January 5, 2009, 12:41 am

priya said:

  Thanks for the notes.It is very informative
January 22, 2009, 3:50 pm

Anand said:

  Excellent Article.
January 23, 2009, 2:32 pm

swathi n said:

  thank u soo much. its excellent .
February 1, 2009, 1:33 pm

Rajesh said:

  yes good attempt
February 16, 2009, 2:46 am

DK Parsai said:

  Good attempt, except that there can be a few modifications.

1. Code Review is not necessary except in case of White Box Testing. Unit testing should NOT be a responsibility of the tester.

2. Bug reporting will come after Test Execution and Test Report will be the last activity before Release to Manufacturing/ Production.

So the steps above would be more like:
7. Test Execution
8. Bugs Reporting
9. Regression Testing

This loops to Step 8 and finally when desired bug open to fixed level is reach Step 10 Test Report detailing the testing efforts and remaining open issues and why they are not fixed and why it is recommended for release.

There is a difference between Bug Report and Test Report.

10. Test Reports
11. Release to production.
April 17, 2009, 3:42 pm

Post Your Comment:

Members Please Login
Your Name:*
e-mail ID:(required for notification)*
Image Verification: 
 
 Subscribe    

Sponsored Links