ISTQB certification exam questions for chapter Static techniques

A    The analysis of batch programs.

B    The reviewing of test plans.

C    The analysis of program code.

D    The use of black box testing.

A    Reviews cannot be performed on user requirements specifications.

B    Reviews are the least effective way of testing code.

C    Reviews are unlikely to find faults in test plans.

D    Reviews should be performed on specifications, code, and test plans.

A    Because they share the aim of identifying defects and find the same types of defect.

B    Because they have different aims and differ in the types of defect they find.

C    Because they have different aims but find the same types of defect.

D    Because they share the aim of identifying defects but differ in the types of defect they find.

A    I, II and IV

B    I, II and III

C    I, II, III and IV

D    II, III and IV.

A    Same as static testing

B    Done by the developers

C    Both A. and B

D    None of the above

A    Moderator

B    Author

C    Reviewer

D    Recorder

A    s = 4, t = 3, u = 2 and 5, v = 1

B    s = 4 and 5, t = 3, u = 2, v = 1

C    s = 1 and 5, t = 3, u = 2, v = 4

D    s = 5, t = 4, u = 3, v = 1 and 2

E    s = 4 and 5, t = 1, u = 2, v = 3

A    Inspection is the most formal review process

B    Inspections should be led by a trained leader

C    Managers can perform inspections on management documents

D    Inspection is appropriate even when there are no written documents

E    Inspection compares documents with predecessor (source) documents

A    The use of a variable before it has been defined

B    Unreachable ("dead") code

C    Whether the value stored in a variable is correct

D    The re-definition of a variable before it has been used

E    Array bound violations

A    Defects and issues are identified and corrected

B    The product is reviewed not the producer

C    All members of the reviewing team are responsible for the result of the review

D    Each review has a clear predefined objective

A    Requirement specifications, test plan, code, memory leaks.

B    Requirement specifications, test cases, user guides.

C    Requirement specifications, user guides, performance.

D    Requirement specifications, website, code, use cases.

A    Testers

B    Developers

C    Testers & Developers

D    None

A    I, II and IV

B    I and III

C    III and IV

D    I, III and IV

A    Moderator

B    Scribe

C    Reviewers

D    Author

A    Log defects.

B    Explain the documents to the participants.

C    Gather metrics.

D    Allocate the individual roles.

A    Formal inspection

B    Dynamic testing

C    Code walkthrough

D    Execution testing

A    Customers and users

B    Developers and designers

C    Business and systems analysts

D    System and acceptance testers

A    Supporting reviews.

B    Validating models of the software.

C    Testing code executed in a special test harness.

D    Enforcement of coding standards.

A    Deviations from standards,

B    Requirement defects,

C    Design defects,

D    All of the above.

A    Identifying defects.

B    Fixing defects.

C    A. and B

D    None of the above

A    Planning, Review meeting, Rework, Kickoff

B    Planning, Individual preparation, Kickoff, Rework

C    Planning, Review meeting, Rework, Follow up

D    Planning, Individual preparation, Follow up, Kick off

A    Confront the person and ask that other team members be allowed to express their opinions.

B    Wait for the person to pause, acknowledge the person’ s opinion, and ask for someone else’ s opinion.

C    Switch the topic to an issue about which the person does not have a strong opinion.

D    Express an opinion that differs from the person’ s opinion in order to encourage others to express their ideas.

A    Inexpensive way to get some benefit

B    Find defects

C    Learning, gaining understanding, effect finding

D    Discuss, make decisions, solve technical problems

A    L- N + 2P

B    N - L + 2P

C    N - L + P

D    N - L + P

A    The use of a variable before it has been defined

B    Unreachable ("dead") code

C    Memory leaks

D    Array bound violations

A    ii is true and i,iii,iv are false

B    i,iii,iv are true and ii is false

C    i,iii,iv are false and ii is true

D    iii is true and I,ii,iv are false

A    i,ii,iii,iv,v,vi

B    vi,i,ii,iii,iv,v

C    i,v,iv,ii,iii,vi

D    . i,ii,iii,v,iv,vi

A    i,ii,iii,iv are true

B    i,ii,iii are true and iv is false

C    ii,iii,iv are true and i is false.

D    i,iv are true and ii, iii are false.

A    Static testing requires the running of tests through the code

B    Static testing includes desk checking

C    Static testing includes techniques such as reviews and inspections

D    Static testing can give measurements such as cyclomatic complexity

A    Moderator.

B    Scribe

C    Author

D    Manager

A    Looking for defects occurs during kick-off phase
Fixing defects found happens during rework phase

B    Personnel selection occurs during planning phase
Gathering metrics happens during the review meeting phase

C    Distributing documents occurs during the planning phase
Personal review happens during individual preparation phase

D    Personnel selection occurs during planning phase
Fixing defects found happens during rework phase

A    Scenario, Dry Run, Peer Group

B    Pre-Meeting Preparations

C    Formal Follow Up Process

D    Includes Metrics

A    Explaining the objectives

B    Selecting the personnel, allocating roles.

C    Follow up

D    Individual Meeting preparations

A    Requirements

B    Design

C    Coding

D    All of the above

A    I and III

B    II, III and IV

C    I, II and III

D    IV

A    Reviewer

B    Author

C    Moderator

D    Auditor

A    Inspection.

B    Walkthrough.

C    Review

D    Non Conformance

A    Checklist

B    Checkpoint review

C    Decision table

D    Decision tree

A    Programming standard violations

B    Referring a variable with an undefined value

C    Security vulnerabilities

D    All Above

A    Initiation, Preparation, Informal Review Meeting, Status, Rework, and Follow up.

B    Planning, Preparation, Technical Review, Rework, and Closure.

C    Preparation, Inspection, Rework, Closure, and Follow up.

D    Planning, Kick off, Individual Preparation, Review Meeting, Rework, and Follow up

A    2

B    3

C    4

D    5

A    Takes minutes of the meeting

B    Mediates between people

C    Takes telephone calls

D    Writes the documents to be reviewed

A    Unreachable code

B    Undeclared variable

C    Faults in the requirements

D    Too few comments

A    With static analysis, defects can be found that are difficult to find with dynamic testing.

B    Compiling is not form of static analysis

C    When properly performed, static analysis makes functional testing redundant.

D    Static analysis finds all faults.

A    Gives quality information about the code without executing it.

B    Checks expected results against actual results.

C    Can detect memory leaks.

D    Gives information about what code has and has not been exercised.

A    b, c and d are true; a and e are false

B    a is true; b, c, d and e are false

C    c, d and e are true; a and b are false

D    a, b and d are true; c and e are false

A    Testers and reviewers are not curious enough to find defects.

B    Testers and reviewers are not qualified enough to find failures and
faults.

C    Testers and reviewers communicate defects as criticism against
persons and not against the software product.

D    Testers and reviewers expect that defects in the software product have
already been found and fixed by the developers

A    Initiation, status, preparation, review meeting, rework, follow up.

B    Planning, preparation, review meeting, rework, closure, follow up.

C    Planning, kick off, individual preparation, review meeting, rework, follow
up.

D    Preparation, review meeting, rework, closure, follow up, root cause
analysis.

A    Static analysis can be used as a preventive measure with appropriate
process in place.

B    Static analysis can find defects that are not easily found by dynamic
testing.

C    Static analysis can result in cost savings by finding defects early.

D    Static analysis is a good way to force failures into the software.