Waterfall Software Testing is a type of software testing in which the different testing levels are performed one after the other. It involves the testing team members and unlike the agile testing development team is not involved in the testing phase. Testing team basically performs the testing operation once the full development of the software or the product is complete. Only after the completion of development life cycle, the testing life cycle begins. Once the software is fully developed then only the testing operation are performed.
Objective of Waterfall Testing:
The objective of the Waterfall testing is:
- To detect the defects in the software product or the application.
- To test the system or application once development is complete.
- To find all the defects at the same time.
- To carry out testing processes in a order.
Features of Waterfall Testing:
- Testing is considered as a separate phase.
- Testing is performed only after the development phase is complete.
- Development team is not involved in the testing work.
- Testing is performed in a level manner.
- Another testing takes place only after the completion of the previous one.
Waterfall Testing Representation:
Advantages of Waterfall Testing:
The advantages of Waterfall Testing are:
- As the development team is not involved so workload of developers are reduced.
- Involvement of may minds leads to a worse conclusion and creates problem in decision making hence there is no such problem in waterfall testing as development and testing team doesn’t work together.
- Less time consuming as testing is not performed in each iteration.
- All defects are detected at the same time.
- Development work and testing work is separate that improves software quality.
- There is not barrier in development phase.
Disadvantages of Waterfall Testing:
The disadvantages of Waterfall Testing are:
- If one test fails there is stoppage and further testing can’t be processed.
- Sometimes it may be more time consuming as the several defects are defected at the same time.
- The workload of testing team is increased.
- Testing team performs tests in level-wise manner that may lead to time consuming.
- Software quality may be low as compared to agile testing.
- Difference between Agile Testing and Waterfall Testing
- Software Engineering | Failure of Waterfall model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Classical Waterfall Model
- Software Engineering | Differences between Sanity Testing and Smoke Testing
- Software Engineering | Comparison between Regression Testing and Re-Testing
- Difference between Software Testing and Embedded Testing
- Gray Box Testing | Software Testing
- Sanity Testing | Software Testing
- Software Testing | Scalability Testing
- Stress Testing | Software Testing
- Software Testing | Reliability Testing
- Acceptance Testing | Software Testing
- Unit Testing | Software Testing
- Smoke Testing | Software Testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.