ISTQB- All Chapters Exam16 assesses knowledge across various testing techniques like experience-based, error guessing, and exploratory testing. It evaluates understanding of test design, architecture diagrams, and code coverage, crucial for professionals aiming to validate their testing skills.
Specification-based Testing
Error Guessing
Structure-Based Testing
Mutation Analysis
Rate this question:
Learn, design tests, and execute tests simultaneously
Try something, anything, and see what happens
Type randomly on the keyboard to force errors
Identify test criteria and develop test cases as early as possible
Rate this question:
The source code may not be available to the tester
The program’s control flow logic may be flawed
The tester may not know the programming language being used
The program may act unpredictably
Rate this question:
Program control
Coverage
Data flow
Architecture/design
Rate this question:
Program complexity and the skills of the developer
Program complexity and the risk of failure
The time available for testing
Program complexity and the skills of the tester
Rate this question:
100% statement coverage always guarantees 100% path coverage
100% decision or branch coverage always guarantees 100% statement coverage
If a program implements loops, the number of test cases needed to achieve 100% statement coverage is essentially infinite
The number of tests to achieve 100% path coverage will always be more than the number to achieve 100% statement coverage
Rate this question:
100% path coverage, 100% multiple condition coverage, 100% statement coverage, 100% decision/branch coverage
100% statement coverage, 100% condition coverage, 100% conformance coverage, 100% path coverage
100% statement coverage, 100% decision/branch coverage, 100% condition coverage, 100% path coverage
100% statement coverage, 100% path coverage, 100% decision/branch coverage, 100% multiple condition coverage
Rate this question:
100% path coverage from testing does not guarantee sufficient testing of a component
100% path coverage is less comprehensive than 100% branch coverage
100% path coverage will find most or all defects in a component
All of the above
Rate this question:
Measuring code coverage achieved at the unit / component level
Testing for race conditions using a load generation tool
Executing the Functional test suite
Reviewing requirements specification for ambiguity
Rate this question:
All defects before the code is executed
Who developed and tested the code
Process improvement opportunities
The same defects as dynamic testing
Rate this question:
Searching for defects by running the program using only invalid data
Searching for defects by running the program using only valid data
Searching for defects through inspection and analysis rather than running the program
All of the above
Rate this question:
Finding deviations for standard coding practices
Finding ambiguous and missing requirements
Finding overly complex and not maintainable code
Finding defects related to environmental issues such as hardware and operating systems
Rate this question:
Review meeting
Individual preparation
Review process evaluation
Planning
Rate this question:
The review team is trained and comfortable in their roles
The review has loosely defined goals
The reviewers first see the review item in the review meeting
The people issues are not discussed
Rate this question:
The author of the work product leads the walkthrough
Pre-meeting preparation is optional
Sessions are generally open-ended rather than time-boxed
All of the above All of the above - correct
Rate this question:
Informal review
Outside review
Inspection
Technical review
Rate this question:
The manager of the person whose work product is being reviewed
The designated scribe (or recorder)
A trained leader with no vested interest in the work product being reviewed
The author of the work product being reviewed
Rate this question:
Defects
Failures
Requirements
All of the above
Rate this question:
Are Simply problems with the tools and can be safely ignored by testers
Should be logged as System defects
Must be verified individually to determine their validity
Make today's static analysis tools virtually useless
Rate this question:
Standards violations
Unreachable code
Security Vulnerabilities
Failures caused by design errors
Rate this question:
Verification
Validation
Testing
Quality assurance
Rate this question:
Coding
Detailed design
Requirements
High-level design
Rate this question:
For every development activity there is a corresponding testing activity
Each testing activity can be planned as its corresponding development activity is being performed
Test planning can begin long before the code is ready to test
All of the above
Rate this question:
Developers continue adding features and functionality in each subsequent increment
Developers use the V-model of software development
Developers create the entire system in one increment from start to finish
Developers increment components for testing
Rate this question:
Developers are working in isolation while building components
Required functions of the software are not documented
Budgets are limited
All components are not ready for testing at the same time
Rate this question:
Finding as many functional defects as possible
Evaluating whether the system meets the users’ needs and business requirements
Evaluating the users’ experience with the system interface
Measuring the system’s performance
Rate this question:
Is generally performed by independent testers under the direction of the programmers
Focuses on establishing confidence that the system meets the users’ needs
Focuses on the functionality and non-functional characteristics of code modules
Focuses on the functionality of the entire system as specified in the requirements
Rate this question:
Integration
Compliance
Alpha
Beta
Rate this question:
Stub
Sub-system
Driver
Module
Rate this question:
Structural testing only
Functional testing and possibly some structural and non-functional testing
Behavioral testing and simulations
White-box testing and possibly some specification-based testing
Rate this question:
Components in isolation
Interfaces to external systems and packages
Performed by users
Using only black-box techniques
Rate this question:
Black-box testing
Grey-box testing
White-box testing
All of the above
Rate this question:
A synonym for testing
Finding and removing the cause of failures in the specifications
Finding and removing the cause of failures in the code
Finding and removing the cause of failures in the test plan
Rate this question:
The capability of the system to perform required functions
The capability of the system to provide adequate performance
The capability of the system to be learned and used in normal operations
The capability of the system to perform required functions for a specified period of time
Rate this question:
Confidence testing
Re-testing
Regression testing
Change testing
Rate this question:
2, 3, 4, and 5
1, 2, 3, and 4
2, 3, and 4
2, 3, and 5
Rate this question:
Testing of a previously tested program to ensure that defects have not been introduced or uncovered due to program modifications
Going back and re-executing a previous test level when defects are found() For example, testing the design when coding errors are found()
Testing with respect to user needs, requirements, and business processes to determine whether the system meets its acceptance criteria
Testing to determine the system's or component's compliance to standards, regulations, or conventions
Rate this question:
The skills and knowledge of testers to perform regression testing
Different test design techniques to use for re-testing after a change
How changes to a system might affect the unchanged areas of the system
How long a legacy system can remain operational and not need replacement
Rate this question:
Change testing
Re-testing
Smoke testing
Regression testing
Rate this question:
Quiz Review Timeline (Updated): Mar 22, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.