ISTQB- All Chapters Exam 17 assesses knowledge on maintenance testing triggers, regression testing, impact analysis, risk dimensions, and identification of product and project risks. This quiz is essential for professionals aiming to validate their software testing skills and understanding of industry standards.
Testers can find all the defects before a system is released
By participating in high-level design reviews, testers can better plan and schedule test resource needs
Testers can recommend how to make the system easier to test
Because testers have to think about how to test a function of the system, they can help identify ambiguous requirements specifications
Rate this question:
Requirements specifications
Designs and code
Hardware and operating systems
Testware
Rate this question:
A flaw in a component or system that can cause the component or system to fail to perform its required function
The deviation of the component or system from its expected delivery, service, or result
A human action that produces an incorrect result
All of the above
Rate this question:
100% statement coverage has been achieved but 100% decision coverage has not been achieved.
100% decision coverage has been achieved but 100% statement coverage has not been achieved.
100% statement coverage and 100% branch coverage have been achieved.
100% statement and 100% decision coverage have been achieved
Rate this question:
7 and 13 are boundary values for the equivalence partition including age 10.
$3.01 is a valid output boundary value.
Thursday is a valid input boundary value.
A minimum of 6 valid test cases are derived from boundary value analysis based on input age.
Rate this question:
Suitability and performance of a Multi media (audio video based) system to a new operating system
The ability of an Anti virus package to detect and quarantine a new threat
A billing system used to calculate monthly charge based on large number of subscribers parameters.
Accuracy usability of a new Navigation system compared with previous system.
Rate this question:
A team of users from the accounting department, and have them test the application
Outsource the testing to external company that specializes in accounting software testing.
A team with a mix of software testers and experts from the accounting department.
Rate this question:
Mistakes in the software requirements or specification
Poor coding practices
Extremely tight schedules
All of the above
Rate this question:
Show that the software works as expected
Prove that the software is perfect
Find faults in a system
Prevent errors
Rate this question:
Provides developers with information to isolate the failure
Provides test leaders with information to report test progress
Provides ideas for test process improvement
Does not belong in an incident report.
Rate this question:
Iv is correct and i,ii,iii are incorrect.
I,ii,iii is correct and iv is incorrect
ii is correct and i,ii,iii are incorrect
Iii and iv are correct and i,ii are incorrect
Rate this question:
I and ii
Iii and iv
I and iv
ii and iii
Rate this question:
Send an email to the developers and not report the bug
Report the bug as is without any further action
Try to identify the code fragment causing the problem
Try to recreate the incident before reporting
Rate this question:
I,ii,iv are true and iii is false
I,,iv are true and ii is false
I,ii are true and iii,iv are false
Ii,iii,iv are true and i is false
Rate this question:
Project management
Build release
Configuration management.
Test automation.
Rate this question:
Poor software quality characteristics, software does not perform its intended functions
Skill and staff shortages; software does not perform its intended functions, Problems in defining the right requirements
Skill and staff shortages, Problems in defining the right requirements; contractual issues
Problems in defining the right requirements; contractual issues; Poor software quality characteristics.
Rate this question:
I,ii
Ii,iii
I,iv
Iv
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:
Impact and likelihood
User loss and organizational loss
Anticipated loss and mitigation cost
Probability and possibility
Rate this question:
Poor system reliability
Poor communication between developers and testers
Poor quality of test data
Lack of needed tester training
Rate this question:
System too costly to operate
Skill and/or staff shortage
Poor system performance
Vital function not implemented
Rate this question:
Controlling and mitigating risks
Identifying risks
Comparing identified risks to actual occurrences
Prioritizing risks
Rate this question:
The formal, written requirements document
The set of all test cases, test procedures, input data, and expected results
All documents and sources from which the requirements of a system can be inferred
Another name for the test plan
Rate this question:
The total number of combinations of valid equivalence classes of age and gender is 8
There are two invalid equivalence classes for the age input parameter
All valid equivalence classes could be covered with 6 test cases
All combinations of valid equivalence classes could be covered with 4 test cases
A-unknown B-limited access C-unknown
A-Full access B-Limited access C-unknown
A-unknown B-Full access C-unknown
A-Full access B-limited access C-limited access
Rate this question:
Exploring the system based on the tester's experience
Analyzing the test basis
Logging test results in chronological order
Creating test data
Rate this question:
Criteria for when to stop testing
Test design techniques to employ
Results from performing a set of test cases
Risks and contingencies
Rate this question:
Gather together and save all the key artifacts from the testing project
Close the incident reports after defects are corrected
Complete and turn in test design documents
Destroy evidence of bugs that were fixed before releasing the software
Rate this question:
During test planning activities
After evaluating the list of remaining defects in the system
After the system is ready for execution
Before recommending releasing the system into operational use
Rate this question:
Describe the defect and its effects in neutral, factual terms to avoid criticizing the developer personally
Not only describe the defect but also suggest a correction to the code to speed the defect’s correction
Describe the defect and its effects as negatively as possible to get the developers attention
Describe the defect as briefly as possible to maximize their time finding other defects
Rate this question:
Developers tend to test what they did, and testers tend to test against requirements
Developers are more skilled than testers
Developers write code, and testers check it
Developers and testers rarely if ever work well together
Rate this question:
100% statement coverage has been achieved but 100% decision coverage has not been achieved
100% decision coverage has been achieved but 100% statement coverage has not been achieved
100% statement coverage and 100% branch coverage have been achieved
100% statement and 100% decision coverage have been achieved
Rate this question:
Having another developer on the same team write the tests
Having a tester on an independent team write the tests
Having the users write the tests
Having the developer write tests for his own code
Rate this question:
I,II,III
I,II,III,IV
I,II
II,III,IV,V
Rate this question:
Every method you use to find bugs is limited by your knowledge and experience
Every method you use to find bugs works according to the 80-20 rule: 80 percent of the bugs will be found in 20 percent of the code
Every method you use to find bugs finds fewer than the methods you used before
Every method you use to find bugs leaves other bugs against which those tests are ineffective
Rate this question:
1 and 2 are true; 3 and 4 are false
2 and 3 are true; 1 and 4 are false
2, 3, and 4 are true; 1 is false
1, 2, and 3 are true; 4 is false
Rate this question:
To identify the maximum number of test cases
To identify the values that are not included in the test cases
To test the behavior of the software at or near its limits
To determine the average value for test inputs
Rate this question:
Quiz Review Timeline (Updated): Jan 19, 2025 +
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.