Static Techniques

Question 1

What is static testing?

Answer 1

Static Testing is the examination of program source code or other project documentation, without the execution of the code, to find the defects.

Question 2

What are reviews in static testing?

Answer 2

Manual examination of documents - done by humans.

Question 3

What is static analysis?

Answer 3

automated analysis of source code and software - done by tools.

Question 4

Wha is dyanmic testing?

Answer 4

testing performed by executing software undr test and comparing actual vs. expected results.

Question 5

What is the difference between static and dynamic testing?

Answer 5

Static testing will aim at find causes of failuders directly while dynamic will find failures which might be caused by defects.

Question 6

What are some typical documents that get reviewed?

Answer 6

Business requirements, functional specifications, system and database design, source code, test plans, etc..

Question 7

What are some benefits of conducting reviews?

Answer 7

Early defect detection and correction, increased dev productivity, reduced dev cost, fewer defects in code, reduced time and cost of dynamic testing.

Question 8

What is the goal of a review?

Answer 8

The goals of reviews are to verify and validate document against specifications, being consistent with previous documents, and completennes and conformance to stanards.

Question 9

What is the structure of a review?

Answer 9

Planning - kick-off individual preparation - review meeting - re-work - follow-up

Question 10

Reviews - what is planning?

Answer 10

Where the intiial decisions are made, for example the criteria to review, the people who willk review.

Question 11

Reviews - what is a kick-off?

Answer 11

Documents being distributed 3 days prior to the meeting

Question 12

Reviews - what is individual preparation?

Answer 12

The attendees will review the documents and make notes on potential defects they found etc..

Question 13

Reviews - what is the review meeting?

Answer 13

The meeting where the review is held. Managed by the moderator to ensure it is on track.

Question 14

Reviews - what is the rework?

Answer 14

The authour will correct the document

Question 15

Reviews - what is the follow-up?

Answer 15

The moderator ensures the document has been corrected and collects metric on for example time spent reviewing.

Question 16

Reviews - what is a manager?

Answer 16

decides the execution of the review and may not participate.

Question 17

Reviews - what is a moderator?

Answer 17

the one responsible for managing all review team activities. He plans, motitivates, facilitates, trains, and monitor. He should be trained in this process.

Question 18

Reviews - what is the author?

Answer 18

The one preparing the material to be reviewed.

Question 19

Reviews - what are the reviewers?

Answer 19

The ones responsible for finding defects, should have experience on the system and would be ideal to have them from different areas of the business.

Question 20

Reviews - what is the scribe?

Answer 20

Documents all the issue, etc..

Question 21

What are the different types of review?

Answer 21

Informal - walkthrough - technical review - inspection.

Question 22

What is an informal review?

Answer 22

One to one, no formal process. Inexpensive.

Question 23

What is walkthrough review?

Answer 23

Meeting led by the author. Might be a dry scenario, or peer group. The objective is to present information and learn.

Question 24

What is a technical review?

Answer 24

Documented, well defined, with a moderator. Will use guidelines or checklists. A review report is sent out at the end.

Question 25

What is an inspection review?

Answer 25

Vey thorough, has a process. There needs to be entry criteria. There is a moderator, documents will likely be created.

Question 26

What are success factors in reviews?

Answer 26

Clear predefined objectives, right people, testers are valued, defects are welcomed, atmosphere of trust.

Question 27

What are checklists in reviews?

Answer 27

A set of questions usually from one perspective (tester, developer, etc..)

Question 28

What are the benefits of static analysis?

Answer 28

It allows to provide early detection of defects, it can help prevent further defects.

Question 29

What are some examples of defects found by static analysis?

Answer 29

Looping code, unreachable code, data flow analysis.

Question 30

What is a looping code?

Answer 30

A continuous loop running forever.

Question 31

What is unreachable code?

Answer 31

A piece of code that cannot be reached.

Question 32

What is data flow analysis?

Answer 32

Understanding if variables are used or not.

Question 33

Why use static analysis tools and what are they?

Answer 33

These are tools that can be used to review the code. Allow to locate complex source code, produce graphics, design structural tests, examine source code from a number of perspectives.