This exam tests knowledge on various aspects of software testing, including incident management, load testing, and test analysis, aligning with ISTQB standards.
Different industries have different risks and quality requirements. This impacts test process.
The size of the software for the new project is much larger than previous one .This impacts test process.
Revising test policy and work procedures should be done at the beginning of each project.
Large organizations mandate strict testing regime from their vendors. This impacts test process.
Rate this question:
Manage the incidents in a spreadsheet posted on the intranet
Purchase and deploy an incident management tool
Manage the incidents through E-mails and phone calls
Document incidents on a large board in the lab
Rate this question:
(-1, 0, 12, 13, 18, 19)
(4, 5, 15, 20)
(-1, 0, 11, 12, 13, 14, 18, 19)
(0, 12, 13, 19)
Rate this question:
Load testing can be performed only in the integration testing phase
Load testing is a functional testing that can be performed at all test levels
Load testing can't be performed by the testing team
Load testing is a non functional testing that can be performed at all test levels
Rate this question:
Test control
Evaluating exit criteria and reporting
Test analysis and design
Test execution
Rate this question:
Do a root cause analysis
Perform bug isolation to find the conditions that cause the crash
Report the incident as is without any further actions
Try to identify the code fragment causing the problem
Rate this question:
Enforcement of coding standards.
Detecting dependencies in software modules.
Quantitative analysis related to tests (e.g . tests passed)
Calculation of complexity of the code.
Rate this question:
$3.01 is a valid output boundary value.
A minimum of 6 valid test cases are derived from boundary value analysis based on input age.
7 and 13 are valid boundary values for equivalence class partition including age 10.
Thursday is a valid input value.
Rate this question:
Decide on the execution of reviews.
Determines if the review objectives have been met.
Planning the review.
Allocate time for review.
Rate this question:
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:
Advantage: being closer to customer perspective, Disadvantage: less independence in perspectives
Advantage: Pulled to support tasks and having less time for testing, Disadvantage: less chances to move a tester to development
Advantage: increased changes to move a tester to development, Disadvantage: pulled to support tasks and having less time for testing
Advantage: More independence in deciding what and how to test, Disadvantage: Isolation from the development team knowledge
Rate this question:
If new defects are to be found, we should run the same test set more often
Testing is better if it starts at the beginning of a project.
How testing is done, is based on situation in a particular project.
More defects are found in a small subset of a systems module.
Rate this question:
Test control
Test Planning
Test execution
Test report
Rate this question:
Load testing, Stress testing, Maintainability testing and Structural testing.
Performance testing, equivalence class testing Reliability testing and Load testing.
Stress testing, Usability testing, Portability testing and Maintainability testing.
System Integration testing, Load testing, Stress testing, and Performance testing.
Rate this question:
II, III, V
I, II,III
I, II, IV
I, IV, V
Rate this question:
I, II, IV
II, III, IV
All the statements are true.
I, II, IV, V
Rate this question:
Open-ended sessions
Usually peer examination
Pre-meeting preparation
Inspection report
Rate this question:
Finding root cause of a defect
Reporting and tracking bugs
Writing test specifications
Producing interim test report
Rate this question:
Can be applied only at system level testing.
Will include only path coverage.
Cannot be applied by using tool support.
May include level of coverage that is stronger than decision coverage.
Rate this question:
Skill and staff shortages; problems in defining the right requirements; contractual issues
Problems in defining the right requirements; contractual issues; poor softwae quality characteristics.
Skill and staff shortages; software does not perform its intended functions; problems in defining the right requirements
Poor software quality characteristics; software does not perform its intended functions
Rate this question:
The number of features implemented in the code
Percentage of work done in test environment preparation
The number of changes done to the product's requirements
Percentage of work done on the user's manuals
Rate this question:
Statement coverage
Multiple condition coverage
Decision coverage
Condition coverage
Rate this question:
A test in which the test cases and test data are based on the program structure of the test object
A static comparison of test and requirements specification of a test object
A dynamic test which is based on the specification of the test object
A test focused on the efficient interactions among different parts of the system.
Rate this question:
I,II
II,III
I,IV
III,IV
Rate this question:
An increasing number of testers always reduce testing time.
A large number of test repetitions mean less test execution effort.
Test case execution effort is dependent on the build quality.
Test case execution effort is independent of the number of test environments.
Rate this question:
I, III
I, II
III,IV
II , IV
Rate this question:
2 test case for statement coverage , 2 test case for branch coverage.
3 test case for statement coverage , 3 test case for branch coverage.
2 test case for statement coverage , 3 test case for branch coverage.
1 test case for statement coverage , 3 test case for branch coverage.
Rate this question:
Developers not needing testers is high level of independence.
Independence of testers results in efficient finding of bugs during unit testing.
Developers should not test their own code because they are NOT objective towards their own code.
Independence of testing does NOT mean that developers should not test their own code.
Rate this question:
I,II,III
I,II
I,IV
I,II,IV
Rate this question:
Acceptance testing is the last level of testing performed prior to system release.
The customers or system users are often responsible for the acceptance testing.
Testing of disaster recovery and backup/restore is usually NOT part of acceptance testing.
The main goal of acceptance testing is to build confidence in the system,not to find defects.
Rate this question:
Because this way you cover the full scope of the products functionality.
Because of the time constraints that usually accompany a test project.
Because choosing a test technique is a common practice in software testing.
Because you need to match the way you test to the content of the product under test.
Rate this question:
Cusotmer A: doesn't offer any upgrade, Customer B: offers upgrade to Gold Luxury room
Customer A: offers upgrade to Gold Luxury room, Customer B: doesn't offer any upgrade
Customer A: doesn't offer any upgrade, Customer B: doesn't offer any upgrade
Customer A: offers upgrade to Silver room, Customer B: offers upgrade to Silver room
Rate this question:
N
N
N
N200
Rate this question:
I, III, IV, V
I, III, IV
II, IV
I, II, III, V
Stress testing is focused on the ability of the system to work under minimum load
Monitoring tools are available only for functional testing
COTS tools are available for the general market and can be adapted to meet specific needs
A test suite must include static and dynamic code analysis tool
Rate this question:
XTime, YCost,ACost of test(per week), BCost of finding a single bug(per week)
XTime, YNumber of defects, ANumber of open defects, BNumber of closed defects
XTime, YCount, ATotal number of executed tests, BNumber of open bugs.
XTime, YPercent, A% of functional tests in the test suite, B% of nonfunctional tests in the test suite
Rate this question:
3, 2,1,0, 30, 31, 32, 33
1, 2, 29, 30
0, 1, 30, 31
1,0,1,2,29,30,31
Rate this question:
The transformation of the test objectives in testing conditions and tangible test cases
The continues comparison between current progress and the test plan, in order to identify deviations
The test ability evaluation of the test basis and test objects and the rootcause analysis
The data collection on the completed test activities, in order to consolidate experience, testware, facts and figures
Experience based testing is best used in integration testing.
Black box testing is equivalent to equivalence partitioning
Experience based testing should be applied after systematic test methods have been used.
White box testing is equally useful for low level and high level testing
Rate this question:
Quiz Review Timeline (Updated): Mar 18, 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.