Skip to main content

Type of Reviews

In Software Testing Review is very important way to improve the quality of the software. In this method defects identifies in very early stage of SDLC so it is very easy to fix them and it is very cost effective.

Here i am described you the type of Reviews.

1. Walkthrough: Walkthrough is performed by the Author of the software. Author mentioned each and every steps in proper way so that the participants who are from the software or the outside of the software can easily be understand the software. During Walkthrough, Author check with participants that no defects is missed in the document. In Walkthrough, the software document is present for the stackholders both within and outside the software to make the software understandable. If any point which is not understandable they can provide the alternative solution for that.

2. Technical Review: Technical Review is the discussion in the meeting to discuss about the Technical points within the documents. Technical Review is lead by the Technical Moderators or by the Technical Experts. It is Often performed as a Peer Review without Management Participation.
This is a Defect detection process in which report created with list of issue that need to be addressed.

3. Inspection: Inspection is the most formal review method and lead by the moderator. The document prepared in the Inspection and check by the Reviewer before the meeting, compare it with the product, source or other references. The defect found during Inspections being logged.  Inspection help the quality of the document, Remove defect efficiency as soon as possible, improve product quality by producing high quality of document and create the common understanding between the inspection participants. 

Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.