ISTQB Certification Questions on Software Testing

Functional System Testing

• Functional system testing is testing the end-to-end functionality of the system as a whole.

Peer Reviews

• Peer Reviews are also called Inspections.

State Transition Diagram

• An invalid state transition is from FAULT to ON.

Code Coverage

• 100% statement coverage does not guarantee 100% branch coverage.
• 100% branch coverage guarantees 100% decision coverage.
• 100% decision coverage does not guarantee 100% branch coverage.

Kick-Off Phase

• The Kick-Off phase of a formal review includes explaining the objective.

Software Development Life Cycle

• Hi-level design corresponds to Unit tests.
• Code corresponds to Acceptance tests.
• Low-level design corresponds to System tests.
• Business requirements correspond to Integration tests.

Fundamental Test Process

• The phases of the Fundamental Test Process are Test Planning and Control, Test implementation and Execution, and Evaluating Exit criteria and reporting.
• Requirement Analysis is not a phase of the Fundamental Test Process.

Black Box Techniques

• State transition testing is a black box technique.
• Boundary value analysis is a black box technique.
• LCSAJ (Linear Code Sequence and Jump) is not a black box technique.

Success Factors for Review

• Success factors for a review include management supporting a good review process and an emphasis on learning and process improvement.
• Defects found are welcomed and expressed objectively.

Defects Discovered by Static Analysis Tools

• Defects discovered by static analysis tools include variables that are never used, security vulnerabilities, programming standard violations, uncalled functions, and procedures.

Test Conditions

• Test Conditions are derived from Specifications.

White and Black Box Testing Techniques

• Equivalence partitioning, Boundary Value Analysis, and State Transition are black box testing techniques.
• Decision Table and Control flow are white box testing techniques.

Regression Testing

• Regression testing should be performed after the software has changed, when the environment has changed, and to verify the Test Environment.

Monitoring Test Progress

• Monitoring test progress includes tracking the percentage of Test Case Execution, percentage of work done in test environment preparation, and defect information.

Test Approach

• The selection of a test approach should consider the context, including risk, skills and experience of the people, and the objective of the testing endeavor.

Large Systems

• Testing large systems should be based on Risk.