Software testing is an essential part of software quality assurance. It is a process that consists of all lifecycle activities, both static and dynamic, related to the planning, preparation and evaluation of software products and related work products to determine if they meet specific requirements, demonstrate that they are suitable for your purpose and detect defects. Reviews are a type of test in which a group of people discuss the product produced by the developer, detect errors, and attempt to correct them systematically. There are different types of reviews that can be performed at different stages of software development.
For instance, an informal review can be conducted before a technical review, or an inspection of a requirements specification can be done before a guided tour with customers. This helps to minimize the cost of software, since it is easier to record and fix defects in the early stages. Software testing methodologies are broadly divided into two categories: static techniques and dynamic techniques. The advantage of testing at all stages is that it helps to find different types of defects at different stages of software development.
It is clear that none of the following types of reviews are the “winner”, but they serve different purposes at different stages of a document's lifecycle. If the project has a significant number of errors, the team rejects the model, requests modifications, and holds another review meeting. If there are only a few errors, they ask that the errors be corrected and there are no further review meetings. When testing the software, the test engineer seeks to find errors in the system to uncover any undiscovered errors.
