For example, an informal review can be performed before a technical review, or an inspection of a requirements specification can be performed before a guided tour with customers. This helps to minimize the cost of software, since it is easier to record defects and correct them in the early stages of software development. software testing methodologies are broadly divided into two, namely, static techniques and dynamic techniques. The advantage of testing at all stages is that they help to find different defects at different stages of software development.
Clearly, none of the following types of revisions are the “winner”, but the different types serve different purposes at different stages of a document's lifecycle. A review is a type of test in which a group of people discuss the product produced by the developer, detects errors, and attempts to correct them systematically. If the project has a significant number of errors, they reject the model, request to modify it, and hold another review meeting. It is clear from the above definition that a software review is as essential as software testing.
If the project only has a few errors, the team asks 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 find an undiscovered error. Software testing 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. From the definition of software testing, it is clear that software testing constitutes the fundamental component of software quality assurance.