Scribd
Upload
7 views

Software Testing & Quality - Wk3

Uploaded by

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

Software Testing & Quality - Wk3

Uploaded by

moayyadsmra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Click to edit Master title style

Software Testing & Quality


Inspections, Walkthroughs & Reviews

1
Click to edit Master title style

Inspections,
Walkthroughs & Reviews

2 2
Click to Testing
Human edit Master title style

• Codes should be human-readable (Since 1970s)


• Factors affect human testing practice:
1. The size or complexity of the application
2. The size of the development team
3. The timeline for application development
4. The background and culture of the programming team
• Time: between coding finished and computer-based
testing

3 3
Click to Testing
Human edit Master title style

• Why does it matter?


1. Finding bugs in earlier stages makes corrections cheaper
2. Due to time pressure, programmers tend to produce more bugs
during computer-based testing
• What are the methods?
1. Code inspections
2. Walkthroughs
3. User (or usability) testing

4 4
Click to edit&Master
Inspections Walkthroughs
title style

• Advantages
1. Involve people other than the author (vs desk-checking)
2. Locate bugs more precisely (vs black-box testing)
3. Good at verification, can find 30-70% logic design and coding
errors
• Disadvantages
1. Bad at validation or finding high-level design errors
2. Only good at finding certain types of errors, complementary to
computer-based testing (e.g. uninitiated variables vs division by
zero)
• Can be applied to regression testing

5 5
Click to edit Master title style
Inspections

• A team of 4 people (a moderator, the author, possibly


the program’s designer and a test specialist)
• Moderator duties:
1. Distributing materials for, and scheduling, the inspection
session (several days in advance)
2. Leading the session
3. Recording all errors found
4. Ensuring that the errors are subsequently corrected

6 6
Click to edit Master title style
Inspections

• During the session:


1. The programmer narrates, statement by statement, the logic of
the program. During the discourse, other participants should
raise questions, which should be pursued to determine whether
errors exist. It is likely that the programmer, rather than the
other team members, will find many of the errors identified
during this narration. In other words, the simple act of reading
aloud a program to an audience seems to be a remarkably
effective error-detection technique.
2. The program is analyzed with respect to checklists of
historically common programming .

7 7
Click to edit Master title style
Inspections

• Focus on finding errors, not correcting them


• Sometimes correction proposal might lead to detection of
flawed overall design
• The optimal amount of time for the inspection session appears
to be from 90 to 120 minutes
• Most inspections proceed at a rate of approximately 150
program statements per hour
• Large programs should be examined over multiple inspections,
each dealing with one or several modules or subroutines
• The results of an inspection should be confidential
• Create a cooperative culture and learn from each other
• Locate most error-prone sections in the program

8 8
Click to edit
Checklist: Data
Master
Reference
title style
& Computation Errors

9 9
Click to edit
Checklist: Data
Master
Declaration
title style
& Comparison Errors

1010
Click to edit
Checklist: Control
MasterFlow
title&style
I/O Errors

1111
Click to edit
Checklist: Interface
Master title
& Other
styleErrors

1212
Click to edit Master title style
Walkthroughs

• An uninterrupted meeting of one to two hours in


duration
• A team of 3-5 people, including a moderator, a secretary,
a tester, and:
1. A highly experienced programmer
2. A programming-language expert
3. A new programmer (to give a fresh, unbiased outlook)
4. The person who will eventually maintain the program
5. Someone from a different project
6. Someone from the same programming team as the
programmer

1313
Click to edit Master title style
Walkthroughs

• The tester should prepare a set of paper test cases and


“run” them manually
• The rest of procedure, follow-up, and side effects are
similar to that of the inspection

1414
Click Checking
Desk to edit Master
& Peer
title
Ratings
style

• Desk checking: one person inspection


• Peer rating: a technique of evaluating anonymous
programs in terms of their overall quality, maintainability,
extensibility, usability for programmer’s self-evaluation
1. 6-20 participants
2. Each submits 2 programs to review
3. 30 minutes to review each program
4. On a scale from 1 to 10, answer (a tentative list):
q Was the program easy to understand?
q Was the high-level design visible and reasonable?
q Was the low-level design visible and reasonable?
q Would it be easy for you to modify this program?
q Would you be proud to have written this program?
1515
Click2to
Lab (Code
edit Review)
Master title style

• Lab 2 (Code Review)


• Ask one of your classmates (not from your group) for a Python
program whose size is about 150 lines (max: 200)
• Review the code according to the checklist (data reference, data
declaration, computation, comparison & interfaces) provided by
our textbook
• Identify the items not applicable to Python in that checklist and
write a report
• Turn in your report and the code you review
• You gain 5 extra points if you give your program to your
classmate to test
• Each group shares one and only one sample program among
your group members to test but every student should do their
review and report independently (you will get 0 for plagiarism)
• 50% Find out applicable items + 50% code review + extra points
• Due: 10/7 Sun 24:00 1616
Click to edit Master title style

Thank You!

17

You might also like