This ISTQB - All Chapters Exam1 assesses knowledge across various software testing topics, including static analysis tools, boundary value analysis, structure-based techniques, defect management, and test planning. It's designed for developers, testers, and QA personnel, emphasizing practical skills and theoretical understanding.
-3, -2, -1, 0, 30, 31, 32, 33
0, 1, 30, 31
1, 2, 29, 30
-1,0,1,2,29,30,31
Rate this question:
Statement coverage
Multiple condition
Condition coverage
Decision coverage
Rate this question:
The test engineer should not re-run the tests, as they have already be run, and results recorded
The test engineer should re-run the tests, because the defect shows that the test cases need to be updated
The test engineer should not re-run the tests; they should be part of the developer tests
The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix
Rate this question:
Experience-based testing is best used in integration testing.
Black-box testing is equivalent to equivalence partitioning
White-box testing is equally useful for low-level and high-level testing
Experience-based testing should be applied after systematic test methods have been used.
Rate this question:
Time schedule and deadlines
The features not to be tested
Test policy
Information about test environment and test data
Rate this question:
Unit Test
Acceptance test
System Test
Performance test
Rate this question:
Exit criteria are decided on the basis of entry criteria only
Once finalized, exit criteria cannot be changed by the test manager
Completion of regression testing is never a part of exit criteria
Exit criteria evaluation results in decision to continue or stop testing
Rate this question:
II,IV,V
I,IV
I,III,IV
II
Rate this question:
Provides project managers with information on the project risks.
Provides developers with information to isolate the failure.
Provides test managers with information to report test progress.
Does not belong to an incident report
Rate this question:
N<0, 0<=n<200, n>200
N<0,0<=n<20, 20<=n<=200, n>200
N<=0, n<20, n>=20, n>200
N<0, 0<=n<20, n>=20
Rate this question:
(4,5,15,20)
(0,12,13,18,19)
(-1,0,12,13,18,19)
(-1,0,11,12,13,14,18,19)
Rate this question:
4
1
A very high number
2
Rate this question:
X-Time, Y-Percent, A-% of functional tests in the test suite, B-% of non-functional tests in the test suite
X-Time, Y-Cost, A-Cost of test(per week), B-Cost of finding a single bug(per week)
X-Time, Y-Count, A-Total number of executed tests, B- Number of open bugs.
X-Time, Y-Number of defects, A-Number of open defects, B- Number of closed defects
Rate this question:
0-100-2000-6000
0-1999-2000-5000
1-2000-5001-10000
0, 99-1-2000-4999, 99
Rate this question:
Use case testing provides end-to-end scenario based tests.
Use case based testing is more efficient than other techniques.
Use case-based testing cannot be used in agile projects but other techniques can be used for other models.
Use case based testing is used only for object-oriented projects where as other techniques can be used for all types of projects.
Rate this question:
Ll, lV
LV, V
L, ll
I, ll, lll, IV
Rate this question:
peer reviews find failures while static analysis finds defects.
Static analysis targets the code technically whereas peer review is applicable to together aspects.
Peer reviews cannot find missing requirements where as static analysis can find
peer reviews find defects while static analysis finds failures.
Rate this question:
Testing that the interfaces work correctly.
Another term for testing system integrity.
Looking for faults in larger components or subsystems.
Specifying which components to integrate in which order.
Rate this question:
The number of round bugs is reduced.
The time spent on repetitive tasks is reduced.
The total cost of the test project always decreases
Test coverage is increased.
Rate this question:
During development and testing of a product
During review and testing of a product
During testing and maintenance of a product
During development, review, testing and use of a product
Rate this question:
Testing can show that defects are present, but cannot prove that there are no defects
If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new bugs
Testing everything (all combinations of inputs and preconditions) is not feasible, except for trivial cases
A small number of modules contain most of the defects discovered during pre-release testing, or show most of the operational failures
Agile development is not related to any life cycle model
RAD
V Model
Iterative or incremental
Rate this question:
Incidents may be raised during development, review, testing or use of a software product
Since incidents are the discrepancies between actual and expected outcomes they cannot be raised during development
Incidents should be tracked from discovery and classification to correction and confirmation of the solution
The discrepancies between actual and expected outcomes need to be logged as incidents
Rate this question:
Since test planning is influenced by the developers work, test planning should not start before the entire project plan of the development team is available.
Because independence of testers enhances quality and improves testing, test planning should not take into account constraints from the development team.
Test planning is influenced by among others, the scope of testing, the risks and the availability of resources.
Test planning is an activity that is only performed at the very beginning of the project.
Rate this question:
The evaluation done by testers is not influenced by personal experience
Testers and programmer must always have opposite mindsets
Testers need good communication skills
Experienced testers always guarantee high software quality
Rate this question:
The test specification should follow IEEE standard template.
The test specification should be written very detailed to ensure that everyone understands the application.
The tests should be very detailed with step by step procedures, including button clicks, tabs and menu selections
The tests can be written with less details because of the testers expertise
Rate this question:
A test suite must include static and dynamic code analysis tool
monitoring tools are available only for functional testing
COTS tools are available for the general market and can be adapted to meet specific needs
Stress testing is focused on the ability of the system to work under minimum load
Rate this question:
Requirements review
Calculating path coverage using tools
Usability testing
Performance testing
Rate this question:
IEEE standard 829 covers only test case design specifications.
IEEE standard 829 doesn't cover test case design. It only relates to test planning.
IEEE standard 829 applies mainly for HW testing projects.
IEEE standard 829 is a standard for SW test documentation.
Rate this question:
The test cases are always designed by customers or end users.
The test cases are designed to be used by real users, not by professional testers.
the test cases are designed to find defects in the process flow.
The test cases are designed to find defects in the data flow.
Rate this question:
Impact analysis requires a regression testing for all program elements when there are new changes integrated (new functionalities).
There is no relation between impact analysis and regression testing.
The impact analysis is used to evaluate the amount of regression testing to be performed
Impact analysis requires a regression testing for only the tests that have detected faults in Previous SW release.
Rate this question:
I, III, IV
I, III, IV, V
I, II, III, V
II, IV
Rate this question:
A project manager asks to a test leader to estimate the test effort
A tester installs a test item in the test environment
A tester finds a bug which is resolved prior to release
A test leader writes a test summary report
Rate this question:
Planning, analysis and reporting, design and implementation, execution, test closure activities, evaluating exit criteria.
Planning, analysis, design and implementation, execution, logging, test closure activities, evaluating exit criteria.
Planning, analysis and design, execution, logging and reporting, regression testing
Planning, analysis and design, implementation and execution, evaluation exit criteria and reporting, test closure activities
Rate this question:
Clear allocation of roles to review members, confidence that participants are familiar with the reviewed subject.
No need to write specific plans for reviews , code reviews can save white box testing
Low cost of defects detection, enhancement of code and documents quality, identification improvement opportunities
No need of specific tools, lower risk verification, better classification of detected defects
Rate this question:
The ability to identify related items in documentation, such as requirements vs software design.
The degree to which a requirement is stated in terms that permit establishment of test design.
An approach to integration testing where the component at the top of the component hierarchy is tested first.
The capability of software product to enable modified software to be tested.
Rate this question:
The test ability evaluation of the test basis and test objects and the root-cause analysis
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 data collection on the completed test activities, in order to consolidate experience, testware, facts and figures
Rate this question:
Dynamic test design
Keyword-driven
data coverage analysis
Data driven
Rate this question:
There is very little influence of configuration management practices on the test project
Without proper configuration management, test planning cannot proceed
Configuration management is important for developers, not for testers
Proper configuration management ensures that testers can uniquely identify the tested item
Rate this question:
Quiz Review Timeline (Updated): Nov 9, 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.