What is Inspection in software testing?


  • It is the most formal review type
  • It is led by the trained moderators [Read more...]

What is Technical review in software testing?

Technical review:

  • It is less formal review
  • It is led by the trained moderator but can also be led by a technical expert [Read more...]

What is Walkthrough in software testing?


  • It is not a formal process/review
  • It is led by the authors [Read more...]

What is test design technique?

By design we mean to create a plan for how to implement an idea and technique is a method or way for performing a task. So, Test Design is creating a set of inputs for given software that will provide a set of expected outputs.  [Read more...]


What is a static test technique?

Static test techniques provide a great way to improve the quality and productivity of software development.  It includes the reviews and provides the overview of how they are conducted. The primary objective of static testing is to improve the quality of software products by assisting engineers to recognize and fix their own defects early in the software development process.

Also See: What is static testing technique?


What is static Testing?

  • Static testing is the testing of the software work products manually, or with a set of tools, but they are not executed.
  • It starts early in the Life cycle and so it is done during the verification process.
  • It does not need computer as the testing of program is done without executing the program. For example:  reviewing, walk through, inspection, etc.

What are the uses of Static Testing?

 The uses of static testing are as follows:

  • Since static testing can start early in the life cycle so early feedback on quality issues can be established.
  • As the defects are getting detected at an early stage so the rework cost most often relatively low.
  • Development productivity is likely to increase because of the less rework effort.
  • Types of the defects that are easier to find during the static testing are: deviation from standards, missing requirements, design defects, non-maintainable code and inconsistent interface specifications.
  • Static tests contribute to the increased awareness of quality issues.

What is Informal reviews?

Informal reviews are applied many times during the early stages of the life cycle of the document. A two person team can conduct an informal review. In later stages these reviews often involve more people and a meeting. The goal is to keep the author and to improve the quality of the document. The most important thing to keep in mind about the informal reviews is that they are not documented.


What is Formal review?

Formal reviews follow a formal process. It is well structured and regulated.
A formal review process consists of six main steps:

  1. Planning
  2. Kick-off
  3. Preparation
  4. Review meeting
  5. Rework
  6. Follow-up [Read more...]

What are the roles and responsibilities involved during a review?

During a review four types of participants take part. They are:

  1. The moderator:
  • Also known as review leader
  • Performs entry check
  • Follow-up on the rework
  • Schedules the meeting
  • Coaches other team
  • Leads the possible discussion and stores the data that is collected
  1. [Read more...]