IV - Static Testing

Question 1

What is Static Testing?

Answer 1

Static testing assesses work products (e.g. documents or code). It is part of the Analysis process.

Question 2

What are the benefits of Static Testing?

Answer 2

Early detection of defects and cost reduction. Easier and cheaper :)

Question 3

What is the difference between Static and Dynamic testing?

Answer 3

Static Testing: Finds defects in work products directly. Is completed BEFORE software is built.

Dynamic Testing: Finds failures. Is completed AFTER software is built.

Question 4

What is a Review?

Answer 4

A type of static testing in which a work product or process is evaluated by one or more individuals to detect defects or to provide improvements.

Question 5

What are the main activities of the Review Process?

Answer 5

Planning
Initiate Review
Individual Review
Issue Communication
Fixing & Reporting

Question 6

What happens in the Planning stage of the Review Process?

Answer 6

Completed by the management team.

Defines what is to be evaluated.

Estimates effort/timeframe.

Selecting participants.

Defines entry/exist criteria.

Question 7

What happens in the Initiate Review stage of the Review Process?

Answer 7

Completed by the manager.

Distribute the work product and other material.

Explains the purpose, scope, roles, etc.

Answers any questions from participants.

Question 8

What happens in the Individual Review stage of the Review Process?

Answer 8

Completed by an individual reviewer.

Review documentation in question and prepare personal notes in a constructive manner - questions, recommendations, defects, etc.

Question 9

What happens in the Issue Communication stage of the Review Process?

Answer 9

Communicating your individual notes to the team.

Make a review decision to reject or accept discussed changes.

Question 10

What happens in the Fixing & Reporting stage of the Review Process?

Answer 10

Making the agreed upon changes (typically completed by the original author).

Record updated status of changes.

Question 11

What are the different roles and responsibilities in a Review?

Answer 11

Management: Review planning, decides on execution of reviews, assigns staff, budget, timeline.

Facilitator (Moderator): Overall responsibility for the review. Decides who is involved, when and where.

Review Leader: Ensures effective running of the review meetings. Mediates when necessary.

Author: Creates the work products under review. Fixes defects.

Reviewers: Experts with technical or business background, stakeholders, involved in the project from different perspectives (ex. tester, designer, etc.)

Scribe (Recorder): Collates found defects. Records open points, defects, and decisions made.

Question 12

What are the different types of Review?

Answer 12

Informal Review
Inspection
Technical Review
Walkthrough

Question 13

What happens in an Informal Review?

Answer 13

A quick/informal meeting or conversation. Often used in Agile development, helpful for quickly solving minor problems.

Ex. Buddy check

Question 14

What happens in a Walkthrough?

Answer 14

Walking through the steps to reproduce with someone else, to show your findings. Informal. Dry runs or similuations.

Ex. Dev not finding the defect after following your Steps to Reproduce, so you walk them through what you did

Question 15

What happens in a Technical Walkthrough?

Answer 15

Reviewing a technical part of a document. Typically completed with a technical expert.

Ideally led by a trained facilitator (typically not the author).

Question 16

What happens in an Inspection?

Answer 16

Follows a defined process, with formal documented outputs, based on rules and checklists.

Uses clearly defined roles (all mandatory).

You’re inviting someone to inspect.

Ex. You bought a house and need a house inspection - You call an expert to do this. They come up with a checklist, to know what to look for.

Ex. The release manager is the “inspector”, to make sure something is ready to be released to production.

Question 17

What are the different types of review techniques that can be applied during the Individual Review?

Answer 17

• Adhoc
• Checklist-based
• Scenarios and dry runs
• Perspective-based
• Role-based

Question 18

What are the characteristics of an Adhoc review?

Answer 18

Reviewers often read the work product sequentially, identifying and documenting issues as they encounter them.

Commonly used technique needing little preparation.

Question 19

What are the characteristics of an Checklist-based review?

Answer 19

A systematic technique, whereby the reviewers detect issues based on checklists.

Main advantage: systematic coverage of typical defect types.

Ex. Inspection Review

Question 20

What are the characteristics of an Scenarios and Dry Run review?

Answer 20

Reviewers are provided with structured guidelines on how to read through the work product.

These scenarios provide reviewers with better guidelines on how to identify specific defect types than simple checklist entries.

Ex. Walkthrough

Question 21

What are the characteristics of an Perspective-based review?

Answer 21

Different reviewers take on different stakeholder viewpoints in individual reviewing (ex. end user, marketer, designer, tester, etc.)

Using different stakeholder viewpoints leads to …
→ more depth in individual reviewing.
→ less duplication of issues.

Question 22

What are the characteristics of an role-based review?

Answer 22

A technique in which the reviewers evaluate the work product from the perspective of individual stakeholder roles (experienced user, child, user admin, system admin, etc.)

Question 23

What are some examples of Organization success factors?

Answer 23

Clear objectives, adequate type and technique, appropriate preparation time, management support

Question 24

What are some examples of People-related success factors?

Answer 24

Choosing the right participants, treating mistakes objectively, good communication in reviews, review culture