Walkthrough in software testing is used to review documents with peers, managers, and team members who are guided by author of the document to gather feedback.

1. WALKTHROUGH
NANDHITA.B
DEPARTMENT OF COMPUTER SCIENCE
NADAR SARASWATHI COLLEGE OF ARTS AND
SCIENCE

2. WALKTHROUGH
• Walkthrough in software testing is used to reviewing the
documents with managers, team members who guide by the
author for the document to gather feedback and consensus.
• The walkthrough is the formal way of testing, no formal
authority is been involved in this testing.
• During this process, participants ask question and comment on
potential errors, deviation from development standards, and
other issues.

3. WALKTHROUGH
• A software walkthrough is done for several reasons.
• Here are some reasons:
 To gather feedback on technical quality of the document.
It helps identity and rectify errors in the early stages of SDLC.
• When is Software Walkthrough Needed?
 To review the source code.
It is valuable for reviewing Software Documentation.

4. WHERE IS A SOFTWARE WALKTHROUGH
DONE?
• Meeting Rooms.
• Virtual Meeting.
• In Testing Environment.
• Conference Rooms.
• Within the Development Environments.

5. STRUCTURED WALKTHROUGH
PARTICIPANTS
• AUTHOR: The author of the document under review.
• PRESENTER: The presenter usually develops the agenda.
• MODERATOR: The moderator facilitates the walkthrough
session, ensures the walkthrough agenda is followed.
• REVIEWERS: The reviewers evaluate the document under test to
determine if it is technically accurate.

6. MEMBERS OF THE WALKTHROUGH
• Project Leader.
• Other members of the project team.
• Quality assurance group representative.
• Technical Writer.
• Team members.

7. CHALLENGES
• Team members from different cultural backgrounds may face
challenges expressing their opinions freely.
• In effective communication can hinder the success of a
walkthrough.
• Getting key stakeholders to participate in the walkthrough can
be difficult.

8. ADVANTAGES
• To explain and discuss the information in the document.
• To verify the validity of the system.
• Acts as a “proof of concept” at an early stage.
• Increases the knowledge of the entire team related to thw code in
question.
• Incorporates multiple perspectives.
DISADVANTAGES
• It is not suitable for large projects as the size of the project may
make it more challenging to review thoroughly.