0% found this document useful (0 votes)
81 views1 page

Walkthrough vs Inspection in Software Testing

The document outlines the differences between walkthroughs and inspections in software quality assurance. Inspections are formal processes requiring planning and participation from qualified reviewers to verify compliance with standards, while walkthroughs are informal, open-ended sessions involving the entire team without prior preparation. Both methods aim to identify defects, but they differ in structure, preparation, and participant involvement.

Uploaded by

Prabin Magar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
81 views1 page

Walkthrough vs Inspection in Software Testing

The document outlines the differences between walkthroughs and inspections in software quality assurance. Inspections are formal processes requiring planning and participation from qualified reviewers to verify compliance with standards, while walkthroughs are informal, open-ended sessions involving the entire team without prior preparation. Both methods aim to identify defects, but they differ in structure, preparation, and participant involvement.

Uploaded by

Prabin Magar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

DIFFERENCE BETWEEN WALKTHROUGH AND INSPECTION

Inspection: is used to verify the compliance of the product with specified standards and requirements. It is done by examining,
comparing the product with the designs, code, artefacts and any other documentation available. It needs proper planning and
overviews are done on the planning to ensure that inspections are held properly. Lots of preparations are needed, meetings are
held to do inspections and then on the basis of the feedback of the inspection, rework is done.

Inspection is deserving method with careful consideration of an organization, which concerns about the quality of the product.
The process is being done by the quality control department.

Inspection is a disciplined practice for correcting defects in software artifacts.

Walkthroughs: Author presents their developed artifact to an audience of peers. Peers question and comment on the artifact to
identify as many defects as possible. It involves no prior preparation by the audience. Usually involves minimal documentation
of either the process or any arising issues. Defect tracking in walkthroughs is inconsistent.

A walk through is an evaluation process which is an informal meeting, which does not require preparation.

The product is described by the produced and queries for the comments of participants. The results are the information to the
participants about the product instead of correcting it.

Walkthrough Inspection

[Link] is informal process. [Link] is pure Formal process.

[Link] team may participate. [Link] experienced and qualified reviewers can participate.

[Link] ended session. [Link] is time bound review meeting.

[Link] preparation is needed by all participants before


[Link] individual preparation is needed before meeting.
meeting.

[Link] is defect finding, finding out alternative


[Link] defect finding is the objective.
solutions, open ended session.

You might also like